maestro:status
Show track progress overview with phase/task completion stats, next actions, and blockers.
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.
analyze
Primary deep read-only investigation workflow. Use this first to understand a problem before any implementation work.
learner
Extracts reusable principles from the current session and stores them as learned skills. Use when you want to capture durable patterns after completing work.
maestro:implement
Execute track tasks following TDD workflow. Single-agent by default, --team for parallel Agent Teams. Use when ready to implement a planned track.
doctor
Primary Maestro diagnostic flow. Diagnoses installation issues, detects configuration drift, and auto-fixes common problems.
security-review
Performs deep security analysis: checks auth flows, injection vectors, secrets, and dependencies. Reports findings with severity ratings and file:line evidence. Use when reviewing code for security vulnerabilities or performing security audits.
maestro:revert
Git-aware revert of track, phase, or individual task. Safely undoes implementation with plan state rollback.
review
Performs code review with plan-to-implementation comparison and structured diff analysis, including auto-fix support. Use when validating quality and addressing review findings.
maestro-design
Deep discovery and specification for ambitious features. Full BMAD-inspired interview with classification, vision, journeys, domain analysis, and FR synthesis. Same output contract (spec.md + plan.md) as new-track but far richer. Use for multi-component systems, regulated domains, or unclear requirements.
reset
Cleans stale Maestro state by removing old drafts, orphaned teams, and stale task directories. Use when the local Maestro state is inconsistent or cluttered.
research
Supporting follow-up mode for multi-source validation after analyze. Use to extend existing findings with docs/web cross-checks.
example-skill
Template for creating skills. Use when writing new code, reviewing code, or when the skill's specific domain applies. Replace this description with specifics.
trace
Shows agent execution timelines and performance summaries. Use when debugging orchestration flow or measuring run behavior.
maestro:review
Code review for a track against its spec and plan. Verifies implementation matches requirements, checks code quality and security.
setup-check
Fast prerequisite gate for Maestro runtime readiness. Use before `/design` or `/work` to verify required local tooling and flags.
planning
Generate comprehensive implementation plans through systematic discovery, synthesis, verification, and decomposition into beads. Use when asked to plan a feature, create a roadmap, design an implementation approach, or decompose work into trackable issues. Do NOT use for simple one-step tasks, quick fixes, or when the user just wants to execute an existing plan — use the work skill instead.
design
Conducts interview-driven planning via Prometheus agent asking clarifying questions before generating an implementation plan. Use when starting work on features or tasks.
psm
Manages isolated development sessions using git worktrees and tmux. Use when running parallel tasks that require separate environments.
init
Generates AGENTS.md file using the WHAT/WHY/HOW framework. Explores the codebase and produces a minimal (<100 line) context file with progressive disclosure.
pipeline
Runs sequential agent chains with context passed between stages. Use when work should flow through ordered specialist steps.
maestro-note
Capture decisions, constraints, and context to persistent notepad. Priority notes are injected into every session and implementation run.
context7
Fetches up-to-date library documentation via Context7 MCP for external libraries, APIs, and frameworks. Use when working with external dependencies or unfamiliar APIs.
release
Automates version bumping, tagging, publishing, and GitHub release creation. Use when preparing and shipping a project release.
maestro
Provides the Maestro workflow for interview-driven planning and team-based execution. Use when orchestrating work with /design, /planning, and /work.
project-conventions
Discovers project conventions from configuration files and coding-standard sources. Use when agents need repository-specific style and workflow rules.
setup
Scaffolds persistent project context files through a guided interview. Use when onboarding a repository to Maestro context workflows.
status
Shows current Maestro state including plans, drafts, active tasks, and wisdom files. Use when checking progress and session health.
web-design-guidelines
Reviews UI code for Web Interface Guidelines compliance checking accessibility, design patterns, and UX best practices. Use when auditing UI code or reviewing designs.
git-worktrees
Creates isolated working directories using git worktrees for parallel plan execution. Enables multiple plans to run simultaneously without file conflicts. Use when running concurrent development tasks.
work
Execute a plan or direct task with worker delegation and verification.
styleguide
Detects project languages and injects code style guides into CLAUDE.md. Use when establishing consistent coding conventions.
maestro:setup
Scaffolds project context (product, tech stack, coding guidelines, product guidelines, workflow) and initializes track registry. Use for first-time project onboarding.
plan-template
Scaffolds a blank plan file with required sections in .maestro/plans/. Use when creating a new implementation plan. Do NOT use when a full planning pipeline is needed — use the planning skill instead.
ultraqa
Runs an iterative fix-and-verify loop for tests, build, lint, and typecheck failures. Use when you need automated diagnose-fix-reverify cycles.
note
Manages persistent working-memory notes across sessions. Use when you need to store priority context, decisions, or reminders.