subagent-driven-development

Dispatch isolated subagents per task with two-stage spec and quality reviews.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrate complex implementation plans by delegating each task to a fresh subagent, ensuring isolated context and disciplined review loops.

Core Features & Use Cases

  • Fresh-subagent per task: dispatch dedicated subagents for each task to avoid context leakage.
  • Two-stage review: spec compliance review first, then code quality review, ensuring alignment with requirements and maintainable code.
  • Parallel-friendly workflow: organize tasks to be processed in sequence within a single session without human-in-the-loop between tasks.
  • Finalization: after all tasks pass reviews, finish a development branch per plan.

Quick Start

Dispatch a plan to subagents and let them execute each task with two-stage reviews and finalization.

Frequently Asked Questions about subagent-driven-development

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

FAQPage Schema
How do I orchestrate subagents for plan-driven development workflows?

Orchestrate subagents in plan-driven development by dispatching an isolated subagent per decomposed task. This ensures strict spec compliance and code quality checks across multiple tasks before finalizing a development branch.

What is the two-stage review process for subagent-driven development?

Two-stage review in subagent-driven development performs a spec compliance review first, followed by a code quality review. This ensures each task aligns with requirements and produces maintainable code before proceeding.

How do I prevent context leakage when automating development workflows with multiple tasks?

Prevent context leakage in automated development workflows by dispatching a fresh, isolated subagent for each decomposed task. This keeps task execution independent and maintains strict boundaries across the orchestration sequence.

Can I process development tasks in sequence without human-in-the-loop interaction?

Yes, you can process development tasks in sequence within a single session without human-in-the-loop interaction between tasks. The orchestration workflow is parallel-friendly and automates reviews continuously until finalization.

When do I need subagent orchestration for code review and spec compliance?

You need subagent orchestration when executing complex implementation plans that require strict spec compliance and code quality reviews across multiple decomposed tasks, ensuring isolated context and disciplined review loops.

Does subagent-driven development require external dependencies to finalize a development branch?

No, subagent-driven development requires no external dependencies to finalize a development branch. The workflow operates independently, finalizing the branch only after all tasks pass both spec compliance and code quality reviews.