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…

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…

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

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

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

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…

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…

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…

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

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…

Decision support and grounded teaching for the human. Invoke when the user signals a message didn't land ("wait, what?", "I don't understand", "explain it like I'm five", "which is better?", "I'm not sure") about a question or fork they've been asked, or when…

Diagnosis-only investigation of a failure with unknown cause — reproduce, localize, reduce, deliver root cause with evidence. Read-only; an explicit fix request routes by target and tier instead, never here.

Answer an evidence question without touching production code — research external facts against primary sources, build or iterate a disposable prototype (its own bugfixes included), or baseline current repository behavior before deciding or implementing. Use…

Compact the current conversation so another agent can pick the work up — into the active bundle's NOTES.md when one exists, or a standalone handoff document otherwise. Adapted from Matt Pocock's handoff.

Implement authorized Full-tier work from the bundle's SPEC.md, red-first at pre-agreed seams. Requires an explicit user request to implement or fix production code, and a SPEC whose red-test list covers this exact scope — post-ship review findings and…

Turn a decision the user can't fully answer into a Markdown questionnaire for the one person who can — filled in async, or together over a meeting. Adapted from Matt Pocock's to-questionnaire.

Settle the pre-spec unknowns that need a decision — interview the user on open forks, prototype feel-right design questions, sharpen the domain model, or chart an effort too big for one session. Use when an idea is still vague, options compete unchosen, the…

Turn the current conversation and codebase understanding into a work bundle with SPEC.md — synthesis of what is already known, interviewing only on material open forks. Use for unresolved ideas, requirements, sources, system maps, or plans.

Turn filed lessons into the smallest doctrine edit - group pending lessons by target, make one commit per target carrying their evidence ids, mark each lesson processed by that commit or answered with the reason it was rejected, and hand back for the…

Route work into the right maestro tier and drive the SPEC/NOTES/VERIFY bundle lifecycle - open, resume, close, recall.

Settle unknowns and lock decisions before implementation - recall past bundles, walk one fork at a time, record every settled choice with a rationale.

Verify and close - cross-check coverage, run the VERIFY table, deliver the verdict, harvest durable lessons into decisions, close the bundle, and never claim remote state from local evidence.

Drive one accepted implementation unit test-first - smallest falsifiable behavior, minimum edits, evidence that names the real falsifier.

Use the durable Irina Chief of Staff through the universal Irina CLI. Trigger when the owner asks to contact, open, inspect, or bootstrap Irina or Staff, or when governed Staff receives an IRINA_OWNER_INBOX_V1 doorbell.