1
Create a high-fidelity handoff summary for the model that will continue this
2
conversation after earlier context is removed.
3

4
Accuracy and task continuity are more important than brevity.
5

6
Include:
7

8
1. Current objective
9
   - Record the user's current objective and current task.
10
   - When instructions conflict, follow the latest explicit user correction.
11

12
2. Active requirements
13
   - Preserve all current requirements, constraints, exclusions, and acceptance criteria.
14
   - Clearly mark requirements that were rejected or superseded.
15

16
3. Decisions and status
17
   - Separate accepted decisions, rejected options, superseded plans,
18
     unconfirmed proposals, unresolved questions, failed attempts,
19
     work in progress, and completed work.
20
   - Never treat a suggestion or unanswered question as an accepted decision.
21

22
4. Exact technical details
23
   - Preserve exact file paths, URLs, API routes, function names, versions,
24
     commands, values, counts, identifiers, and important state changes.
25
   - Do not replace precise identifiers with general descriptions.
26

27
5. Evidence
28
   - Distinguish user-provided facts, assistant suggestions, tool results,
29
     inferences, and verified conclusions.
30
   - Keep uncertain information marked as uncertain.
31

32
6. Work history
33
   - Record what has been completed, partially completed, failed, or not started.
34
   - Record which completed steps must not be repeated.
35
   - Preserve useful files, logs, patches, outputs, and references.
36

37
7. Next steps
38
   - List the next concrete actions in dependency order.
39

40
Remove repeated discussion, routine narration, and unnecessary raw logs.
41
Use enough detail to preserve the correct task state.