The CRISP workflow
The core loop is five commands, in order. Each one hands its output to the next.
/crisp-teach → /crisp-review → /crisp-audit → /feature-design → /handoff
The core loop
- /crisp-teach — once per project. Writes
.crisp.md, the context every later command reads. - /crisp-review — the fast loop. A grade and the top three issues in thirty seconds, while you iterate.
- /crisp-audit — the thorough pass. All five dimensions, P0–P3 severity, a prioritised action plan. Run it before anything ships.
- /feature-design — for new work. A problem statement in, user flows and component decisions with rationale out.
- /handoff — the exit. Turns a reviewed design into a developer-ready specification with states, tokens, edge cases, and an accessibility checklist.
Where the specialists slot in
- Before design: /crisp-brief scopes a vague request; /crisp-research surfaces competitive patterns and risks.
- During evaluation: /crisp-ux-laws applies cognitive laws; /crisp-copy holds the microcopy to Contextual and Intelligent.
- Before shipping: /crisp-a11y scores WCAG 2.2 AA with code-level fixes; /crisp-design-eng governs motion and polish.
- Special surfaces: /crisp-ai for AI-native UI; /crisp-redesign for existing UIs; /crisp-funnel when the deliverable is a funnel, not a verdict.
Next: The five dimensions — the standard every command evaluates against.