subagent-driven-development

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Executing a multi-task implementation plan in a single session often leads to context pollution, skipped reviews, and inconsistent quality. This Skill orchestrates plan execution by dispatching a fresh subagent for each task and enforcing a two-stage review (spec compliance, then code quality) after every task. ## Core Features & Use Cases - Fresh Subagent Per Task: Each task runs in an isolated subagent context with exactly the instructions and context it needs, preserving the controller's context for coordination. - Two-Stage Review Gates: A spec compliance reviewer verifies the code matches requirements before a code quality reviewer assesses maintainability, with fix-and-re-review loops until approval. - Status-Based Escalation: Implementer subagents report DONE, DONE_WITH_CONCERNS, NEEDS_CONTEXT, or BLOCKED, and the controller responds with more context, a more capable model, or task decomposition. - Use Case: You have a written plan with 5 mostly independent tasks. This Skill extracts all tasks into a todo list, dispatches an implementer subagent for each, runs spec and quality reviews after each task, and finishes with a final whole-implementation review. ## Quick Start Use subagent-driven development to execute the implementation plan in docs/plans/feature-plan.md task by task with reviews after each task.

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?

Extract all tasks from the plan into a todo list, then dispatch a fresh implementer subagent per task with the full task text and context. After each task, run a spec compliance review followed by a code quality review before marking the task complete.

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

Subagent-driven development runs in the same session with a fresh subagent per task and no human-in-loop between tasks. Executing plans uses a parallel session with a handoff, which suits cases where you do not want to stay in the current session.

When should I not use subagent-driven development?

Avoid it when tasks are tightly coupled and cannot be implemented independently, when there is no written implementation plan, or when you prefer a parallel session workflow. Also never dispatch multiple implementation subagents in parallel due to conflicts.

What should I do when an implementer subagent reports BLOCKED?

Assess the blocker: provide more context and re-dispatch if it is a context problem, use a more capable model if the task needs more reasoning, break the task into smaller pieces if too large, or escalate to the human if the plan itself is wrong.

Why must spec compliance review come before code quality review?

Spec compliance confirms the implementation matches requirements with nothing missing or extra. Reviewing code quality before correctness wastes effort, since spec fixes may change the code that a quality review would assess.