maestro:status

23
ReinaMacCredyReinaMacCredy

Show track progress overview with phase/task completion stats, next actions, and blockers.

194 days ago

maestro:new-track

23
ReinaMacCredyReinaMacCredy

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.

194 days ago

analyze

23
ReinaMacCredyReinaMacCredy

Primary deep read-only investigation workflow. Use this first to understand a problem before any implementation work.

194 days ago

learner

23
ReinaMacCredyReinaMacCredy

Extracts reusable principles from the current session and stores them as learned skills. Use when you want to capture durable patterns after completing work.

194 days ago

maestro:implement

23
ReinaMacCredyReinaMacCredy

Execute track tasks following TDD workflow. Single-agent by default, --team for parallel Agent Teams. Use when ready to implement a planned track.

194 days ago

doctor

23
ReinaMacCredyReinaMacCredy

Primary Maestro diagnostic flow. Diagnoses installation issues, detects configuration drift, and auto-fixes common problems.

194 days ago

security-review

23
ReinaMacCredyReinaMacCredy

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.

194 days ago

maestro:revert

23
ReinaMacCredyReinaMacCredy

Git-aware revert of track, phase, or individual task. Safely undoes implementation with plan state rollback.

194 days ago

review

23
ReinaMacCredyReinaMacCredy

Performs code review with plan-to-implementation comparison and structured diff analysis, including auto-fix support. Use when validating quality and addressing review findings.

195 days ago

maestro-design

23
ReinaMacCredyReinaMacCredy

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.

194 days ago

reset

23
ReinaMacCredyReinaMacCredy

Cleans stale Maestro state by removing old drafts, orphaned teams, and stale task directories. Use when the local Maestro state is inconsistent or cluttered.

194 days ago

research

23
ReinaMacCredyReinaMacCredy

Supporting follow-up mode for multi-source validation after analyze. Use to extend existing findings with docs/web cross-checks.

195 days ago

example-skill

23
ReinaMacCredyReinaMacCredy

Template for creating skills. Use when writing new code, reviewing code, or when the skill's specific domain applies. Replace this description with specifics.

195 days ago

trace

23
ReinaMacCredyReinaMacCredy

Shows agent execution timelines and performance summaries. Use when debugging orchestration flow or measuring run behavior.

194 days ago

maestro:review

23
ReinaMacCredyReinaMacCredy

Code review for a track against its spec and plan. Verifies implementation matches requirements, checks code quality and security.

194 days ago

setup-check

23
ReinaMacCredyReinaMacCredy

Fast prerequisite gate for Maestro runtime readiness. Use before `/design` or `/work` to verify required local tooling and flags.

194 days ago

planning

23
ReinaMacCredyReinaMacCredy

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.

194 days ago

design

23
ReinaMacCredyReinaMacCredy

Conducts interview-driven planning via Prometheus agent asking clarifying questions before generating an implementation plan. Use when starting work on features or tasks.

194 days ago

psm

23
ReinaMacCredyReinaMacCredy

Manages isolated development sessions using git worktrees and tmux. Use when running parallel tasks that require separate environments.

194 days ago

init

23
ReinaMacCredyReinaMacCredy

Generates AGENTS.md file using the WHAT/WHY/HOW framework. Explores the codebase and produces a minimal (<100 line) context file with progressive disclosure.

194 days ago

pipeline

23
ReinaMacCredyReinaMacCredy

Runs sequential agent chains with context passed between stages. Use when work should flow through ordered specialist steps.

194 days ago

maestro-note

23
ReinaMacCredyReinaMacCredy

Capture decisions, constraints, and context to persistent notepad. Priority notes are injected into every session and implementation run.

195 days ago

context7

23
ReinaMacCredyReinaMacCredy

Fetches up-to-date library documentation via Context7 MCP for external libraries, APIs, and frameworks. Use when working with external dependencies or unfamiliar APIs.

194 days ago

release

23
ReinaMacCredyReinaMacCredy

Automates version bumping, tagging, publishing, and GitHub release creation. Use when preparing and shipping a project release.

194 days ago

maestro

23
ReinaMacCredyReinaMacCredy

Provides the Maestro workflow for interview-driven planning and team-based execution. Use when orchestrating work with /design, /planning, and /work.

195 days ago

project-conventions

23
ReinaMacCredyReinaMacCredy

Discovers project conventions from configuration files and coding-standard sources. Use when agents need repository-specific style and workflow rules.

194 days ago

setup

23
ReinaMacCredyReinaMacCredy

Scaffolds persistent project context files through a guided interview. Use when onboarding a repository to Maestro context workflows.

194 days ago

status

23
ReinaMacCredyReinaMacCredy

Shows current Maestro state including plans, drafts, active tasks, and wisdom files. Use when checking progress and session health.

194 days ago

web-design-guidelines

23
ReinaMacCredyReinaMacCredy

Reviews UI code for Web Interface Guidelines compliance checking accessibility, design patterns, and UX best practices. Use when auditing UI code or reviewing designs.

195 days ago

git-worktrees

23
ReinaMacCredyReinaMacCredy

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.

194 days ago

work

23
ReinaMacCredyReinaMacCredy

Execute a plan or direct task with worker delegation and verification.

194 days ago

styleguide

23
ReinaMacCredyReinaMacCredy

Detects project languages and injects code style guides into CLAUDE.md. Use when establishing consistent coding conventions.

194 days ago

maestro:setup

23
ReinaMacCredyReinaMacCredy

Scaffolds project context (product, tech stack, coding guidelines, product guidelines, workflow) and initializes track registry. Use for first-time project onboarding.

194 days ago

plan-template

23
ReinaMacCredyReinaMacCredy

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.

194 days ago

ultraqa

23
ReinaMacCredyReinaMacCredy

Runs an iterative fix-and-verify loop for tests, build, lint, and typecheck failures. Use when you need automated diagnose-fix-reverify cycles.

195 days ago

note

23
ReinaMacCredyReinaMacCredy

Manages persistent working-memory notes across sessions. Use when you need to store priority context, decisions, or reminders.

194 days ago