maestro-revert
Revert -- Git-Aware Undo
Safely revert implementation work at track, phase, or task granularity. Updates plan state to reflect the rollback.
Arguments
$ARGUMENTS
<track>: Track name or ID (optional -- if omitted, enter Guided Selection)--phase <N>: Revert only phase N (optional)--task <name>: Revert only a specific task (optional)- No scope flag: revert the entire track
Step 1: Parse Target Scope
Determine what to revert:
- Track-level: No
--phaseor--taskflag. Revert all commits in the track.
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-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
>
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