taodeng/memory-continuity
1
0
Fork 0
mirror of https://github.com/dtzp555-max/memory-continuity.git synced 2026-07-21 21:15:07 +00:00
Code Issues Packages Projects Releases Wiki Activity

Harden workflow evidence gates after failed agent test

Browse Source
This commit is contained in:
taodeng
2026-03-09 07:00:17 +10:00
parent d4513c1482
commit 4509a8e7f6
5 changed files with 41 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/execution-agent-dispatch/SKILL.md
+8 -3
View File
@@ -50,11 +50,16 @@ Tell the worker what first checkpoint matters and when main expects the first up
## Worker response format
Execution agents should respond compactly with:
- `status:` ok | blocked | failed
- `changed:` files changed/created, commands run, or "none"
- `notes:` short summary
- `status:` accepted | milestone | blocked | failed | done
- `summary:` short summary
- `evidence:` files changed/created, commands run, session/log proof, or `none`
- `risk:` key caveat or `none`
- `next:` next action or handoff need
Important:
- A reply without `evidence` is not enough for main to claim the task is truly `in_progress`.
- `accepted` means the worker has seen the handoff; it does not automatically mean meaningful execution has started.
## Escalate immediately when
A worker should report back to main instead of silently stalling when: