ReinaMacCredy

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

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

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

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 multi-component systems, regulated domains, or unclear requirements.

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

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

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.

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.

UI/UX design intelligence with searchable database

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.

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

Deep investigation mode. Gather context, analyze, synthesize recommendations without making code changes.

Fetch up-to-date library documentation via Context7 MCP. Use when working with external libraries, APIs, or frameworks.

Start interview-driven planning with Prometheus. Asks clarifying questions before generating implementation plan.

Diagnose and fix Maestro installation issues

Git worktree isolation for parallel plan execution. Creates isolated working directories so multiple plans can execute simultaneously without conflicts.

Isolated Codex goal-loop skill that combines spec-to-plan, goal-loop-native phase planning, and gated phase-by-phase execution. Use when the user asks to turn a spec into a goal-loop plan, run a goal-loop plan, or package the spec-to-goal-plan, goal-loop-planner, and goal-loop flow as one Codex skill. Planner work uses GPT-5.4 high, implementation and gate-fix subagents use model 5.5 high, and review gates use model 5.4.

Autonomous phase-by-phase plan execution loop. Plan-subagent decomposes each phase into a dependency-tagged wave graph, parallel Opus sub-agents implement via the inlined orchestrator pattern (main thread plans/synthesizes, sub-agents do all edits), advisor + /code-review --effort extra-high + the inlined review-swarm protocol gate every phase, IMPLEMENTATION_NOTES.md captures off-spec decisions. Self-contained — orchestrator and review-swarm protocols ship inline as references, no third-party skill dependencies. Use when the user invokes /goal-loop <plan-path>, when /goal hook fires with a goal-loop directive, or when the user wants autonomous phase-by-phase execution of a markdown plan file. Pairs with goal-distill (which produces compatible plan prompts).

Distill the current session — conversation, decisions, corrections, repo state, and recent history — into a single paste-ready /goal prompt that drives an autonomous phase-by-phase loop (decompose → Plan-subagent on Opus → main-thread execute → re-measure → repeat) until the success criterion is met or a stop condition fires. Universal — works in any repo, writes no files. Copies the prompt to the clipboard on macOS. Use this whenever the user says "distill goal", "distill this session", "goal-distill", "reconstruct goal", "rebuild the spec", "rebuild the masterplan", "give me a /goal", "phase-by-phase to the goal", "loop until done", "iterate toward the goal", or "turn this into a /goal prompt I can paste later" — and prefer it even when the user doesn't name the skill but clearly wants this session compressed into a runnable prompt for a future agent.

Deep strategic analysis of a project to identify the single highest-leverage, most innovative addition. Use this whenever the user asks what to build next, what the most impactful improvement would be, what the "next big thing" is for their project, what's the smartest thing to add, or any question about strategic direction and priorities. Also trigger when the user seems stuck choosing between competing features, is evaluating what matters most, or asks open-ended questions like "what would you do with this project?" or "what am I missing?"

Enter orchestration-only mode where Claude plans, delegates to sub-agents, and synthesizes results instead of implementing directly. Use whenever the user says they want to act as tech lead, wants Claude to orchestrate, wants sub-agents to do the work, says things like "you orchestrate, I brainstorm", "don't code yourself", "delegate this", "break this up and dispatch it", or explicitly invokes /orchestrator. Also use when the user frames the session as brainstorming-to-spec-to-delegation and wants Claude to stay out of the implementation seat.

Parallel read-only multi-agent root-cause investigation for bugs, regressions, crashes, flaky behavior, or unexplained failures. Use when the user asks to investigate a bug, find the root cause, trace a regression, understand why something broke, or wants a ranked diagnosis with the fastest proof path without making code edits.

Parallel read-only multi-agent review of a current git diff or explicit file scope to find behavioral regressions, security or privacy risks, performance or reliability issues, and contract or test coverage gaps. Use when the user asks for a review swarm, parallel review, diff review, regression review, security review, or wants high-signal issues plus a prioritized fix path without editing files.

Generate beautiful, self-contained HTML pages that visually explain systems, code changes, plans, and data — including interactive Mermaid diagrams with auto-playing source→target flow animation, hover-to-trace the full upstream+downstream chain, and tap-to-pin a node + open its detail panel. Use when the user asks for a diagram, architecture overview, diff review, plan review, project recap, comparison table, or any visual explanation of technical concepts. Also use proactively when you are about to render a complex ASCII table (4+ rows or 3+ columns) — present it as a styled HTML page instead.

Pre-design research for Maestro cards: creates or validates a same-card research.md receipt, maps context, stakeholders, hosting, unknowns, and the first design fork. Use before maestro-design when the user brings a new idea, zero-context feature, external/pasted plan, unfamiliar domain, stakeholder-heavy request, hosting-unclear work, or when research is missing, stale, skipped-risky, or needed for READY_FOR_DESIGN.

Witness feature close: use after Maestro feature proof and QA pass, before feature close, to write current witness.md/advisor.md receipts, auto-invoke an independent advisor when allowed, apply risk-tier and human-demo policy, and emit Gate: APPROVED.

Card work in a project using Maestro after design approval: use for implement, fix, verify, QA, close, release, continue, or unattended prompts like use loop, keep looping, work while away/asleep.

Audit a project using Maestro read-only: use for code review, architecture review, deepening opportunities, backlog proposals, harness-improvement findings, or repo-wide improvement audits without fixes.

Design in a project using Maestro before implementation: use for brainstorm, plan, PRD synthesis, grilling/stress-test, domain model, deepening candidate, wording, workflow, skill/harness, card/task/feature, architecture, UX, or agent-process decisions.

Router for choosing the next Maestro skill or lifecycle recipe.

Setup Maestro in a project using or adopting Maestro: use for init/install/sync/doctor, global skills, hooks, harness setup, or agent integration diagnosis/repair.

Update repository documentation to match the current state of the codebase. Local replacement for the remote /docs command (which needs the Claude GitHub app). Use when the user says /docs, "update the docs", "sync the README", "document this feature", or asks you to refresh docs to reflect current code. Works inline in the current session and edits files in the working tree.