fasalzein Handover
Write a handover document so a fresh agent can continue without replaying this conversation.
For wiki-forge projects, use wiki handover or wiki agent-handover to write the durable record under the configured Knowledge vault. Resolve the vault through KNOWLEDGE_VAULT_ROOT or wiki init <project> --repo <path>.
For standalone use, save to mktemp -t handover-XXXXXX.md.
What to include
- Current objective and next action.
- Relevant artifact paths: PRD, slice, commit, test, handover.
- Forge truth commands:
wiki checkpoint,wiki forge next,wiki forge status. - Ordered runbook commands for the next agent.
- Skills the next session should load.
- v2 command:
wiki handover <project> --repo <path> --json
Required skills block
The handover prompt must include:
Required skills before changing files:
- /wiki for vault memory, freshness, handover, and retrieval
- /forge for tracked lifecycle, phase packets, evidence, review, and close
- /handover when ending/transferring the session
What to exclude
- Prior conversation reconstruction.
- Broad wiki queries.
- Content already in other artifacts; reference by path instead.
Suggest skills for the next session. Return the CLI's copy/paste prompt to the user verbatim.
Forge integration
Load this skill when a Forge session is ending or transferring.
Use wiki handover/wiki agent-handover for durable records.
Include wiki forge next in the runbook.
After handover completes: return to /forge — run wiki forge next to advance.