subagent-driven-development

Dispatch fresh subagents sequentially for plan-driven tasks with mandatory reviews.

3|2|Updated Oct 10, 2025
One-click install
npx skills add https://github.com/liauw-media/CodeAssist --skill subagent-driven-development-liauw-media
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/liauw-media/CodeAssist/tree/main/skills/workflow/subagent-driven-development
Command: npx skills add https://github.com/liauw-media/CodeAssist --skill subagent-driven-development-liauw-media

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Complex work benefits from decomposing into focused tasks with fresh subagents and mandatory reviews between tasks.

Core Features & Use Cases

  • Plan-driven task decomposition: Load a clear plan with distinct tasks.
  • Fresh subagents per task: Dispatch a new subagent for each task to avoid context leakage.
  • Mandatory review between tasks: Review outputs before moving to the next task.
  • No parallel dispatch: Enforce sequential task execution for quality control.

Quick Start

Load a plan with explicit tasks, then dispatch the first subagent and wait for its output before proceeding.

Frequently Asked Questions about subagent-driven-development

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

FAQPage Schema
How do I break down complex projects into focused tasks with fresh context?

Task decomposition with fresh subagents isolates context per task, preventing leakage across work streams. Load a plan with distinct tasks, dispatch a new subagent for each one, and enforce mandatory reviews between tasks to maintain quality control and catch errors early.

Why should I use separate subagents for each task instead of one continuous agent?

Fresh subagents per task eliminate accumulated context bias and reasoning drift. Each subagent starts clean, focused only on its assigned work, reducing mistakes and enabling strict inter-task reviews before proceeding to dependent work.

What's the best way to structure reviews between sequential tasks?

Mandatory reviews enforce a plan-driven sequence: complete one task, review its output against the plan, apply feedback if needed, mark completion, then dispatch the next subagent. This gating prevents cascading errors and keeps work aligned with the original plan.

Can I run tasks in parallel, or must they execute sequentially?

Tasks execute sequentially with no parallel dispatch. This enforces quality control and ensures each task can depend on verified outputs from prior tasks, making the workflow predictable and reviewable.

When should I use task decomposition with subagent reviews instead of a single agent?

Use this approach for complex projects with multiple independent tasks, diverse required skills, and strict quality gates. It's ideal when context leakage between tasks poses risk or when you need auditable reviews at each stage.