subagent-driven-development

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

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/kangjuhyup/study --skill subagent-driven-development-kangjuhyup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/kangjuhyup/study/tree/main/scoped-superpowers-ab/workflow-code-benchmark/fixture/workflows/full/skills/subagent-driven-development
Command: npx skills add https://github.com/kangjuhyup/study --skill subagent-driven-development-kangjuhyup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Executing a multi-task implementation plan in one AI session often leads to context pollution, skipped reviews, and lost progress after context compaction. This Skill orchestrates plan execution by delegating each task to a fresh subagent with isolated context, enforcing per-task reviews, and tracking progress in a persistent ledger. ## Core Features & Use Cases - Fresh subagent per task: Dispatches an implementer subagent with a task brief file, then a task reviewer subagent that verifies spec compliance and code quality against the diff. - Bounded fix loop with escalation: Runs up to five fix rounds per task, resuming the original implementer for rounds 1-3 and escalating to a more capable model for rounds 4-5, with adjudication at the cap. - Ledger-based recovery: Records task completions, rulings, and parked findings in a per-plan workspace ledger so progress survives context compaction. - Use Case: Given a plan file with ten independent tasks, the controller dispatches implementers one at a time, reviews each diff via generated review packages, and finishes with a whole-branch review before merging. ## 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 task brief file, then dispatch a task reviewer against the generated diff package. Track completions in a ledger file and run a final whole-branch review after all tasks finish.

When should I use subagent-driven development vs executing plans directly?

Use it when you have an implementation plan with mostly independent tasks and want to stay in the current session. Tightly coupled tasks or missing plans call for manual execution or brainstorming first.

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

Rounds 1-3 resume the original implementer with the findings verbatim; rounds 4-5 dispatch a fresh implementer on a more capable model. After five rounds, the controller adjudicates each open finding and records rulings in the ledger.

Why does the skill use a ledger file instead of todos?

Conversation memory does not survive context compaction, and controllers without a ledger have re-dispatched completed task sequences. The ledger plus git log provides a durable recovery map of completed work.

Can implementer subagents spawn their own reviewers?

No. The dispatch contract forbids implementers from spawning any subagents, including reviewers. Review arrives only from the controller after the implementer reports, since worker-spawned reviewers duplicate the task review at full cost.