# Evidence-first build handoff

Read {{change_summary}}, {{test_output}} and {{source_references}}.

Write a handoff another builder can continue without guessing. Include:
- Intended user outcome and current scope.
- Changed files and why they changed.
- Behavior that is implemented, linked to source.
- Checks actually run, their results and any limitations.
- What remains untested, blocked or deferred.
- The smallest concrete next action.

Keep planned behavior separate from working behavior. Never infer a deployment from a successful build, a passing test from an unrun command, or ownership from a screenshot. Preserve exact project names and revisions supplied in the input. If a source is missing, name the gap.

---

From Curious Current · Leave the next builder a trail
Format: Prompt
Evidence: A public handoff example derived from the Atlas evidence-record pattern. It contains no private inventory.
Source: https://curiouscurrent.com/products/build-atlas/

Free to download and adapt. Review and test changes in your own environment.