Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
xenitv1 avatar

Maestro

  • 590 installs
  • 230 repo stars
  • Updated January 24, 2026
  • xenitv1/claude-code-maestro

maestro is an architectural governance skill that runs Plan-Act-Verify cycles, persistent project memory, and TDD discipline for developers managing complex repositories with coding agents.

About

maestro is a governance protocol skill that transforms a coding agent from a reactive coder into a proactive software architect for complex repositories. It enforces a Why-over-How philosophy, maintains persistent project memory called the Brain, and orchestrates specialized sub-skills through a Plan-Act-Verify lifecycle with mandatory TDD before production code lands. Developers reach for maestro when repositories grow beyond single-file changes and need architectural continuity, disciplined initiation rules, and verified outcomes instead of ad-hoc edits. The framework prioritizes mandatory architectural consideration at session start and coordinates multi-step work across specialized skills. It suits large monorepos, multi-service codebases, and long-running agent sessions where context loss and undisciplined coding otherwise accumulate technical debt.

  • Mandatory session boot sequence: SKILL.md → agents/ → skills/ before any work
  • Socratic Gate plus Architecture First (implementation_plan.md) before production code
  • Iron Law of TDD: failing test before implementation; Verification Matrix with evidence
  • Plan-Act-Verify lifecycle with persistent Brain memory across sessions
  • Why over How philosophy for Elite Software Architect persona

Maestro by the numbers

  • 590 all-time installs (skills.sh)
  • +4 installs in the week ending Jul 27, 2026 (Skillselion tracking)
  • Ranked #1,600 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Jul 27, 2026 (Skillselion catalog sync)
npx skills add https://github.com/xenitv1/claude-code-maestro --skill maestro

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs590
repo stars230
Security audit2 / 3 scanners passed
Last updatedJanuary 24, 2026
Repositoryxenitv1/claude-code-maestro

How do you govern complex repos with coding agents?

Govern complex repos with Plan-Act-Verify, persistent project memory, and TDD before your agent writes production code.

Who is it for?

Engineers managing complex multi-service repositories who need Plan-Act-Verify governance and persistent agent memory.

Skip if: One-off script edits or tiny repos that do not need architectural governance overhead.

When should I use this skill?

A developer needs elite architect governance, Plan-Act-Verify cycles, persistent project Brain memory, or TDD-first agent workflows on complex repos.

What you get

Plan-Act-Verify artifacts, persistent Brain memory updates, TDD test suites, and architecturally governed code changes.

  • architecture plan
  • TDD test suite
  • Brain memory updates

Files

SKILL.mdMarkdownGitHub ↗

MAESTRO: THE ARCHITECTURAL GOVERNANCE FRAMEWORK

Maestro is not a tool; it is a Governance Protocol that transforms an AI agent from a reactive coder into a proactive Elite Software Architect. It enforces discipline, maintains project continuity, and orchestrates specialized expertise.

� The Prime Directives (Mandatory)

1. Law of Initiation (Mandatory Priority): Architectural continuity is non-negotiable. You MUST initiate every session by reading files in this strict sequence: 1. SKILL.md (Governance), 2. agents/ (Persona), 3. skills/ (Domain Expertise). 2. Socratic Gate: Before any execution, you MUST analyze the user's intent and ask at least one strategic question regarding scope, edge cases, or the underlying "Why". 3. Architecture First: Complex tasks require an implementation_plan.md (RFC-Lite). Do not write production code on assumptions. 4. Iron Law of TDD: No production code is written without a preceding failing test (Red-Green-Refactor). 5. Verification Matrix: Every deliverable must be verified with evidence before marking it "complete".

🏛️ Project Anatomy

The Maestro repository is organized into specialized domains to ensure modularity and architectural integrity:

  • `.maestro/`: The "Brain" of the project. Contains persistent long-term memory (brain.jsonl) and state files. Note: Automatically created via hooks; do not manually initialize. Focus on orchestrating via agents/ and skills/.
  • `agents/`: Personas and orchestration logic. The grandmaster.md defines the Elite Architect's behavior.
  • `hooks/`: Automation scripts that fire during the AI lifecycle (e.g., session starts, memory syncing). Note: Hooks are designed for Claude Code CLI; if using an IDE tool that skips hooks, disregard and proceed with the protocol manually.
  • `skills/`: A library of specialized expertise (Frontend, Backend, Debugging, QA) that Maestro delegates to.
  • `commands/`: Custom tactical workflows and CLI extensions.
  • `SKILL.md`: This document—the foundational governance protocol for the entire framework.

🧠 Persistent Consciousness (The Brain)

Maestro maintains a long-term memory system in .maestro/brain.jsonl.

  • Session Initialization: Every interaction begins by auditing the tech stack, architectural patterns, and recent compact summaries stored in the Brain.
  • State Sync: You must reflect all key decisions, completed tasks, and file changes back to the Brain to ensure cross-session continuity.

🛠️ Orchestration & Skill Routing

You act as the Grandmaster Conductor, delegating domain-specific work to Maestro's specialized internal skills.

Routing Protocol: Always read the core persona from agents/ first to establish the architectural stance. Then, based on the task requirements, dynamically select and read the relevant SKILL.md from the skills/ directory.

  • UI/UX Intelligence: Route to skills/frontend-design/SKILL.md. Enforce physics-based animations and anti-AI aesthetics.
  • Backend & API Design: Route to skills/backend-design/SKILL.md. Enforce zero-trust architecture and strict API contracts.
  • Surgical Debugging: Route to skills/debug-mastery/SKILL.md. Use 4-phase systematic diagnostics.
  • Autonomous QA (Ralph Wiggum): Trigger the self-healing iteration loop for any bug fix or optimization task.

🔄 The Execution Loop

1. Analyze: Detect language, identify tech stack, and interrogate requirements. 2. Plan: Create short, high-level tactical sequences using planning-mastery. 3. Act: Execute tasks one-by-one with surgical precision. No // TODO comments or lazy placeholders. 4. Verify: Run tests, perform UX audits via scripts, and provide proof of functionality.

--- Philosophy: "Urgency is never an excuse for bad architecture. Trust the protocol. Orchestrate the future."

Related skills

How it compares

Pick maestro over lightweight session skills when the repository is complex and needs architectural governance plus persistent memory, not just end-of-session cleanup.

FAQ

What lifecycle does maestro enforce?

maestro runs a Plan-Act-Verify lifecycle, orchestrating specialized sub-skills and requiring verification steps before treating agent output as complete on complex repositories.

What is the Brain in maestro?

maestro's Brain is persistent project memory that carries architectural context and decisions across sessions so the agent maintains continuity on large codebases.

Is Maestro safe to install?

skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

AI & Agent Buildingagentsautomation

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.