Carry what the next decision needs.
More context is useful only when it helps the next decision. A clear task, relevant paths, and a brief verification record often serve an iteration better than a long transcript. Keep the repository itself as the source of current implementation detail.
- 01
Start with the active outcome
State the current behavior, desired result, and boundary of the task. Point to likely files and explain why they matter. Include a small reproduction when available. Avoid pasting entire directories or private logs when the assistant can inspect the relevant source directly.
- 02
Separate facts from proposals
Record decisions already made and mark suggestions as suggestions. Note which checks have run and whether code changed afterward. When context is stale, ask the assistant to inspect the current files again. A previous summary should orient that inspection, not overrule the checkout.
- 03
Refresh at a natural boundary
After completing a slice, summarize what changed, what was verified, and the next action. Keep unresolved constraints visible. If your client supports session summaries, check the result for missing decisions before relying on it. Available context tools vary with the software you choose.
A useful finish
The assistant can identify the next useful action without guessing which decisions or repository details are current.
A compact continuation brief
Current objective: [outcome]. Relevant paths: [files]. Completed: [changes]. Verified: [checks and results]. Unresolved: [specific issue]. Next action: [one step]. Inspect the current repository state before continuing; preserve existing edits.