maestro-review
Review -- Track Code Review
Review the implementation of a track against its specification and plan. Verifies intent match, code quality, test coverage, and security.
Arguments
$ARGUMENTS
<track-name>: Match track by name or ID substring--current: Auto-select the in-progress ([~]) track- No args: ask user which track to review, or fall back to uncommitted/staged changes if no tracks exist
Step 1: Select Track
- If
--current: Find the[~]track in.maestro/tracks.md - If track name given: Match by ID or description substring
- If no args and tracks exist: List completed and in-progress tracks, ask user
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