AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

using-superpowers

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

Original source
obra
License
MIT
Pinned revision
2ce8aa15d05bd57213e6f746f953aafb7ded7a8b

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read obra--using-superpowers at revision 2ce8aa15d05bd57213e6f746f953aafb7ded7a8b, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 8

references/claude-code-tools.md

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.