maestro-new-track
New Track -- Specification & Planning
Create a new development track with a requirements specification and phased implementation plan. Every feature, bug fix, or chore gets its own track.
Arguments
$ARGUMENTS
The track description. Examples: "Add dark mode support", "Fix login timeout", "Refactor connection pooling"
Step 1: Validate Prerequisites
Check .maestro/context/product.md exists. If not: "Run /maestro:setup first." Stop.
Check .maestro/tracks.md exists. If missing, create it with registry header.
Step 2: Parse Input
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.
9init
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
>
7maestro-implement
Execute track tasks following TDD workflow. Single-agent by default, --team for parallel Agent Teams, Sub Agent Parallels. Use when ready to implement a planned track.
7