# Specification handoff

Blank working document. Replace placeholders with your own evidence; an empty field is unknown, not a passing result.

Owner: [fill in]
Source revision: [fill in]
Environment: [fill in]
Evidence date: [fill in]

## Decision context

Agreed task: ___
Source revision: ___
Decision records: ___
Explicit non-goals: ___

## Acceptance map

| Requirement | Observable case | Source decision | Open question |
| --- | --- | --- | --- |
| ___ | ___ | ___ | ___ |

## Architecture

Files/interfaces affected: ___
Invariants to preserve: ___
Dependency seams: ___
Implementation order: ___

## Handoff

Local specification path: ___
Blocking decisions/owners: ___
Tracker destination, if authorised: ___
Changes to setup/configuration: ___

## Boundaries

- The to-spec skill synthesises an existing discussion; it does not replace requirements discovery. Its configured tracker can publish issues and labels.

- The architect proposes a design without executing it. Older model/tool names need host adaptation, and a readiness label is not implementation evidence.

Workflow: https://undominated.ai/workflows/#turn-a-decision-into-a-spec

Original worksheet: MIT. Linked resources retain their own licences and setup requirements.