Maestro: Architectural Governance

What it does

Maestro is a governance framework that guides an AI to behave as an Elite Software Architect. It prescribes session initialization steps, maintains persistent project memory (a Brain), enforces planning (RFC-lite), test-first coding, and a Plan-Act-Verify lifecycle to ensure architectural continuity and verifiable deliverables.

When to use it

Use Maestro for large or complex engineering work where continuity, architecture, and verification matter: repository refactors, multi-component designs, onboarding large feature work, or when you want strict orchestration across multiple internal skills. It activates when tasks require long-term memory, structured plans, or rigorous testing discipline.

What's included

• Scripts: none found (has_scripts=false) but the skill references a .maestro/ brain, agents/, skills/, and hooks/ directories as part of its workflow.
• References: no bundled references, but the SKILL.md provides a detailed governance protocol and file layout guidance.
• Instructions: a set of "Prime Directives" (init sequence, Socratic Gate question, Architecture First, TDD requirement, Verification Matrix) and an execution loop (Analyze → Plan → Act → Verify). The doc also describes repository organization (.maestro/, agents/, skills/, hooks/) and expectations for maintaining the Brain.

Compatible agents

{}