domains / families / software-engineering / handoff-spec

handoff-spec

combined

Write the implementation handoff — measurements, behaviours, assets, states, and edge cases. Use when engineering picks up the work. For verifying the result afterwards use `design-qa-checklist`; for reusable library components use `component-spec` (design-systems). Hand a spec that is mid-implementation to another machine or another agent.

When to use

• Writing implementation handoff documents
• Documenting visual and interaction specifications
• Specifying content, assets, and edge cases
• Handing off mid-implementation specs to another agent
• Recording decisions and current work status
• Documenting unpushed branches and local state

When not to use

• Verifying the result afterwards
• Creating reusable library components

Skill page

Conflict

The two copies use the same name for two different tasks. The dzhng/skills copy is a procedure for updating a living spec so a cold agent on another machine can continue mid-implementation work. The Owl-Listener copy is a template for a design-to-engineering handoff document containing visual, interaction, content, asset, and edge-case specifications. They overlap only in the broad idea of handing off work, but each contains material steps and constraints the other lacks, so crowning one would hide a real alternative.