subagent-driven-development

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

Updated May 22, 2026
One-click install
npx skills add https://github.com/viniciuscs84/sdd-toolkit --skill subagent-driven-development-viniciuscs84
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/viniciuscs84/sdd-toolkit/tree/main/skills/subagent-driven-development%20copy
Command: npx skills add https://github.com/viniciuscs84/sdd-toolkit --skill subagent-driven-development-viniciuscs84

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Executing a multi-task implementation plan in a single AI session often leads to context pollution, skipped reviews, and inconsistent quality. This Skill coordinates plan execution by dispatching a fresh subagent for each task and enforcing spec compliance and code quality reviews after every task. ## Core Features & Use Cases - Fresh subagent per task: Each task runs in an isolated context with curated instructions, preventing cross-task confusion and preserving the controller's context. - Two-stage review gates: A spec compliance reviewer verifies the code matches requirements before a code quality reviewer assesses maintainability, with fix-and-re-review loops until approval. - Status-based escalation handling: Implementer subagents report DONE, DONE_WITH_CONCERNS, NEEDS_CONTEXT, or BLOCKED, and the controller responds with more context, a more capable model, or task decomposition. - Use Case: Given a written implementation plan with five independent tasks, execute all of them continuously in the current session, with each task implemented, tested, committed, and reviewed before moving on. ## Quick Start Use subagent-driven development to execute the implementation plan at docs/plans/feature-plan.md task by task with reviews after each task.

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 AI subagents?

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

What is the difference between subagent-driven development and executing plans in a parallel session?

Subagent-driven development stays in the current session with no context switch, dispatches a fresh subagent per task, and iterates faster without human-in-the-loop between tasks. Executing plans in a parallel session suits work that should run separately from the current conversation.

When should I not use subagent-driven development?

Avoid it when there is no implementation plan yet, when tasks are tightly coupled and cannot be delegated independently, or when you need a parallel session instead of same-session execution. Also never dispatch multiple implementer subagents in parallel due to conflicts.

What happens when an implementer subagent reports BLOCKED status?

Assess the blocker: provide more context and re-dispatch if it is a context problem, re-dispatch with a more capable model if more reasoning is needed, break the task into smaller pieces if too large, or escalate to the human if the plan itself is wrong.

Why must spec compliance review come before code quality review?

Spec compliance confirms the implementer built exactly what was requested, nothing missing and nothing extra. Reviewing code quality before correctness wastes effort, since code that fails spec compliance will be rewritten anyway.