Sponsored by

Find leads on Reddit on auto pilot

Topic: plugin

507 skills in this topic.

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 that upgrades prompts before execution.
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: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.
ReinaMacCredy/maestro 26
maestro:dispatching Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
ReinaMacCredy/maestro 26
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: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.
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:revert Git-aware revert of track, phase, or individual task. Safely undoes implementation with plan state rollback.
ReinaMacCredy/maestro 26
maestro:review Code review for a track against its spec and plan. Verifies implementation matches requirements, checks code quality and security.
ReinaMacCredy/maestro 26
maestro:setup Scaffolds project context (product, tech stack, coding guidelines, product guidelines, workflow) and initializes track registry. Use for first-time project onboarding.
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
debug Investigate stuck runs and execution failures by tracing Symphony and Codex logs with issue/session identifiers; use when runs stall, retry repeatedly, or fail unexpectedly.
ReinaMacCredy/maestro 26
land Land a PR by monitoring conflicts, resolving them, waiting for checks, and squash-merging when green; use when asked to land, merge, or shepherd a PR to completion.
ReinaMacCredy/maestro 26
linear Use Symphony's `linear_graphql` client tool for raw Linear GraphQL operations such as comment editing and upload flows.
ReinaMacCredy/maestro 26
pull Pull latest origin/main into the current local branch and resolve merge conflicts (aka update-branch). Use when Codex needs to sync a feature branch with origin, perform a merge-based update (not rebase), and guide conflict resolution best practices.
ReinaMacCredy/maestro 26
push Push current branch changes to origin and create or update the corresponding pull request; use when asked to push, publish updates, or create pull request.
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
bug-fix Bug-fix pipeline. Dual RCA (Sonnet+Opus) -> Consolidation -> Codex Validation -> Implementation -> Code Review.
Z-M-Huang/claude-codex 24
multi-ai Start the multi-AI pipeline. Plan -> Review -> Implement (loop until reviews approve). Codex final gate.
Z-M-Huang/claude-codex 24