ReinaMacCredy/Maestro-CLI

maestroagents-md

Use when bootstrapping, updating, or reviewing AGENTS.md — teaches what makes effective agent memory, how to structure sections, signal vs noise filtering, and when to prune stale entries

maestrobrainstorming

Use before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

maestrodebugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

maestrodesign

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 a standard feature but far richer. Use for…

maestrodispatching

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

maestrodocker

Use when working with Docker containers — debugging container failures, writing Dockerfiles, docker-compose for integration tests, image optimization, or deploying containerized applications

maestroimplement

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

maestronew-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.

maestronext-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…

maestronote

Capture decisions, constraints, and context to persistent memory. Global memory is injected into every session and implementation run. Per-feature memory tracks working context.

maestroparallel-exploration

Use when you need parallel, read-only exploration with task() (Scout fan-out)

maestroplan-review-loop

Deep-review any plan (maestro, Codex, Claude Code plan mode, or plain markdown) using iterative subagent review loops with BMAD-inspired adversarial edge-case discovery. Spawns reviewer subagents that find issues using pre-mortem, inversion, and red-team…

maestroprompt-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,…

maestrorevert

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

maestroreview

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

maestrosimplify

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.

maestrotdd

Use when implementing any feature or bugfix, before writing implementation code

maestroverification

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

maestrovisual

Create interactive HTML visualizations of maestro state and debug data

maestro-pipeline-test

Run a full end-to-end smoke test of all 34 maestro MCP tools AND the CLI commands in a single session. Use this skill when testing the maestro pipeline, verifying tool installation, validating a maestro setup, or checking that all tool groups work (feature,…

maestrodesign

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…

maestronew-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.

maestroplan-review-loop

Deep-review any plan (maestro, Codex, Claude Code plan mode, or plain markdown) using iterative subagent review loops with BMAD-inspired adversarial edge-case discovery. Spawns reviewer subagents that find issues using pre-mortem, inversion, and red-team…

maestroplan-review-loop

Deep-review any plan (maestro, Codex, Claude Code plan mode, or plain markdown) using iterative subagent review loops with BMAD-inspired adversarial edge-case discovery. Spawns reviewer subagents that find issues using pre-mortem, inversion, and red-team…

maestroresearch

Structured research workflow for maestro features. Guides tool selection across three tiers (codebase exploration, Context7 for library docs, NotebookLM for deep analysis), defines research patterns, finding organization via memory_write, and completion…

maestrobrainstorming

Use before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

maestro-dev

Development workflow for maestroCLI itself. Encodes the hexagonal architecture pattern (port -> adapter -> use-case -> command -> MCP tool -> test) and project-specific conventions. Use when implementing new maestro features, adding CLI commands, extending…

maestro-skill-author

Create, update, or debug maestro built-in skills. Covers SKILL.md frontmatter, reference directory structure, step-file architecture, build-time embedding, naming conventions, alias management, and registry validation. Use when creating a new maestro built-in…

maestroagents-md

Use when bootstrapping, updating, or reviewing AGENTS.md — teaches what makes effective agent memory, how to structure sections, signal vs noise filtering, and when to prune stale entries

maestrobrainstorming

Use before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

maestrodebugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

maestrodispatching

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

maestrodocker

Use when working with Docker containers — debugging container failures, writing Dockerfiles, docker-compose for integration tests, image optimization, or deploying containerized applications

maestroimplement

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.

maestronote

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

maestroparallel-exploration

Use when you need parallel, read-only exploration with task() (Scout fan-out)

maestroprompt-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,…

maestrorevert

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

maestroreview

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

maestrosetup

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