Docs · skills/handoff-spec/templates/handoff.md

{Feature} — handoff

Design source: {link} · Prototype: {link} · Built against: {release / sprint} Walkthrough held: {date, attendees} · Office hours: {when}

What this is

{Two sentences: the job, and the metric from project-brief.md.}

Tokens

{Export link + the naming convention. Flag any token introduced by this work.}

New tokenValueTierWhy it was needed

Components

ComponentNew / changed / reusedStates deliveredOutstanding

Screens

For each screen: link, states delivered, focus order, accessible names, content source, and the rules below.

Behaviour rules

ConditionConsequence
Content column < 480pxThe rail collapses above the content
List exceeds 50 rowsPagination replaces infinite scroll

Data and failure

ScreenData neededSourceLatePartialAbsent

Accessibility

{Per-screen record from a11y-spec, plus the criterion-by-criterion checklist.}

Content

{Every string, at shipping length. Longest-case examples marked.}

Open questions for engineering

#QuestionOwnerNeeded by

Design QA

{Link to the filled qa-checklist.md. Sign-off happens on staging, before release.}

The method, written down

Every page here is one file from the skill library. The folder is loadable as a Claude project as-is.