Session Handoff

Use this prompt before changing agents or starting a fresh session on a long task. Save the resulting note in the project’s agreed location, then have the next agent verify it against the working tree. The durable progress and decision record adapts the approach in Codex execution plans.

Write a concise handoff for the next coding session. Use repository-relative
paths and sanitized command results. Do not include secrets, private storage
paths, individual-level records, or sensitive logs.

## Objective and acceptance criteria
- User's requested outcome: [goal]
- Done means: [observable behavior and required checks]
- Constraints and out-of-scope work: [scope and applicable instructions]

## Current state
- Branch/worktree identifier, if available: [identifier]
- Files changed and purpose: [paths and short explanation]
- Existing user or other agent changes to preserve: [paths/context]
- Completed work: [implemented behavior]
- Incomplete work: [remaining behavior; do not imply it is finished]

## Method and decisions
- Agreed method, definitions, units, and missingness rules: [details]
- Decisions and reasons: [include rejected options only when useful]
- Evidence: [source links or repository paths; versions when verified]
- Assumptions that still need validation: [specific uncertainties]

## Verification evidence
- Working directory: [repository-relative location]
- Commands actually run: [exact commands]
- Results: [pass/fail, relevant output, and scope of verification]
- Checks not run and why: [specific limits]
- Known failures: [reproduction command and current explanation]

## Next actions
1. Read the applicable AGENTS.md and inspect git status and the current diff.
2. Verify this handoff against the files; treat stale notes as context, not proof.
3. Continue with: [smallest next action and owned files]
4. Run: [next validation command and expected result]

## Stop conditions and final report
- Unresolved decision or blocker: [what needs a decision, if anything]
- Pause affected work if proceeding would invent a method, overwrite others'
  work, access protected data, or exceed the user's authorization.
- At completion, report the actual changes, checks and results, and any
  remaining limitations against the original acceptance criteria.