Turn an approved design into a build spec.

(What it does)

The bridge from approved design to build. /handoff turns a reviewed design into a complete developer spec: every component, every state of every element, design tokens and spacing, interactions with exact timings and easing curves, edge cases, an accessibility checklist, and every piece of copy written out in full. Nothing is left as "TBD".

The reasoning is simple: any state the spec leaves out, a developer will have to invent. That hands a design decision to someone who was never meant to make it. The spec removes the guesswork before any code is written.

(When to use it)

Use it once a design has passed review:

• A design has passed /crisp-audit or /crisp-review and is moving to build
• Work is going to another developer, a contractor, or an AI agent in a separate session
• A component keeps coming back from build with made-up empty states and missing error handling

(What you get)

• Every state of every component
• Token and spacing references
• Edge cases and error states
• Accessibility checklist

(Example output)

Illustrative example only. This is not a real audit.

(Every state, documented)

For each interactive element, the spec covers every state. The states most often missing from designs are the ones users hit at the worst moments:

• Default, hover, focus, active, and disabled
• Loading: skeleton, spinner, or optimistic update, and why
• Empty: never "No data available"
• Error: the exact message and how the user recovers
• Success: what confirms the action, and exactly what it did

(Common questions)

(Related skills)