Sponsored by

Find leads on Reddit on auto pilot

Topic: plugin

507 skills in this topic.

maestro:docker Use when working with Docker containers — debugging container failures, writing Dockerfiles, docker-compose for integration tests, image optimization, or deploying containerized applications
ReinaMacCredy/maestro 26
maestro:implement 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.
ReinaMacCredy/maestro 26
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.
ReinaMacCredy/maestro 26
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.
ReinaMacCredy/maestro 26
maestro:note Capture decisions, constraints, and context to persistent memory. Global memory is injected into every session and implementation run. Per-feature memory tracks working context.
ReinaMacCredy/maestro 26
maestro:parallel-exploration Use when you need parallel, read-only exploration with task() (Scout fan-out)
ReinaMacCredy/maestro 26
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 fix strategies, and re-reviews until the plan passes with zero actionable issues. Use when the user says 'review the plan', 'deep review', 'check the plan thoroughly', 'review loop', 'validate before approving', or wants rigorous plan validation before execution. Also use proactively before plan-approve when the plan is complex or high-risk.
ReinaMacCredy/maestro 26
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.
ReinaMacCredy/maestro 26
maestro:revert Git-aware revert of feature, phase, or individual task. Safely undoes implementation with task state rollback.
ReinaMacCredy/maestro 26
maestro:review Code review for a feature against its spec and plan. Verifies implementation matches requirements, checks code quality and security.
ReinaMacCredy/maestro 26
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.
ReinaMacCredy/maestro 26
maestro:tdd Use when implementing any feature or bugfix, before writing implementation code
ReinaMacCredy/maestro 26
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
ReinaMacCredy/maestro 26
maestro:visual Create interactive HTML visualizations of maestro state and debug data
ReinaMacCredy/maestro 26
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, adding reference files, debugging skill loading failures, updating the skills registry, or working on the skills full port. Also use when frontmatter validation fails, skills don't appear in skill-list, or reference files fail to load.
ReinaMacCredy/maestro 26
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), adding new v2 features, or debugging v2 behavior. Also use when you see imports from adapters/fs/context, references to 'contextAdapter', or task states that don't match the 4-state model.
ReinaMacCredy/maestro 26
maestro:brainstorming Use before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
ReinaMacCredy/maestro 26
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
ReinaMacCredy/maestro 26
maestro:brainstorming Use before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
ReinaMacCredy/maestro 26
maestro:note Capture decisions, constraints, and context to persistent notepad. Priority notes are injected into every session and implementation run.
ReinaMacCredy/maestro 26
maestro:parallel-exploration Use when you need parallel, read-only exploration with task() (Scout fan-out)
ReinaMacCredy/maestro 26
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 fix strategies, and re-reviews until the plan passes with zero actionable issues. Use when the user says 'review the plan', 'deep review', 'check the plan thoroughly', 'review loop', 'validate before approving', or wants rigorous plan validation before execution. Also use proactively before plan-approve when the plan is complex or high-risk.
ReinaMacCredy/maestro 26
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.
ReinaMacCredy/maestro 26
commit Create a well-formed git commit from current changes using session history for rationale and summary; use when asked to commit, prepare a commit message, or finalize staged work.
ReinaMacCredy/maestro 26