subagent-driven-development

Executes implementation plans by dispatching fresh subagents per task with two-stage review.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/CHENHUI-X/toolbox --skill subagent-driven-development-chenhui-x
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/CHENHUI-X/toolbox/tree/main/custom-skills/software-development/subagent-driven-development
Command: npx skills add https://github.com/CHENHUI-X/toolbox --skill subagent-driven-development-chenhui-x

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Executing a multi-task implementation plan in a single session leads to context pollution, inconsistent quality, and undetected spec drift. This Skill orchestrates plan execution by delegating each task to a fresh subagent and enforcing systematic review between tasks. ## Core Features & Use Cases - Per-Task Subagent Dispatch: Parses a plan file once, then delegates each task via delegate_task with full task text and project context, so subagents never read the plan file themselves. - Two-Stage Review Pipeline: Runs a spec compliance review first, then a code quality review, looping fixes until both pass before marking a task complete. - Final Integration Review: After all tasks complete, dispatches a reviewer to check cross-task consistency, run the full test suite, and confirm merge readiness. - Use Case: Given a plan like docs/plans/auth-feature.md with five tasks (User model, password hashing, login endpoint, JWT generation, registration endpoint), the Skill implements each task with TDD, reviews each twice, and delivers a fully tested feature. ## Quick Start Execute the implementation plan in docs/plans/feature-plan.md by dispatching a fresh subagent for each task with spec and quality reviews between tasks.

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 subagents?

Read the plan file once, extract all tasks into a todo list, then dispatch a fresh implementer subagent per task with the full task text in context. After each implementation, run a spec compliance review followed by a code quality review before marking the task complete.

What is the two-stage review process for subagent code?

The first stage checks spec compliance against the original task requirements, catching missing features or scope creep. The second stage reviews code quality including conventions, error handling, test coverage, and security. Spec review must pass before quality review begins.

Why use a fresh subagent for each task instead of one session?

Fresh subagents prevent context pollution from accumulated state, giving each task clean, focused context without confusion from prior tasks' code or reasoning. This improves consistency and makes review outcomes more reliable across all tasks.

How big should each task be for subagent delegation?

Each task should represent 2-5 minutes of focused work, such as creating a single model, adding one hashing function, or building one endpoint. Broad tasks like implementing an entire authentication system should be split into smaller units first.

What happens when a reviewer subagent finds issues?

The implementer subagent, or a new fix subagent, addresses the specific issues, then the reviewer re-reviews the work. This loop repeats until approval, and the workflow never proceeds to the next task with open critical or important issues.

When should I not use subagent-driven development?

Avoid it when there is no written implementation plan, when tasks are tightly coupled and touch the same files concurrently, or when you would skip the review loops. Starting implementation without a plan or skipping reviews defeats the process.