| name | handover |
| description | Create a context packet and continuation prompt to continue with the next phase in a slice (or audit & close). Use whenever a phase is completed and a fresh agent would more efficiently continue. |
Handover
Write .doctrine/slice/<nnn>/handover.md — the disposable, gitignored "start
here" for the agent picking up the next phase. It is scaffolding for the next
session, not a durable record: durable facts live in design.md / plan.toml /
notes.md / doc/memories/; the handover only points at them and frames the
immediate work.
When to use
- Closing out a phase, before the next agent starts.
- The current
handover.md (if it exists) targets a phase that is now done.
TODO
Shape (sections to emit)
- Where this is — phase status ladder + commit refs; what is DONE, what is now.
- The gate —
no code without an approved plan; first action is the phase sheet.
- Read before you plan — pointers to design/plan/notes + key source
file:lines.
- What the last phase built — the surface to ride, not refork.
- Next-phase scope — EX/VT restated, plus watch-outs and any seam decisions.
- Immediate next actions — the literal
doctrine slice phase … in_progress
command, fill the sheet, TDD, commit, flip completed.
- Environment notes — build/gate/lint specifics; pre-existing dirty files to leave.
- Artifacts / pointers — scope / design / plan / notes / specs.
Rules
- handover is gitignored + will be deleted — never put the only copy of a durable fact here.
- Link to durable artifacts, don't repeat their contents.
- Supersede stale notes explicitly; do not leave contradictory guidance.
- Terse. Fragments fine. Reader is an agent, not human reviewer.
