Add dispatch checklist and failure template

skills/execution-agent-dispatch/CHECKLIST.md

@@ -0,0 +1,60 @@
+# Execution-Agent Dispatch Checklist
+
+Use this checklist before main claims delegated work is underway.
+
+## A. Before dispatch
+- [ ] The task is worth delegating (not a tiny one-shot edit main should just do directly)
+- [ ] The correct worker is chosen
+- [ ] Scope is explicit
+- [ ] Out-of-scope boundaries are explicit
+- [ ] Deliverable is explicit
+- [ ] Constraints are explicit
+- [ ] Milestone 1 and ETA are explicit
+- [ ] Escalation conditions are explicit
+
+## B. Immediately after dispatch
+- [ ] Record task state as `dispatching`
+- [ ] Do **not** call it `in_progress` yet
+- [ ] Do **not** tell Tao that execution is underway unless evidence already exists
+
+## C. Evidence gate for `in_progress`
+At least one of these must exist before main upgrades the task to `in_progress`:
+- [ ] Worker session has a visible non-empty reply
+- [ ] Worker reported `accepted` with real execution context
+- [ ] Worker reported a milestone
+- [ ] A branch / commit / PR exists
+- [ ] A file / artifact / runtime log exists
+
+If none of the above exists, the task is still `dispatching`.
+
+## D. Launch-failure rule
+- [ ] If no first evidence appears within 10 minutes, mark the task `blocked`
+- [ ] Use blocked reason: `launch failure`
+- [ ] Tell Tao plainly that the worker never produced execution evidence
+
+## E. Allowed Tao-visible updates
+Main should proactively update Tao only when one of these is true:
+- [ ] Worker truly started (with evidence)
+- [ ] Milestone reached
+- [ ] Blocked / failed
+- [ ] Completed
+- [ ] Main is switching workers / phases in a way Tao should know
+
+If none is true, do not send a long "in progress" page.
+
+## F. Worker reply minimums
+A worker reply should include:
+- [ ] `status`
+- [ ] `summary`
+- [ ] `evidence`
+- [ ] `risk`
+- [ ] `next`
+
+A worker reply without `evidence` is not enough to justify `in_progress`.
+
+## G. Completion gate
+Before main says the task is done:
+- [ ] Deliverable exists
+- [ ] Basic verification happened when relevant
+- [ ] Caveats/blockers are disclosed
+- [ ] Tao has been updated

skills/execution-agent-dispatch/FAILURE_TEMPLATE.md

@@ -0,0 +1,32 @@
+# Delegation Failure Template
+
+Use this when a delegated task did not truly start, stalled, or was misreported.
+
+## Minimal internal record
+- Task:
+- Intended worker(s):
+- State when failure recognized:
+- Failure type: `launch failure` | `stalled` | `model` | `auth` | `tool` | `path/repo` | `scope` | `policy/review` | `external`
+- Evidence present:
+- Evidence missing:
+- User-visible impact:
+- Correct next state:
+- Prevention rule:
+
+## Minimal Tao update
+- who:
+- status:
+- output:
+- next:
+
+## Example: launch failure
+- who: `data_worker`
+- status: blocked — launch failure
+- output: dispatch was attempted, but no worker session evidence / milestone / artifact appeared within the launch window
+- next: mark this worker blocked, stop claiming progress, and either retry explicitly or revise the plan
+
+## Example: main misreporting failure
+- who: main
+- status: failed — reporting/process failure
+- output: main reported progress without execution evidence from the delegated worker
+- next: correct state to `dispatching` or `blocked`, notify Tao, and tighten the evidence gate before future dispatches

skills/execution-agent-dispatch/README.md

@@ -42,11 +42,17 @@ A good worker handoff should answer:
 
 ## Recommended result packet
 
-- `status:` ok | blocked | failed
-- `changed:` ...
-- `notes:` ...
+- `status:` accepted | milestone | blocked | failed | done
+- `summary:` ...
+- `evidence:` ...
+- `risk:` ...
 - `next:` ...
 
+## Added operational aids
+
+- `CHECKLIST.md` — pre-dispatch / post-dispatch / evidence-gate checklist for main
+- `FAILURE_TEMPLATE.md` — compact template for documenting launch failure, stall, or misreporting cases
+
 ## Notes
 
 This is a dispatch / coordination skill, not an implementation skill.