1  # What to include
 2  
 3  Use these section headings exactly. Omit a section only if it is truly empty. Prefer bullets under each heading.
 4  
 5  ## Brief
 6  Current objective, current state, immediate next action. Note if the objective shifted from the original request.
 7  
 8  ## Constraints & preferences
 9  Requirements, preferences, or constraints stated by the user that the next agent must respect.
10  
11  ## Key decisions & rejected paths
12  Decisions that materially affect continuation, with brief rationale. Also include approaches that were tried, rejected, or failed when that prevents repeating mistakes.
13  
14  ## Status
15  What is done, what is in progress, what remains unverified, and what is blocked. Check the last several user messages for unresolved requests before marking anything done.
16  
17  ## Open issues & uncertainties
18  Unresolved problems, risky assumptions, and surprising findings. Distinguish observed facts from inferences.
19  
20  ## Immediate next steps
21  Concrete next actions in execution order. Note dependencies between steps.
22  
23  ## Mandatory reading
24  Exact file paths the next agent should open first.
25  
26  # Style
27  - Keep the summary concise and continuation-friendly
28  - Preserve exact file paths, symbol names, commands, and error text where useful
29  - If a files-touched block is present, use it as authoritative context but do not repeat the whole list
30  - Output only markdown for the summary