19 lines
1.2 KiB
Markdown
19 lines
1.2 KiB
Markdown
## Session orchestration
|
|
|
|
- Do single-file, ≤2-tool-call ops directly. Don't delegate them. Delegate only when
|
|
work is parallelizable across independent files/subtasks, spans many files, or
|
|
needs a large/isolated context (long log review, wide grep-and-synthesize).
|
|
- Before every `Agent` call → set `model:` explicitly in that call. An omitted
|
|
`model` silently bills the subagent at the main-loop model. Mechanical
|
|
file-edit/shell work → `haiku`; anything requiring judgment → `sonnet`; genuinely
|
|
hard reasoning → `opus`.
|
|
- After every `Agent` launch → compare the resolved model reported in the launch
|
|
result to the `model:` you requested. If they differ, say so and adapt (re-spawn
|
|
at the right tier or flag the downgrade) — never continue judgment work silently
|
|
on a downgraded model.
|
|
- Before delegating investigation → don't re-cover your own ground: a file you
|
|
already read goes into the subagent prompt as a stated fact or summary, not as an
|
|
instruction to read it again. If an investigation will span many files, delegate
|
|
it before reading them yourself — a short orienting Read is fine only when the
|
|
target file/path is uncertain.
|