The CRISP workflow

The core loop is five commands, used in order. Each one passes its output to the next.

/crisp-teach  →  /crisp-review  →  /crisp-audit  →  /feature-design  →  /handoff

The core loop

/crisp-teach: run once per project. Writes .crisp.md, the context file every later command reads.
/crisp-review: the quick check. A grade and the top three issues in thirty seconds, while you iterate.
/crisp-audit: the thorough check. Scores all five dimensions, rates each problem from P0 (critical) to P3 (minor) and gives a fix plan in priority order. Run it before anything ships.
/feature-design: for new work. Describe the problem and get user flows and component choices, with the reason for each.
/handoff: the last step. Turns a reviewed design into a spec developers can build from, with states, design tokens, edge cases and an accessibility checklist.

Before design: /crisp-brief turns a vague request into a clear brief. /crisp-research shows what competitors do and where the risks are.
While you evaluate: /crisp-ux-laws applies proven laws about how people think. /crisp-copy checks interface text against the Contextual and Intelligent dimensions.
Before you ship: /crisp-a11y checks WCAG 2.2 AA accessibility and gives exact code fixes. /crisp-design-eng checks motion and polish.
Special cases: /crisp-ai for AI features such as chat and agents. /crisp-redesign for updating an existing UI. /crisp-funnel when you need a built funnel, not a review.

Next: The five dimensions guide explains the standard every command checks against.