subagent-driven-development

Dispatch fresh subagents for each task with spec and code quality reviews.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/AndrewChang-cpu/vibe-coding-configuration --skill subagent-driven-development-andrewchang-cpu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/AndrewChang-cpu/vibe-coding-configuration/tree/main/general-plugin/skills/subagent-driven-development
Command: npx skills add https://github.com/AndrewChang-cpu/vibe-coding-configuration --skill subagent-driven-development-andrewchang-cpu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to execute implementation plans by dispatching fresh subagents for each task, ensuring isolated context and faster iteration while preserving the coordinator's overall context.

Core Features & Use Cases

  • Fresh-subagent per task: each task is handled in isolation with dedicated context and prompts.
  • Two-stage reviews: after each task, a spec-compliance review followed by a code-quality review to ensure quality and alignment.
  • End-to-end workflow: orchestrates per-task execution, self-checks, and formal handoffs between subagents.

Quick Start

Instruct the AI to dispatch a per-task subagent workflow for your current plan and begin execution.

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 implementation plan execution?

To orchestrate subagents for implementation plan execution, dispatch a fresh subagent for each independent task. This isolates context and accelerates iteration while the main coordinator manages the overall workflow and structured review checkpoints.

What is the best way to automate code quality review during task execution?

Automating code quality review requires a two-stage workflow: first checking spec compliance, then evaluating code quality. Dispatching dedicated reviewer subagents after each implementation task ensures structured, automated quality alignment without manual intervention.

How do fresh subagents speed up development workflows with independent tasks?

Fresh subagents speed up development workflows by providing isolated, dedicated context for each independent task. This prevents context overflow, enables faster iteration, and preserves the coordinator's overall project context for higher-quality results.

When should I use a subagent-driven development workflow?

Use a subagent-driven development workflow for sessions containing mostly independent tasks requiring fast iteration. It is ideal when you need structured review checkpoints for spec compliance and code quality without overwhelming a single agent's context.

How do I manage task-specific context provisioning for subagents?

Task-specific context provisioning is managed automatically by dispatching fresh subagents for each task. The coordinator orchestrates this by providing dedicated prompts and isolated context per task, ensuring focused execution and formal handoffs.

Do I need external dependencies to run an automated subagent review workflow?

No external dependencies are required to run an automated subagent review workflow. The system self-contains the implementer, spec reviewer, and code quality reviewer prompts internally to manage execution and automatic reviews.