Document context reset workflow
This commit is contained in:
@@ -27,6 +27,11 @@ Read these first:
|
||||
- Commit and push each verified successful progress slice.
|
||||
- Prefer larger coherent slices over tiny checkpoints, but keep docs/debt updated
|
||||
with each slice.
|
||||
- After a verified slice is committed and pushed, reset conversation context
|
||||
before starting the next slice when practical, especially if the thread is
|
||||
approaching automatic compaction. Record all needed resume state in committed
|
||||
code/docs first so the next thread can restart from `AGENTS.md`, roadmap/debt,
|
||||
and git history instead of relying on chat transcript context.
|
||||
- Do not revert user changes. Unrelated untracked notes, such as
|
||||
`docs/human-review-notes.md`, should be left alone unless explicitly requested.
|
||||
- Use CMake as the source of truth. Legacy Visual Studio project files are not the
|
||||
|
||||
Reference in New Issue
Block a user