Subagent-Driven Development
Execute implementation plans with a fresh implementer subagent per task, a spec+quality review after each, and a whole-branch review at the end
- What
- Execute implementation plans with a fresh implementer subagent per task, a spec+quality review after each, and a whole-branch review at the end
- Cost
- Free
- Needs
- an agent harness that can dispatch subagents (Claude Code style); a git repository; an implementation plan to execute. Companion superpowers skills for the full loop: using-git-worktrees, requesting-code-review, finishing-a-development-branch.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the flagship execution skill of the superpowers suite: run an implementation plan with a fresh subagent per task, a task review (spec compliance AND code quality — both verdicts required) after each one, and one broad whole-branch review at the end. It tracks progress in a git-ignored ledger file (not memory — compaction kills it), pre-flights the plan for task conflicts before dispatching Task 1, picks the cheapest model that fits each role, caps the fix loop at five rounds per task (resume the implementer for rounds 1–3, fresh higher-tier eyes for 4–5, adjudicate at the cap), and keeps going with recorded rulings instead of stalling on human questions — the only stops are irreversible/destructive operations, security-sensitive actions, side effects outside the worktree, or a plan so broken every path is a guess. By @obra, listed here with credit to its creator. Honest caveats: it depends on a harness that can dispatch and message subagents (Claude Code style), on the companion scripts (`sdd-workspace`, `task-brief`, `review-package`) in the repo, and on sibling skills (using-git-worktrees, requesting-code-review, finishing-a-development-branch) for the full loop; it's demanding by design — "continuous execution" means the human is not consulted mid-plan. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: an agent harness that can dispatch subagents (Claude Code style); a git repository; an implementation plan to execute. Companion superpowers skills for the full loop: using-git-worktrees, requesting-code-review, finishing-a-development-branch. Install "Subagent-Driven Development" for me. It executes implementation plans with a fresh implementer subagent per task, a spec+quality review after each task, a 5-round fix loop, and a final whole-branch review. Repository: https://github.com/obra/superpowers/blob/main/skills/subagent-driven-development/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "obra-subagent-driven-development". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself. GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.