maestro

Plugin maestro from marketplace maestro in ReinaMacCredy/Maestro-CLI. Commands read from the repo's manifest — 1 month ago.

Skills (36)

• 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 the MCP server, creating new adapters, modi

• 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, plan, task, memory, meta, graph, handoff,

• 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 skill, modifying an existing SKILL.md, a

• maestro-v2-migration

  Guide for working with maestroCLI's v2 architecture. Covers the context-to-memory rename, 4-state task model, plain file backend, pre-agent hooks, research phase, and memory promotion. Use when touching v2 code, encountering legacy patterns (e.g. 'context' instead of 'memory', old task states), addi

• maestro:brainstorming

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

• maestro:plan-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 techniques, auto-fixes them with structured f

• maestro:research

  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 criteria. Use during the research pipeline sta

• mcp-builder

  Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

• prompt-leverage

  Strengthen a raw user prompt into an execution-ready instruction set for Amp, Claude Code, 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

• maestro:agents-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

• maestro:debugging

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

• 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 require

• 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

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

• commit

  Create a well-formed git commit from current changes using session history for

• debug

  Investigate stuck runs and execution failures by tracing Symphony and Codex

• land

  Land a PR by monitoring conflicts, resolving them, waiting for checks, and

• linear

  Use Symphony's `linear_graphql` client tool for raw Linear GraphQL operations such as comment editing and upload flows.

• pull

  Pull latest origin/main into the current local branch and resolve merge

• push

  Push current branch changes to origin and create or update the corresponding

• 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 c

• 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

MCP servers (1)

• maestro

  runs: node ./start.mjs

Similar plugins