Reference — generated from the toolkit
Source of truth: toolkit/templates/design-handoff-pack.md. Edit it there; this page is regenerated on build.
Design handoff pack — {product / feature name}
- Owner (Design): … Version: 0.1.0
- PFD: {link, version} Design Review gate: pending | passed {date}
Checklist (Design DoD)
- Flows approved — every PFD scenario covered, including error and empty states (ux-flow per flow).
- Data model passed Data + Security review — PII/sensitivity tagged, retention noted, ACORD-aligned where relevant (data-model).
- Screen specs complete with full state matrix — default, loading, empty, error, denied (screen-spec).
- Component mapping — every screen element maps to a named design-system component and tokens; no raw hex/px.
- Prototype link recorded and marked throwaway (validation only — never a Build input).
- SME sign-off on flows recorded (SME design validation).
- Open questions triaged; zero blocking.
- Traceability matrix complete (below) — no PFD scenario without a flow and screen.
Links table
| Artefact | Link | Version | Approved by | Date |
|---|---|---|---|---|
| PFD | … | … | PO (gate) | … |
| UX flows | … | … | Product + Design + SME | … |
| Data model | … | … | Data + Security | … |
| Screen specs | … | … | Design | … |
| Component mapping / tokens | … | … | Design | … |
| Prototype (throwaway) | … | … | — (validation evidence only) | … |
| Glossary (pinned version) | … | … | SME | … |
PFD → flow → screen traceability matrix
Every PFD scenario/AC appears exactly once; a gap in any column is a Design Review blocker.
| PFD scenario / AC | UX flow | Screen(s) | States covered | Notes |
|---|---|---|---|---|
| {AC-001 — …} | {flow-name} | {screen-a}, {screen-b} | default, error, empty | … |
| {AC-002 — …} | … | … | … | … |
Open questions carried into Build
Non-blocking only. Each with owner and a date — an open question without an owner is a future defect.
| # | Question | Owner | Needed by |
|---|---|---|---|
| 1 | … | … | … |
The merge
Raise the pack as a PR into the product repo's design directory. Reviewers = the Design Review gate signatories; their approvals are the sign-off record. Once merged, Build agents consume these artefacts as context — any later design change is a new PR against the pack, not a side-channel conversation.