subagent-driven-development

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

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/Syedyasir001/RVULibPass --skill subagent-driven-development-syedyasir001
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/Syedyasir001/RVULibPass/tree/main/.agent/skills/library/subagent-driven-development
Command: npx skills add https://github.com/Syedyasir001/RVULibPass --skill subagent-driven-development-syedyasir001

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 errors compound. This Skill orchestrates plan execution by dispatching a fresh subagent per task and enforcing spec compliance and code quality reviews after each task. ## Core Features & Use Cases - Fresh subagent per task: Each task runs in 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 the code matches requirements before a code quality reviewer checks maintainability, with fix-and-re-review loops until approval. - Status handling and model selection: Implementers 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 task text, creates a todo list, dispatches implementer and reviewer subagents per task, and finishes with a final whole-implementation review before merging the branch. ## Quick Start Use subagent-driven development to execute the implementation plan in docs/plans/feature-plan.md task by task with reviews.

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 create a todo list. Dispatch a fresh implementer subagent per task with complete context, then run spec compliance and code quality reviews before marking each task complete.

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

Subagent-driven development stays in the same session with fresh subagents per task and continuous progress. Executing plans runs in a parallel session with a handoff, which suits work you want isolated from your current context.

When should I not use subagent-driven development?▼

Avoid it when tasks are tightly coupled and cannot be delegated independently, or when no implementation plan exists yet. Also never dispatch multiple implementation subagents in parallel, since they can conflict.

What should I do when an implementer subagent reports BLOCKED?▼

Assess the blocker: provide more context and re-dispatch for context problems, use 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.

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

Spec compliance confirms the implementation matches requirements with nothing missing or extra. Reviewing code quality first wastes effort on code that may need rework to meet the spec, so quality review only starts after compliance passes.