will/swarm-zap
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(agent): make WIP canonical implementation state

Browse Source
This commit is contained in:
zap
2026-03-12 20:43:19 +00:00
parent c64042b75a
commit 8a5b736ce7
2 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+4 -2
View File
@@ -172,8 +172,10 @@ For non-trivial implementation work, prefer a fresh isolated session/run instead
Default pattern:
1. use the current session to clarify scope, inspect state, and decide the plan
2. write or refresh a compact state file (`WIP.md` for the standing plan, plus `HANDOFF.md` for the immediate baton-pass when useful)
3. start a fresh isolated implementation session/run
4. have that fresh session execute the plan from the state files rather than inheriting a bloated chat history
3. treat `WIP.md` as the canonical implementation state file for non-trivial work
4. when a task or sub-task is completed, update `WIP.md` immediately with status, evidence, and the next recommended action
5. start a fresh isolated implementation session/run
6. have that fresh session execute the plan from the state files rather than inheriting a bloated chat history
Context-window rule of thumb:
- keep the main session for direction, approvals, and summaries