maestro-setup
Maestro Setup -- Project Context Scaffolding
Interview the user to create persistent project context documents. These files are referenced by all maestro:* skills for deeper project understanding.
Arguments
$ARGUMENTS
--reset: Delete all existing context files and start fresh.- Default (no args): Run setup interview. If context already exists, offer to update or skip.
Step 1: Handle --reset
If $ARGUMENTS contains --reset:
- Confirm with user before deleting
.maestro/context/,.maestro/tracks.md,.maestro/setup_state.json - If confirmed: delete and report. Stop.
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.
8tracking
>
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