bryan/agent-team
1
0
Fork 0
mirror of https://github.com/itme-brain/agent-team.git synced 2026-05-08 14:50:13 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

Refine agent escalation contracts

Browse source
This commit is contained in:
Bryan Ramos 2026-04-02 14:05:51 -04:00
parent 947886fba5
commit 2a2cd3ca22
9 changed files with 238 additions and 46 deletions
Download patch file Download diff file Expand all files Collapse all files

13
skills/message-schema/SKILL.md
View file

@ -73,6 +73,19 @@ Optional: `ac_coverage` (omit when no AC provided in assignment)
Body: `## Result` section with implementation details, then `## Self-Assessment` with per-criterion notes and known limitations.
**Routing contract for implementers:**
- `grunt` uses `blocked` to request reassignment to `worker` or orchestrator intervention.
- `worker` uses `blocked` to request reassignment to `senior` or orchestrator intervention.
- `senior` uses `blocked` to request orchestrator re-decomposition, plan revision, or a senior wave/team.
- Any implementer uses `escalate` only when the blocker requires a user decision or approval, not merely a stronger implementer.
When `signal: blocked` or `signal: escalate` is used, the body must include a one-line route hint:
- `Route: worker`
- `Route: senior`
- `Route: orchestrator`
- `Route: orchestrator (re-decompose)`
- `Route: orchestrator (user decision required)`
### review_verdict
Emitted by: reviewer