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
1---2name: maestro-core3description: Use when any Maestro skill loads - provides skill hierarchy, HALT/DEGRADE policies, and trigger routing rules for orchestration decisions4---5
6# Maestro Core - Workflow Router
7
8Central hub for Maestro workflow skills. Routes triggers, defines hierarchy, and handles fallbacks.
9
10## Skill Hierarchy
11
12```
13conductor (1) > orchestrator (2) > designing (3) > tracking (4) > specialized (5)
14```
15
16Higher rank wins on conflicts.
17
18## Ownership Matrix
19
20| Skill | Owns | Primary Triggers |
21|-------|------|------------------|
22| conductor | Implementation + autonomous | `ci`, `ca`, `/conductor-implement`, `/conductor-autonomous` |
23| orchestrator | Parallel execution | `co`, `/conductor-orchestrate` |
24| designing | Phases 1-10 (design → track creation) | `ds`, `cn`, `/conductor-newtrack`, `/conductor-design` |
25| tracking | Task/bead management | `bd *`, `fb`, `rb` |
26| handoff | Session cycling | `ho`, `/conductor-finish`, `/conductor-handoff` |
27| creating-skills | Skill authoring | "create skill", "write skill" |
28
29## Workflow Chain
30
31```
32ds/cn → design.md → /conductor-newtrack → spec.md + plan.md → fb → tracking → ci/co/ca → implementation
33```
34
35## Routing Table
36
37**CRITICAL:** After loading `maestro-core`, you MUST explicitly load the target skill via `skill(name="...")` before proceeding.
38
39See **[routing-table.md](references/routing-table.md)** for complete trigger → skill mappings, phrase triggers, and conditional routing logic.
40
41### Quick Triggers
42
43| Trigger | Skill |
44|---------|-------|
45| `ds`, `cn` | designing |
46| `ci` | conductor |
47| `ca` | conductor |
48| `co` | orchestrator |
49| `fb`, `rb`, `bd *` | tracking |
50| `ho` | handoff |
51
52### Routing Flow
53
54```
551. User triggers command (e.g., `ci`)
562. Load maestro-core → get routing table
573. Look up trigger → find target skill
584. MUST call skill tool to load target skill
595. Follow loaded skill instructions
60```
61
62## Fallback Policies
63
64| Condition | Action | Message |
65|-----------|--------|---------|
66| `bd` unavailable | HALT | `❌ Cannot proceed: bd CLI required` |
67| `conductor/` missing | DEGRADE | `⚠️ Standalone mode - limited features` |
68| Agent Mail unavailable | HALT | `❌ Cannot proceed: Agent Mail required for coordination` |
69
70## Quick Reference
71
72| Concern | Reference |
73|---------|-----------|
74| Complete workflow | [workflow-chain.md](references/workflow-chain.md) |
75| All routing rules | [routing-table.md](references/routing-table.md) |
76| Terms and concepts | [glossary.md](references/glossary.md) |
77| CLI toolboxes | [toolboxes.md](references/toolboxes.md) |
78
79## Related Skills
80
81- [designing](../designing/SKILL.md) - Double Diamond design sessions (phases 1-10)
82- [conductor](../conductor/SKILL.md) - Implementation execution
83- [orchestrator](../orchestrator/SKILL.md) - Multi-agent parallel execution
84- [tracking](../tracking/SKILL.md) - Issue tracking and dependency graphs
85- [handoff](../handoff/SKILL.md) - Session cycling and context preservation
86- [creating-skills](../creating-skills/SKILL.md) - Skill authoring and best practices
87- [sharing-skills](../sharing-skills/SKILL.md) - Contributing skills upstream
88- [using-git-worktrees](../using-git-worktrees/SKILL.md) - Isolated workspaces