Use when running /decide, or whenever a product/technical decision changes something already written (a spec, plan, architecture doc) mid-work — captures it as an ADR and finds what needs to be updated downstream. Philosophy adapted from GitHub Spec-Kit's ADR…
Use when running /spec:plan, after a Specification.md exists and before task breakdown — turns approved requirements into a technical approach, file structure, and testing strategy. Philosophy adapted from GitHub Spec-Kit's plan phase and BMAD-METHOD's…
Use when running /engineering:review, or whenever asked to review a diff or PR for bugs and spec/constitution adherence. If the host project already has Anthropic's official code-review plugin configured, prefer that instead. Philosophy adapted from…
Use when running /spec:spec, or whenever turning a raw feature idea into a written specification — before any implementation planning or code. Philosophy adapted from GitHub Spec-Kit's spec-driven development approach.
Use when implementing any feature or bugfix, before writing any implementation code. Triggered by /engineering:implement and /engineering:test. Philosophy adapted from Superpowers and Matt Pocock's skills repo TDD discipline.
Use when running /business:vision, or whenever capturing a product's problem, target users, and success criteria at the highest level, before any PRD or feature work. Philosophy adapted from BMAD-METHOD's Analyst-stage discovery.
Use when running /business:architecture, after a PRD exists — documents the current-state whole-system architecture. Philosophy adapted from BMAD-METHOD's Architect-stage documentation-first approach.
Use when running /business:persona, or whenever defining a user persona that later UX work (journeys, wireframes) will reference. Philosophy adapted from BMAD-METHOD's discovery stage and the toolkit's UX extension.