Handoff

Capture the context a fresh agent needs to continue without re-asking, re-discovering, or repeating mistakes.

Core Principles

1. Describe state. Write "Auth is implemented; logout is not started," not "Implement logout next." The next agent chooses actions from the context.
2. Link existing artifacts. Reference PRDs, plans, ADRs, issues, commits, diffs, and design docs by path or URL instead of copying their content.
3. Preserve why. Capture decisions, rejected approaches, and failures that code alone cannot explain.
4. Require verification. Present claims as context to check against the actual code, not facts to trust blindly.
5. Redact secrets and PII. Never include keys, tokens, passwords, or personal data. Name credential locations (e.g. ".env.local, not committed"), never values.
6. Keep only useful context. Omit obvious, redundant, or explanatory material recoverable from code or project configuration.

Procedure

1. Read existing project instructions (AGENTS.md or equivalent). Keep the handoff session-specific; do not repeat those instructions.
2. Read and update any prior handoff instead of starting from scratch.
3. Treat user-supplied arguments as the next session's focus.
4. Fill every template section; mark empty sections None.
5. Output the handoff in one fenced code block and save the same content as described under File Output.

Output Format

Use this template inside a single fenced code block:

# HANDOFF: <short title of the work>
Generated: <timestamp> · Session focus: <one line>

## 1. Goal
<The overall objective in 1, 3 sentences.>

## 2. Why This Matters / Background
<Motivation, intended users, timing, constraints, and hard requirements not already in project configuration.>