subagent-driven-development

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents context pollution and manual coordination when executing multi-step implementation plans by dispatching isolated subagents per task and enforcing structured review gates, so work progresses safely and predictably within the same session.

Core Features & Use Cases

  • Fresh subagent per task: Each task runs in an isolated context to avoid leaking session state or history.
  • Two-stage review pipeline: Enforce spec compliance review first, then a separate code quality review before marking tasks complete.
  • Implementer lifecycle & statuses: Implementers must ask clarifying questions, run tests, self-review, and report precise statuses (DONE, DONE_WITH_CONCERNS, NEEDS_CONTEXT, BLOCKED) to drive correct re-dispatching.
  • Model selection guidance: Use lower-power models for mechanical tasks and stronger models for integration, architecture, or troubleshooting.
  • Use case: Execute a development plan by extracting tasks to a TodoWrite, dispatch implementer subagents for each task, and iterate reviews until the branch is ready to finish.

Quick Start

Dispatch this skill to run your implementation plan by extracting tasks, running an implementer subagent per task, and iterating spec compliance and code-quality reviews until all tasks are approved.

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 a multi-step development plan without polluting context or manually coordinating tasks?

Subagent orchestration executes multi-step implementation plans by dispatching isolated subagents per task, preventing context pollution. It provides structured review gates, testing, and commits, so work progresses safely and predictably within the same session.

What is the two-stage review workflow for subagent-driven task execution?

The two-stage review workflow enforces spec compliance review first, then a separate code quality review, before marking tasks complete. This structured pipeline ensures implementation meets requirements and maintains quality standards before proceeding.

How do I coordinate isolated subagents for independent implementation tasks?

You coordinate isolated subagents by dispatching a fresh subagent per task extracted to a TodoWrite. Each subagent handles implementation, asks clarifying questions, runs tests, and reports precise statuses like DONE or BLOCKED to drive correct re-dispatching.

When should I use lower-power models versus stronger models for subagent task execution?

Model selection guidance suggests using lower-power models for mechanical implementation tasks and stronger models for integration, architecture, or troubleshooting. This optimizes orchestration efficiency by matching model capability to task complexity.

What are the limitations of using subagent orchestration for plan execution?

Subagent orchestration is limited to same-session plan execution where tasks are mostly independent. It is not suited for highly dependent tasks requiring shared session state, as each subagent runs in isolated context to prevent history leaking.