Handoff notes that survive the first pull request

Specs crumble when they live only in chat. We walk through a durable structure for comments, acceptance criteria, and open questions.

Specification & Developer Handoff emphasises artefacts engineers can search later. That means linking behaviours to ticket IDs, tagging open questions with owners, and separating “must ship” from “nice if bandwidth appears.”

Students practise rewriting vague adjectives—“snappy,” “subtle”—into observable cues: duration ranges, easing references, focus order. We also rehearse what to do when the design file changes mid-sprint: version notes, diff summaries, and a standing invite to a short async review.

None of this replaces conversation; it makes conversation efficient. When a developer opens a spec at 21:45, they should see the same story the designer told on Tuesday morning.