acceptance-storiesDecompose a written SPEC into discrete user stories, each carrying acceptance criteria and concrete test scenarios, cross-linked back to the spec and the assumptions it depends on. Use after a spec exists and has been assumption-audited, before implementation, to turn "what the system should do" int
assumption-auditExtract every premise a spec takes for granted, rank by cost-if-false, and write ASSUMPTIONS.md. Run as a fresh instance with the spec as the only input, before implementation. Use after a spec or PRP is drafted.
bug-investigationInvestigate observed wrong behavior, reproduce-first, and record the understanding (ruled-out hypotheses, root cause) — not just the diff. Use when starting any non-trivial bug, as distinct from implementing a spec item.
calibrateReason under uncertainty by tracking graded confidence and updating it on evidence. Use when diagnosing a bug, choosing between approaches, estimating risk, or deciding whether to gather more information before acting — anytime a belief is uncertain and tool calls can sharpen it. Trigger on "diagnos
design-interviewElicit a spec by interviewing the user as a domain expert, then draft SPEC.md / PRPs from their answers. Use at the start of a new project or feature, before any implementation, when requirements are not yet written down.
entropy-passRun a deletion-only refactor session — remove code, consolidate duplicates, reduce special cases, with zero new behavior and all validation gates passing. Also prune the journals. Use on a cadence (e.g. every N PRPs) or when entropy has accumulated.
fit-reviewReview a working change for approach-fit — was the bug fixed, or the feature built, the right way *for this codebase*? Catches reinvention of existing code, silently broken contracts, symptom-not-cause fixes, unbidden abstraction, and incoherence with local patterns. For bugfixes, verifies the bug i
project-docs-initScaffold the four durable workflow artifacts (SPEC, ASSUMPTIONS, DECISIONS, LESSONS), seeding the SPEC framing from the project where it can be discovered. Use when the user asks to initialize, scaffold, or set up the project's durable workflow docs.
session-retrospectiveRun the end-of-session distillation by hand — capture dead ends in LESSONS.md and non-obvious choices in DECISIONS.md. Use before wrapping up a session, or when the Stop-hook distillation prompt fires.
spikeBuild a throwaway implementation whose only purpose is to validate or falsify one high-risk assumption by making real contact with the data, library, or environment. Use for any high-cost unvalidated assumption before committing to the design.