Skill Tracer
Skills › Superpowers › using-superpowers › claude-code-tools.md

claude-code-tools.md

29 lines · skills/using-superpowers/references/claude-code-tools.md at 2ce8aa1

Open on GitHub

Most marks come from matching words in the file, so treat them as pointers.

1# Claude Code Tool Notes
2
3Claude Code is the reference harness: skills speak its vocabulary
4(`Agent` for a subagent dispatch, todos, `Skill`). These notes cover the
5one place Claude Code can run a plan cheaper than the skills' default
6shape. It is opt-in by your human partner and changes nothing the skills
7require.
8

Claude Code Tool Notes

Claude Code is the reference harness: skills speak its vocabulary (Agent for a subagent dispatch, todos, Skill). These notes cover the one place Claude Code can run a plan cheaper than the skills' default shape. It is opt-in by your human partner and changes nothing the skills require.

Raw lines 1 to 8
Starts an agent subagent :4
Starts an agent dispatch :4
9## Cheaper orchestration for subagent-driven development
11The controller session is the most expensive seat in a
12superpowers:subagent-driven-development run: it reads every dispatch
13result and every report, and it usually runs on the session's most
14capable model. Claude Code supports nested subagents (three layers below
15the main conversation by default; `CLAUDE_CODE_MAX_SUBAGENT_SPAWN_DEPTH`
16adjusts it), so the whole loop can run one layer down.
18When your human partner asks for it — or has said the session model is
19too expensive to spend on coordination — dispatch ONE orchestrator
20subagent on a mid-tier model with the plan path and the instruction to
21use superpowers:subagent-driven-development end to end. The orchestrator
22dispatches its own implementers and reviewers per that skill's Model
23Selection; the workspace and ledger live on disk, so nothing is lost to
24the extra layer. Its final message must carry the "Rulings I made" list
25verbatim — that list is how the decisions reach your human partner, and
26you relay it, not summarize it.
28Do this only for a whole plan. Nesting a single task's dispatch buys
29nothing and adds a seat.

Cheaper orchestration for subagent-driven development

The controller session is the most expensive seat in a superpowers:subagent-driven-development run: it reads every dispatch result and every report, and it usually runs on the session's most capable model. Claude Code supports nested subagents (three layers below the main conversation by default; CLAUDE_CODE_MAX_SUBAGENT_SPAWN_DEPTH adjusts it), so the whole loop can run one layer down.

When your human partner asks for it — or has said the session model is too expensive to spend on coordination — dispatch ONE orchestrator subagent on a mid-tier model with the plan path and the instruction to use superpowers:subagent-driven-development end to end. The orchestrator dispatches its own implementers and reviewers per that skill's Model Selection; the workspace and ledger live on disk, so nothing is lost to the extra layer. Its final message must carry the "Rulings I made" list verbatim — that list is how the decisions reach your human partner, and you relay it, not summarize it.

Do this only for a whole plan. Nesting a single task's dispatch buys nothing and adds a seat.

Raw lines 9 to 29
Starts an agent subagent :9
Names a skill subagent-driven-development :12
Starts an agent dispatch :12
Starts an agent subagents :14
Starts an agent dispatches :22