summaryrefslogtreecommitdiff
path: root/skills/using-superpowers/references
diff options
context:
space:
mode:
authorJesse Vincent <jesse@primeradiant.com>2026-09-17 17:03:55 -0700
committerJesse Vincent <jesse@primeradiant.com>2026-09-17 17:03:55 -0700
commit5b56e6f7ebe5012dd03bed2b9ebb9aa5ab8444af (patch)
treed89f12295107affc9899d6e1a2d610d6f060cccd /skills/using-superpowers/references
parentdcc1b26bc513bd0d0c0781fce0383ef0ae4ac1e4 (diff)
Add Claude Code platform reference: a nested orchestrator for cheaper subagent-driven developmentclaude-code-platform-reference
Diffstat (limited to 'skills/using-superpowers/references')
-rw-r--r--skills/using-superpowers/references/claude-code-tools.md29
1 files changed, 29 insertions, 0 deletions
diff --git a/skills/using-superpowers/references/claude-code-tools.md b/skills/using-superpowers/references/claude-code-tools.md
new file mode 100644
index 0000000..550b8e4
--- /dev/null
+++ b/skills/using-superpowers/references/claude-code-tools.md
@@ -0,0 +1,29 @@
+# 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.
+
+## 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.