design-handoff

# design-handoff ## Language Rule Follow an explicit artifact or audience language when provided. Otherwise, write the handoff and user-facing report in the conversation language according to `<agent-home>/roles/response-policy.md`. Preserve code, paths, commands, component names, token names, and native format IDs. ## Resolve and Check State Find `design_state.yaml` for the design. - Require `phases.review: done`. - When `--intensity quick` explicitly skipped review, accept `phases.components: done` instead. - Refuse handoff when review status is `failed`; report the blocking findings and recommend returning to the owning design stage. ## Procedure ### Step 1: Inventory Deliverables Collect: - `02_tokens/tokens.md` and the actual generated token-file paths - the complete `03_components/` inventory - the required standalone preview and validated screenshot: - `ui`, `webapp`, `icon`, or `diagram` → `03_components/preview.html` - `slide` → `03_components/slides/slides.html` - accepted issues from `04_review/critique.md` Place the browser-openable preview at the top of the handoff. The only preview exception is a paper architecture figure intentionally handed to the user as a PPTX/layout workflow rather than generated as a final render. ### Step 1.5: Export Delivery Formats When the request and scope need formats beyond the browser preview, use the converter provided by the active adapter or tool projection. Its interface is: ```bash node <design-converter>/conv...