maestro-core
Maestro Core - Workflow Router
Central hub for Maestro workflow skills. Routes triggers, defines hierarchy, and handles fallbacks.
Skill Hierarchy
conductor (1) > orchestrator (2) > designing (3) > tracking (4) > specialized (5)
Higher rank wins on conflicts.
Ownership Matrix
| Skill | Owns | Primary Triggers |
|---|---|---|
| conductor | Implementation + autonomous | ci, ca, /conductor-implement, /conductor-autonomous |
| orchestrator | Parallel execution | co, /conductor-orchestrate |
| designing | Phases 1-10 (design → track creation) | ds, cn, /conductor-newtrack, /conductor-design |
| tracking | Task/bead management | bd *, fb, rb |
| handoff | Session cycling | ho, /conductor-finish, /conductor-handoff |
| creating-skills | Skill authoring | "create skill", "write skill" |
Workflow Chain
ds/cn → design.md → /conductor-newtrack → spec.md + plan.md → fb → tracking → ci/co/ca → implementation
Routing Table
CRITICAL: After loading maestro-core, you MUST explicitly load the target skill via skill(name="...") before proceeding.
See routing-table.md for complete trigger → skill mappings, phrase triggers, and conditional routing logic.
Quick Triggers
| Trigger | Skill |
|---|---|
ds, cn |
designing |
ci |
conductor |
ca |
conductor |
co |
orchestrator |
fb, rb, bd * |
tracking |
ho |
handoff |
Routing Flow
1. User triggers command (e.g., `ci`)
2. Load maestro-core → get routing table
3. Look up trigger → find target skill
4. MUST call skill tool to load target skill
5. Follow loaded skill instructions
Fallback Policies
| Condition | Action | Message |
|---|---|---|
bd unavailable |
HALT | ❌ Cannot proceed: bd CLI required |
conductor/ missing |
DEGRADE | ⚠️ Standalone mode - limited features |
| Agent Mail unavailable | HALT | ❌ Cannot proceed: Agent Mail required for coordination |
Quick Reference
| Concern | Reference |
|---|---|
| Complete workflow | workflow-chain.md |
| All routing rules | routing-table.md |
| Terms and concepts | glossary.md |
| CLI toolboxes | toolboxes.md |
Related Skills
- designing - Double Diamond design sessions (phases 1-10)
- conductor - Implementation execution
- orchestrator - Multi-agent parallel execution
- tracking - Issue tracking and dependency graphs
- handoff - Session cycling and context preservation
- creating-skills - Skill authoring and best practices
- sharing-skills - Contributing skills upstream
- using-git-worktrees - Isolated workspaces
More from reinamaccredy/maestro
conductor
Implementation execution for context-driven development. Trigger with ci, /conductor-implement, or /conductor-* commands. Use when executing tracks with specs/plans. For design phases, see designing skill. For session handoffs, see handoff skill.
10maestro-revert
Git-aware revert of track, phase, or individual task. Safely undoes implementation with plan state rollback.
9maestro-new-track
Create a new feature/bug track with spec and implementation plan. Interactive interview generates requirements spec, then phased TDD plan. Use when starting work on a new feature, bug fix, or chore.
8init
Generates AGENTS.md and CLAUDE.md files using the WHAT/WHY/HOW framework. Explores the codebase and produces minimal (<100 line) context files with progressive disclosure.
8maestro-setup
Scaffolds project context (product, tech stack, coding guidelines, product guidelines, workflow) and initializes track registry. Use for first-time project onboarding.
7tracking
>
7