subagent-driven-development

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

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/erwinv2k-TKG/AgentesVSC --skill subagent-driven-development-erwinv2k-tkg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/erwinv2k-TKG/AgentesVSC/tree/main/packs/superpowers/skills/subagent-driven-development
Command: npx skills add https://github.com/erwinv2k-TKG/AgentesVSC --skill subagent-driven-development-erwinv2k-tkg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Executing a multi-task implementation plan in a single session often pollutes context, skips reviews, and lets quality drift between tasks. This Skill orchestrates plan execution by dispatching a fresh subagent per task with isolated context, then enforcing a two-stage review (spec compliance first, then code quality) after every task. ## Core Features & Use Cases - Fresh subagent per task: Each task runs in an isolated context with exactly the instructions and scene-setting it needs, preserving the controller's context for coordination. - Two-stage review gates: A spec compliance reviewer verifies nothing is missing or extra, then a code quality reviewer checks maintainability before the task is marked complete. - Status handling and escalation: Implementer subagents report DONE, DONE_WITH_CONCERNS, NEEDS_CONTEXT, or BLOCKED, with defined recovery paths including model upgrades and task splitting. - Use Case: Given a written plan with five independent tasks, the controller extracts all task text, creates a todo list, dispatches implementer and reviewer subagents per task, and finishes with a final whole-implementation code review. ## Quick Start Use the subagent-driven-development skill 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?

Read the plan once, extract every task with full text and context, and create a todo list. Dispatch an implementer subagent per task, then run a spec compliance review and 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 automatic review checkpoints. Executing plans uses a parallel session with a handoff, which suits work that should not stay in the current session.

Which model should implementer subagents use for each task?

Use a cheap fast model for mechanical tasks touching one or two files with a clear spec, a standard model for multi-file integration work, and the most capable model for architecture, design, and review tasks.

What happens when an implementer subagent reports BLOCKED?

Assess the blocker before retrying: provide more context for context problems, re-dispatch with a more capable model for reasoning-heavy tasks, split oversized tasks, or escalate to the human if the plan itself is wrong. Never force the same model to retry unchanged.

Can I dispatch multiple implementer subagents in parallel?

No. The skill explicitly forbids dispatching multiple implementation subagents in parallel because they conflict with each other. Tasks run sequentially, each gated by spec compliance and code quality reviews.

Why must spec compliance review come before code quality review?

Spec compliance confirms the implementation matches requirements exactly, with nothing missing or extra. Reviewing code quality before correctness wastes effort on code that may need to change to meet the spec.