Release Patch
Use when releasing a patch on any project — auto-detects the manifest (plugin / npm / python / cargo / go / flat), or falls back to a changelog-only entry when no manifest exists; bumps the PATCH version, prepends a CHANGELOG entry, then HARD STOPS before push. Skips the bump entirely if only docs changed. Never runs git push; emits a ready-to-push message and exits. Self-contained.
Refactor Advisor
Use when code has become hard to change — surface deepening opportunities that turn shallow modules into deep ones (small interface, lots of behaviour) for testability and AI-navigability. Informed by the domain glossary (CONTEXT.md) and ADRs. Do not use to debug a failure (use /diagnose) or to build new behaviour (use /tdd); this finds and designs refactors, it doesn't chase bugs.
Council
Run a high-stakes, hard-to-reverse, or ambiguous decision through a council of 5 AI advisors who independently analyze it, peer-review each other anonymously, and synthesize a final verdict to a lean verdict-<slug>.md. The opt-in decision aid for genuinely hard forks — the pressure-test before an ADR (DOCS_Guide §4) or a G2 design call. Based on Karpathy's LLM Council. Uses sub-agents (≈11 model…
Triage
Use when the existing backlog needs grooming — re-prioritising tasks, flagging stale/duplicate/conflicting items, marking what is ready vs blocked vs needs-info, and routing rejected work out of scope. Operates on TODO.md Backlog only, never the Active Sprint. Do not use to create new tasks (use /task-decomposer) or to form a sprint from the groomed backlog (use /lean-doc-generator promote).
Handoff
Use when ending a session mid-work and a fresh agent (or future you) needs to pick it up — context budget running out, a task blocked, or a deliberate stop. Compacts the live conversation into a handoff document saved to the OS temp dir, with a suggested-skills section and references to durable artifacts. Do not use to record durable project state — that is /lean-doc-generator close (sprint recor…
Task Decomposer
Use when converting a freeform feature request, ticket URL, PRD, or epic into structured TASK-NNN entries in TODO.md. Enforces an assumption registry, risk scoring, vertical-slice granularity, and validation before writing. Self-contained, no specialist agents. Do not use when a task already exists and is ready to build — use /orchestrator instead.
Prime
Use when starting a new session and want to load project context in a deterministic order — CLAUDE.md, CONTEXT.md, README, MEMORY index, active sprint, ARCHITECTURE map. Emits a health check showing which files were found versus missing. Everything degrades gracefully; nothing aborts. Do not use for mid-session orientation — re-read the specific file instead.
Diagnose
Use when debugging a defect, unexpected behaviour, failing test, or performance regression. Runs a disciplined 6-phase loop — build a feedback loop, reproduce, hypothesise, instrument, fix with regression test, cleanup + post-mortem. Do not use for architectural analysis or planning — use /orchestrator mvp instead.
Insights
Use to capture a friction, surprise, or insight as a learning the MOMENT you hit it — mid-work, in quick-mode, or any time a Sprint-Close Retro is too far off. Appends an L-NNN candidate to docs/LEARNINGS.md, or bumps a matching entry's count (which feeds the count≥2 promotion). Complements the Sprint-Close Retro; does not replace it. Do not use for durable project state (a commit / sprint record…
Flow
Conduct the full lean-flow loop end-to-end — assess context, ensure a backlog and sprint exist, build through the gates with the right per-task technique, then close with governance. The opt-in conductor: it sequences the standalone skills as stages and enforces the gates/governance, but never auto-approves a human gate. Use when you want the disciplined workflow run for you; use the individual s…
Lean Doc Generator
Use when creating, updating, or reviewing technical documentation, ADRs, sprint files, or AI-context files; running the sprint lifecycle (promote / execute / close); or **migrating existing docs** (dev-flow / adlc-flow / any layout) into the lean-flow standard. Follows the LEAN DOCUMENTATION STANDARD — WHY and WHERE only, never HOW. Bundles its own templates + standard, so generated docs match a…
Orchestrator
Use when starting, resuming, or completing any development task or sprint. Drives a gate-driven loop — quick, mvp, and sprint-bulk modes — with a G1 Scope gate and a G2 Design gate before any commit. Self-contained, no specialist agents. Do not use for debugging — use /diagnose; or for converting raw intent into tasks — use /task-decomposer.
Prototype
Use when a design question needs to be felt before committing — sanity-check a state machine / data model / API shape, or mock up a few UI options. Builds throwaway code that answers ONE question, then captures the answer and is deleted. Routes to a terminal logic prototype or web UI variants. Do not use to build the real thing (use /tdd) or to debug (use /diagnose).
Tdd
Use when building NEW testable behavior test-first — feature work, business logic, an API surface, a tool wrapper. Runs behaviour-driven red-green-refactor in vertical slices (tracer bullet, then one test → one implementation → repeat). Do not use to debug an existing failure or fix a bug — use /diagnose (it already writes the regression test first). Not for docs, config, or throwaway spikes.