yyqqCoding Handoff
Capture the minimum durable state another session needs to continue safely.
Gather current facts
- Re-read version-control status and relevant diff.
- Read the authoritative requirement/design documents.
- Check the latest verification output rather than relying on memory.
- Identify blockers, unresolved decisions, and unrelated work that must be preserved.
Produce the handoff
Before returning, verify that all eight items below are explicit. State None for an empty category rather than omitting it, especially blockers, unresolved decisions, and unrelated changes.
Include:
- Objective and accepted behavior
- Current implementation state
- Key files and authoritative documents
- Decisions already made and their reasons
- Commands run and their latest results
- Remaining tasks in dependency order
- Known risks, blockers, and unverified areas
- Version-control state and unrelated changes to preserve
References support the handoff facts; they do not replace them. Briefly summarize each existing decision and its reason even when linking the source, and reference existing documents, commits, diffs, and test output instead of copying their full contents.
Write to the requested path when one is provided. Otherwise return the handoff in the response without creating a repository file silently.