designing
Design & Planning
Turn ideas into fully-formed, implementation-ready designs through a unified 10-phase pipeline.
Entry Points
| Trigger | Action |
|---|---|
ds |
Start unified pipeline (all 10 phases) |
/conductor-design |
Start unified pipeline (alias) |
cn, /conductor-newtrack |
Create spec + plan + beads from existing design.md |
pl, /plan |
Planning phases (5-10) - see pl Entry Modes below |
| "design a feature" | Start unified pipeline |
| "let's think through X" | Start unified pipeline |
Quick Reference
Unified Pipeline (10 Phases)
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