roborew/handoff

Write a handoff document summarising the current conversation so a fresh agent can continue the work.

Output path

Persist the handoff document using bash (preferred when your agent has bash: true):

1. HANDOFF_PATH=$(mktemp -t handoff-XXXXXX.md) — capture the path.
2. Write the full document with a shell redirect or tee (heredoc / printf) to "$HANDOFF_PATH".
3. Echo the path in your completion message.

Orchestrate agent has bash: false — do not rely on mktemp. Either output the full handoff markdown in your reply for the user to save manually, or Task developer once with explicit instructions: create file only at a user-approved path under the workspace (e.g. .plan/handoff-<date>.md) using the write tool — then scribe is not required for .plan/*.md... actually developer writes code - developer can write .plan/handoff-notes.md if we allow - .plan/*.md is allowed for scribe; developer has write. Simplest for orchestrate: return the handoff body in chat and tell the user to save to a file or switch to architect to run handoff with bash.

Architect has bash: true and no direct write — use the bash + mktemp method above.

Content

• Current goal, blockers, and next concrete action (one sentence).
• Active artifact path(s): .plan/<type>.<slug>.md if any.
• Pointers only — do not duplicate full plan bodies, CONTEXT.md, ADRs, or long transcripts. Reference paths and URLs.
• Environment notes if relevant (branch, failing command, last error line).
• Suggest which skills the next session should load (e.g. grill-me, architect-plan, orchestrate-execution, debug-fix).

If the user passed arguments (or the hint), treat them as what the next session should focus on and tailor the doc accordingly.