handoff-context

Handoff Context

Do not ask for permission - execute immediately.

<context_handoff>

<original_task> [State the original, specific request or task] </original_task>

<decisions_made> [Architecture choices, tradeoffs accepted, approaches chosen — with the reason each was picked over alternatives. Prevents the next session from relitigating settled calls.]

• [decision] — reason: [why this over alternatives] </decisions_made>

<work_completed> [Every item here MUST include evidence. "Confirmed by: test passed / curl returned 200 / visible in Supabase / Postman response attached." Without evidence, move the item to work_remaining as "Attempted, unconfirmed: [what was tried and why verification was unclear]."]

• [thing that works] — confirmed by: [specific evidence] </work_completed>

<work_remaining> [Work that still needs to be done, in priority order. Distinct from blockers (these are doable now). Include "Attempted, unconfirmed: [description]" for work that was tried but whose completion couldn't be verified.] </work_remaining>

<failed_approaches> [Approaches tried that did NOT work. Pair each with the EXACT failure reason so the next session does not retry blindly. "Threw X error because Y" is useful; "didn't work" is not.]

• [approach tried] — failed because: [exact reason / error message] </failed_approaches>

<untried_approaches> [Promising ideas that have NOT yet been attempted. Distinct from failed — these are still open. Be specific enough that the next session knows exactly what to try.]

• [approach / idea] </untried_approaches>

• [blocker] — waiting on: [who/what] — unblocked when: [condition]

<critical_context> [Essential technical, project, and business context the next session needs but can't derive from the code. Git branch, env state, related PR numbers, stakeholder constraints, time-sensitive notes. Also include overall system state: services running or broken, migrations applied, feature flags set, env vars required.] </critical_context>

<exact_next_step> [The ONE most important action to take on resume. Precise enough that starting requires zero thinking. Singular and concrete, e.g., "In auth/login.ts line 42, add httpOnly flag to the session cookie configuration, then test with curl to verify the Set-Cookie header includes HttpOnly."] </exact_next_step>

</context_handoff>

</handoff-format>

<honesty-requirement>
Write "N/A" or "None" in sections that genuinely have no content — incomplete is worse
than honest empty. Skipping a section is indistinguishable from forgetting to fill it,
which leaves the next session guessing. An empty `<blockers>None</blockers>` is a
positive signal; a missing `<blockers>` tag is ambiguous.

If `work_completed` has no evidence-backed items yet, write "Nothing confirmed working
yet — all approaches still in progress or untested."
</honesty-requirement>