skills: add execution agent dispatch protocol

skills/execution-agent-dispatch/README.md

@@ -0,0 +1,53 @@
+# execution-agent-dispatch
+
+A lightweight skill for turning PM decisions into clear worker handoffs.
+
+## Why this exists
+
+It is not enough to have execution agents.
+They also need a consistent way to receive work and report results.
+
+Without that, the system drifts into familiar failure modes:
+- vague delegation
+- role boundary drift
+- workers doing too much or too little
+- silent blocking
+- messy result reporting
+
+This skill exists to standardize the handoff layer between **main** and execution agents.
+
+## What it standardizes
+
+- the task packet main sends to a worker
+- the result format a worker returns
+- when a worker must escalate instead of staying silent
+- milestone / ETA discipline for delegated work
+
+## Core idea
+
+A good worker handoff should answer:
+1. What exactly should be done?
+2. What is out of bounds?
+3. What does success look like?
+4. When should the worker report back?
+5. What should trigger escalation?
+
+## Recommended task packet
+
+- Task
+- Scope
+- Deliverable
+- Constraints
+- Milestone 1 + ETA
+
+## Recommended result packet
+
+- `status:` ok | blocked | failed
+- `changed:` ...
+- `notes:` ...
+- `next:` ...
+
+## Notes
+
+This is a dispatch / coordination skill, not an implementation skill.
+It works best after `execution-agent-planner` has already decided which workers should exist and what they should own.

skills/execution-agent-dispatch/SKILL.md

@@ -0,0 +1,104 @@
+---
+name: execution-agent-dispatch
+description: Standardize how main dispatches work to execution agents and how execution agents report back. Use when main has already decided which execution agent(s) should do the work and needs a clear handoff packet, result format, blocker/escalation rules, and milestone discipline so workers do not drift or go silent.
+---
+
+# Execution agent dispatch
+
+Use this skill after execution architecture is decided.
+
+## Goal
+
+Turn vague delegation into a clear handoff.
+Every dispatched task should make it obvious:
+- what to do
+- what not to do
+- what counts as done
+- when to escalate back to main
+
+## Dispatch packet
+
+When main assigns work to an execution agent, include these sections:
+
+### 1) Task
+One short statement of the goal.
+
+### 2) Scope
+Specify:
+- repo / path / files if known
+- what area is in bounds
+- what is explicitly out of bounds
+
+### 3) Deliverable
+Define the expected output:
+- code change
+- docs update
+- validation report
+- PR / commit / test result
+- recommendation only
+
+### 4) Constraints
+List non-negotiables, such as:
+- do not change unrelated files
+- do not switch models automatically
+- do not message users directly
+- ask before destructive actions
+
+### 5) Milestone 1 + ETA
+Tell the worker what first checkpoint matters and when main expects the first update.
+
+## Worker response format
+
+Execution agents should respond compactly with:
+- `status:` ok | blocked | failed
+- `changed:` files changed/created, commands run, or "none"
+- `notes:` short summary
+- `next:` next action or handoff need
+
+## Escalate immediately when
+
+A worker should report back to main instead of silently stalling when:
+- permissions are missing
+- the model/tooling is unavailable
+- repo rules block the intended action
+- requirements are contradictory or underspecified
+- the task is crossing role boundaries
+- the ETA has clearly slipped
+- the requested change is riskier or broader than the original handoff suggested
+
+## Silence rule
+
+Workers should not chatter, but should also not disappear.
+
+Default rule:
+- acknowledge briefly
+- do the work
+- report at milestone
+- report immediately on blockers
+
+## Completion rule
+
+A task is not complete just because files changed.
+Completion should include:
+- the requested deliverable exists
+- basic verification happened when relevant
+- blockers or caveats are disclosed
+- main has enough information to review and report upward
+
+## Main's responsibility
+
+Main must not delegate sloppily.
+Before dispatching, main should decide:
+- why this worker is the right worker
+- what the boundary is
+- what review criteria will be used
+- whether the task is small enough that delegation is unnecessary
+
+## Good default tone
+
+- short
+- operational
+- explicit
+- non-dramatic
+
+Prefer a clean task packet over a long motivational speech.