Per-feature (or per-workstream) handover docs — not the project-wide overview in docs/handover/.
Pattern inspired by Millia’s docs/handoffs/ + feature branches: each meaningful slice of work gets a dated handoff on a sensible branch, so the next agent/human can pick up without re-deriving context.
| Kind | Branch | What lands |
|---|---|---|
| Docs / planning stream | docs/<topic>-handoffs |
One or more files under docs/handoffs/ |
| Feature implementation | feat/<issue>-<slug> or mvp/<issue>-<slug> |
Code plus an updated handoff for that issue |
| Quick spike | chore/<slug> |
Optional short docs/handoffs/YYYY-MM-DD-<slug>.md |
Examples: docs/mvp-handoffs, feat/75-policy-versioning, mvp/79-presidio-pii.
docs/handoffs/YYYY-MM-DD-<slug>.md
Use the template: _TEMPLATE.md.
- Starting a feature plan (MVP sub-issue or new epic slice) → create the handoff before large code moves
- After a mergeable chunk ships → update “What shipped” / “Open follow-ups”
- Closing an issue → handoff should say Done / residual debt
Agents: use project skill feature-plan (.agents/skills/feature-plan/ and .cursor/skills/feature-plan/).
| Date | Handoff | Branch / issue | Status |
|---|---|---|---|
| 2026-07-24 | stabilize-contracts-and-ci | dev / #61–#64, #73, #84 |
Done |
| 2026-07-24 | mvp-continuous-compliance-gate | docs/mvp-handoffs / #74 |
In progress |