# Design-to-implementation handoff checklist

Reusable template. A checked box needs a linked artifact, test result or explicit reviewer decision. This checklist is not itself permission to edit a repository, install software, publish, or delete anything.

## Scope and evidence

- [ ] Product, intended users and primary task named.
- [ ] New build versus redesign specified; preserved functionality listed.
- [ ] Source inventory contains only authorized, relevant inputs.
- [ ] Each decision has an ID, status, rationale and source.
- [ ] Status distinguishes approved, proposed, inferred and verified; a confidence score is not approval.
- [ ] Conflicts and unresolved questions are visible, with their implementation impact.
- [ ] Work allowed now and work requiring separate approval are explicit.

## Core package

- [ ] README identifies entry point, scope, package version and open questions.
- [ ] DECISIONS records approved behavior and the decisions still outstanding.
- [ ] DESIGN specifies typography, layout, themes and responsive behavior without silently inventing values.
- [ ] Assets have intended use, source, licensing/redistribution status and version references.
- [ ] One canonical token source generates any additional formats; cross-format consistency is tested.
- [ ] SURFACES lists applicable screens, components and states with stable identifiers.
- [ ] ACCEPTANCE links each criterion to a surface and decision; tests distinguish visual from behavioral evidence.
- [ ] MANIFEST lists real, resolvable files and their roles.

## Applicable behavior

- [ ] Loading, empty, error, unauthorized and success states are specified where applicable.
- [ ] Forms define validation, input preservation, confirmation and recovery where applicable.
- [ ] Keyboard navigation, focus, semantic names and reduced-motion behavior are specified.
- [ ] Authorization and sensitive-data handling are explicit for protected features.
- [ ] Collections, exports, audit trails and complex search are optional modules, not automatic requirements.
- [ ] Not-applicable items have a rationale rather than being silently omitted.

## Verification and handoff

- [ ] Referenced assets and links resolve from the intended delivery location.
- [ ] Rendering checked at representative sizes with realistic content.
- [ ] Font availability and image loading verified; fallbacks documented.
- [ ] Every claim of working behavior has an executed check, not merely a screenshot.
- [ ] Offline capability tested with networking disabled if it is a requirement; otherwise no offline claim.
- [ ] Remaining tests have honest not-run or blocked status and next steps.
- [ ] Reviewer approves the exact package revision before implementation begins.
- [ ] Previous package retained; recovery/reversion plan scoped to this work only.

## Decision row template

| ID | Decision | Status | Source/evidence | Acceptance check | Open issue |
|---|---|---|---|---|---|
| DEC-001 | Replace with a concrete decision | proposed | Add authorized source | Add observable pass/fail condition | None or named gap |

## Review record

- Package revision:
- Reviewer:
- Review date:
- Approved scope:
- Deferred scope:
- Checks executed and results:
- Checks not run and why:

Completing this checklist supports a handoff review; it does not by itself prove production readiness.