subagent-driven-development

Executes implementation plans by dispatching fresh subagents per task with per-task reviews.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/Pega88/agy-superpowers --skill subagent-driven-development-pega88
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/Pega88/agy-superpowers/tree/main/.agents/plugins/superpowers/skills/subagent-driven-development
Command: npx skills add https://github.com/Pega88/agy-superpowers --skill subagent-driven-development-pega88

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Executing a multi-task implementation plan in a single AI session pollutes context, loses progress after compaction, and ships unreviewed code. This Skill orchestrates plan execution by delegating each task to an isolated subagent, gating every task behind a spec-compliance and code-quality review, and tracking progress in a persistent ledger. ## Core Features & Use Cases - Fresh subagent per task: Dispatches implementer subagents with isolated context, task briefs extracted to files, and explicit model selection per task complexity. - Review-gated task loop: Every task gets a spec-compliance and code-quality review, with a bounded five-round fix loop, scoped re-reviews, and adjudication of residual findings. - Ledger-based recovery: A per-plan progress ledger and workspace under .superpowers/sdd/ survive context compaction so completed tasks are never re-dispatched. - Use Case: Given a written implementation plan with eight independent tasks, the Skill creates a worktree, dispatches implementers one task at a time, reviews each diff, runs a final whole-branch review, and finishes the development branch. ## Quick Start Ask the agent to execute your implementation plan using subagent-driven development, pointing it at the plan file path.

Frequently Asked Questions about subagent-driven-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute an implementation plan with AI subagents?

Dispatch a fresh implementer subagent per task with a task brief file, then gate each task behind a spec-compliance and code-quality review. Track progress in a ledger file so completed tasks survive context compaction and are never re-dispatched.

When should I use subagent-driven development instead of executing a plan directly?

Use it when you have an implementation plan whose tasks are mostly independent and you want to stay in the current session. Tightly coupled tasks or plans needing a parallel session fit manual execution or an executing-plans workflow better.

How does the fix loop work when a task review finds issues?

Rounds one through three resume the original implementer with the findings verbatim; rounds four and five dispatch a fresh implementer on a more capable model. After five rounds, remaining findings are adjudicated and parked with recorded rulings.

Can multiple implementation subagents run in parallel?

No, the Skill forbids dispatching multiple implementation subagents in parallel because they conflict on shared files. Small same-shape edits across files are batched into a single dispatch instead.

What happens to progress if the AI session context is compacted?

Progress is tracked in a per-plan ledger file under .superpowers/sdd/, not in conversation memory. After compaction, the controller resumes from the ledger and git log rather than its own recollection.