delegation-detaillisted
Install: claude install-skill yacb2/aidex
# Delegation detail
How to brief, size, launch and gate delegates. The routed agents ship with the plugin and
are named `aidex:<name>` in `subagent_type`: `aidex:artifact-sonnet`, `aidex:backlog-filer`,
`aidex:bugfix-opus`, `aidex:figure-sonnet`, `aidex:gate-runner`, `aidex:impl-sonnet`,
`aidex:lookup-sonnet`, `aidex:research-sonnet`, `aidex:review-diff-opus`,
`aidex:smoke-sonnet`, `aidex:synthesis-sonnet`, `aidex:task-general`,
`aidex:verify-browser-opus`, `aidex:verify-browser-sonnet`.
## The brief
A brief names paths, never "the file we discussed": goal, where to work, what to read first,
what is forbidden, how to verify, what to return. Use a fresh agent always; a fork only when
what the task needs exists nowhere but in this conversation (a fork costs several times a
fresh agent). Two parts are load-bearing; keep them as *named sections*, not sentences in a
paragraph:
- **"Files to read first"**, as the brief's own first step. The same sentence buried in a
lead paragraph is not acted on; as a named first step the canon actually gets read.
Name any file over about 25 KB as a Read-tool target: a Bash result over about 30000
characters reaches the agent only as a ~2 KB preview, so `cat`, `sed` or `head` of it reads
almost nothing (measured on aidex:artifact-sonnet runs).
- **"what you deliberately left alone"**, inside what to return: every defect or edge the
delegate saw and did not touch, one line each, no fix. A delegate is fresh by
construction, and a fre