subagent-driven-development

Executes implementation plans by dispatching fresh subagents per task with two-stage review.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/abhinaaaavvv/dotfiles --skill subagent-driven-development-abhinaaaavvv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/abhinaaaavvv/dotfiles/tree/main/.agents/skills/subagent-driven-development
Command: npx skills add https://github.com/abhinaaaavvv/dotfiles --skill subagent-driven-development-abhinaaaavvv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Executing a multi-task implementation plan in a single session often leads to context pollution, skipped reviews, and inconsistent quality. This Skill orchestrates plan execution by dispatching a fresh subagent for each task and enforcing a two-stage review after every task. ## Core Features & Use Cases - Fresh subagent per task: Each task runs in an isolated context with exactly the instructions and context it needs, preserving the controller's context for coordination. - Two-stage review loop: A spec compliance review runs first, followed by a code quality review, with fix-and-re-review loops until approval. - Status handling and model selection: Implementer subagents report DONE, DONE_WITH_CONCERNS, NEEDS_CONTEXT, or BLOCKED, and the controller escalates, re-dispatches, or switches model capability accordingly. - Use Case: Given a written plan with five independent tasks, the controller extracts all tasks into a todo list, dispatches implementer and reviewer subagents per task, and finishes with a final whole-implementation code review. ## Quick Start Use subagent-driven development to execute the implementation plan in docs/plans/feature-plan.md task by task in this session.

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 an implementation plan with subagents?▼

Extract all tasks from the plan into a todo list, then dispatch a fresh implementer subagent per task with the full task text and context. After each task, run a spec compliance review followed by a code quality review before marking the task complete.

What is the difference between subagent-driven development and executing plans?▼

Subagent-driven development runs in the same session with a fresh subagent per task and no human-in-loop between tasks. Executing plans uses a parallel session with a context handoff, which suits different coordination needs.

When should I not use subagent-driven development?▼

Avoid it when tasks are tightly coupled and cannot be implemented independently, when no implementation plan exists yet, or when you prefer a parallel session workflow. Brainstorm or write the plan first in those cases.

What happens when an implementer subagent reports BLOCKED?▼

The controller assesses the blocker: provide more context and re-dispatch, switch to a more capable model, break the task into smaller pieces, or escalate to the human if the plan itself is wrong. Never force the same model to retry unchanged.

Why must spec compliance review run before code quality review?▼

Spec compliance confirms the implementation matches requirements with nothing missing or extra, which must hold before judging code quality. Reviewing quality first wastes effort on code that may need rework to meet the spec.