maestro:dispatching
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
maestro:docker
Use when working with Docker containers — debugging container failures, writing Dockerfiles, docker-compose for integration tests, image optimization, or deploying containerized applications
maestro: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.
maestro: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.
maestro:note
Capture decisions, constraints, and context to persistent notepad. Priority notes are injected into every session and implementation run.
maestro:parallel-exploration
Use when you need parallel, read-only exploration with task() (Scout fan-out)
maestro:prompt-leverage
Strengthen a raw user prompt into an execution-ready instruction set for Claude Code, Amp, Codex, or another AI agent. Use when the user wants to improve an existing prompt, build a reusable prompting framework, wrap the current request with better structure, add clearer tool rules, or create a hook that upgrades prompts before execution.
maestro:revert
Git-aware revert of track, phase, or individual task. Safely undoes implementation with plan state rollback.
maestro:review
Code review for a track against its spec and plan. Verifies implementation matches requirements, checks code quality and security.
maestro:setup
Scaffolds project context (product, tech stack, coding guidelines, product guidelines, workflow) and initializes track registry. Use for first-time project onboarding.
maestro:status
Interpret feature progress, detect problems, and recommend next actions based on maestro status output.
maestro:symphony-setup
Set up Symphony orchestration for any repository. Installs Codex skills, generates a customized WORKFLOW.md, configures Linear integration, and verifies the setup. Works with any tech stack.
linear
|
maestro:tdd
Use when implementing any feature or bugfix, before writing implementation code
maestro:verification
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
maestro:new-feature
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.
maestro:next-move
Strategic analysis of a project to identify the single highest-leverage, most innovative addition. Use when the user asks what to build next, what the most impactful improvement would be, what's missing, or any question about strategic direction and priorities. Also use when stuck choosing between competing features.
maestro:simplify
Review changed code for reuse, quality, and efficiency, then fix issues found. Use after implementing a task or feature -- catches duplication, hacky patterns, and wasted work before review.
maestro:visual
Create interactive HTML visualizations of maestro state and debug data
Page 3 of 3 · 119 results