| name | maestro-core |
| description | Use when any Maestro skill loads - provides skill hierarchy, HALT/DEGRADE policies, and trigger routing rules for orchestration decisions |
Maestro Core - Workflow Router
Central hub for Maestro workflow skills. Routes triggers, defines hierarchy, and handles fallbacks.
Skill Hierarchy
conductor (1) > orchestrator (2) > design (3) > beads (4) > specialized (5)
Higher rank wins on conflicts.
Workflow Chain
ds → design.md → /conductor-newtrack → spec.md + plan.md → fb → beads → ci/co → implementation
Routing Table
CRITICAL: After loading maestro-core, you MUST explicitly load the target skill via skill(name="...") before proceeding. This table only provides routing - it does NOT auto-load skills.
| Trigger |
Skill to Load |
Description |
ds, /conductor-design |
skill(name="design") |
Double Diamond design sessions |
/conductor-setup |
skill(name="conductor") |
Initialize project |
cn, /conductor-newtrack |
skill(name="conductor") |
Create spec + plan from design |
ci, /conductor-implement |
skill(name="conductor") |
Execute track (auto-routes to orchestrator) |
co, /conductor-orchestrate |
skill(name="orchestrator") |
Parallel execution |
/conductor-finish |
skill(name="conductor") |
Complete track |
fb, file-beads |
skill(name="beads") |
File beads from plan |
rb, review-beads |
skill(name="beads") |
Review filed beads |
bd ready |
skill(name="beads") |
Find available work |
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
Related Skills