subagent-driven-development

Execute implementation plans by dispatching fresh implementer and reviewer subagents per task.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/kxnzee/multi-repo-specs --skill subagent-driven-development-kxnzee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/kxnzee/multi-repo-specs/tree/main/extensions/superpowers/skills/subagent-driven-development
Command: npx skills add https://github.com/kxnzee/multi-repo-specs --skill subagent-driven-development-kxnzee

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, skips quality gates, and loses progress after compaction. This Skill orchestrates plan execution by delegating each task to an isolated subagent with curated context, enforcing review after every task, and tracking progress in a durable ledger. ## Core Features & Use Cases - Per-task subagent dispatch: Each task gets a fresh implementer subagent with a file-based task brief, explicit constraints, and a report contract, keeping the controller's context clean. - Two-stage review gates: A task reviewer verifies spec compliance and code quality per task, followed by a broad whole-branch review at the end, with fix subagents for Critical and Important findings. - Durable progress tracking: A plan-scoped ledger and review-package scripts record commits, snapshot tree SHAs, and verification evidence so work resumes correctly after session compaction. - Use Case: Given a written implementation plan with eight independent tasks, the controller extracts each task brief, dispatches implementers sequentially, reviews each diff, and finishes with a whole-branch code review before merge. ## Quick Start Use subagent-driven development to execute the implementation plan at docs/plans/feature-plan.md task by task with reviews.

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 file-based task brief, then dispatch a task reviewer subagent against the generated diff package. After all tasks pass review, run a final whole-branch review before merging.

What is the difference between subagent-driven development and executing plans?▼

Subagent-driven development stays in the current session with fresh subagents per task and continuous execution. Executing plans uses a parallel session with human-in-the-loop checkpoints between tasks, which suits tightly coupled work.

How does the skill recover progress after session compaction?▼

It writes a plan-scoped progress ledger keyed by checkout, branch, plan path, and plan contents. After compaction, the controller resumes from the ledger and verifies recorded commits against Git evidence instead of trusting task numbers.

When should I not use subagent-driven development?▼

Avoid it when tasks are tightly coupled and cannot be delegated independently, when no implementation plan exists yet, or when a parallel session with human checkpoints fits better. Brainstorm or write the plan first in those cases.

How are code reviews handled between subagent tasks?▼

Each task produces a review package containing the commit list, stat summary, and full diff. A reviewer subagent returns spec compliance and code quality verdicts, and fix subagents address Critical and Important findings before re-review.