subagent-driven-development

Name: subagent-driven-development
Availability: InStock
Author: lightxue

Coordinate implementation plans by deploying subagents with isolated context and staged reviews.

Updated Aug 27, 2026

Search Tags:#automation #workflow #planning #development #orchestration #review #subagent

Ready to run

npx skills add https://github.com/lightxue/dotfiles --skill subagent-driven-development-lightxue

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/lightxue/dotfiles/tree/main/agent/skills/subagent-driven-development
Command: npx skills add https://github.com/lightxue/dotfiles --skill subagent-driven-development-lightxue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to execute implementation plans by dispatching fresh subagents for each task, with isolated context and a two-stage review after every task to ensure spec compliance and code quality.

Core Features & Use Cases

Fresh subagent per task: Delegate tasks to specialized subagents with isolated context, preventing history leakage and context pollution.
Two-stage review after each task: Spec compliance review first, then code quality review.
Deterministic task execution: Follow a clearly defined workflow and prompts to ensure predictable outcomes.
Accelerated iteration in a single session: Maintain momentum without cross-task context contamination.
Use cases: When tasks are largely independent or require rigorous validation before integration.

Quick Start

Start by defining your plan, then dispatch the first implementer subagent to start Task 1 and follow the two-stage review loop.

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 complex implementation plans with isolated subagents?▼

Subagent orchestration deploys independent subagents per task to execute with isolated context. You define a plan, dispatch the first implementer subagent, and follow a two-stage review loop for spec compliance and code quality.

How do I prevent context pollution during rapid development iteration?▼

To prevent context pollution during rapid development, dispatch a fresh subagent for each task. This provides isolated context, preventing history leakage and maintaining momentum without cross-task context contamination.

What is the best way to enforce strict spec compliance in automated workflows?▼

The best way to enforce strict spec compliance in automated workflows is using a two-stage review process. After implementation, a dedicated spec reviewer checks adherence before a separate code quality review is conducted.

When should I use a subagent-driven development workflow?▼

Use a subagent-driven development workflow when tasks are largely independent, require strict adherence to specs, or need rapid iteration within a single session. It ensures deterministic task execution and predictable outcomes.

Do I need template prompts to coordinate tasks with subagents?▼

Yes, coordinating tasks with subagents requires template prompts for implementers, spec reviewers, and code quality reviewers. These templates define the per-task workflow and ensure completion is marked before proceeding.