subagent-driven-development

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

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/rub803030/examenprograma --skill subagent-driven-development-rub803030
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/rub803030/examenprograma/tree/main/EXAMEN_PROGRA_2-master/.agents/skills/subagent-driven-development
Command: npx skills add https://github.com/rub803030/examenprograma --skill subagent-driven-development-rub803030

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Executing a multi-task implementation plan in a single AI session leads to context pollution, skipped reviews, and inconsistent quality. This Skill orchestrates plan execution by dispatching a fresh subagent per task and enforcing spec compliance and code quality reviews after each one. ## 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: Every task passes a spec compliance review first, then a code quality review, with fix-and-re-review loops until approved. - Status-Based Escalation: 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: You have a written plan with 5 independent tasks. The controller extracts all tasks, dispatches an implementer subagent for each, runs both reviews per task, and finishes with a final whole-implementation code review before merging the branch. ## Quick Start Use subagent-driven development to execute the implementation plan at 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 AI subagents?▼

Extract all tasks from the plan with full text, create a todo list, then dispatch a fresh implementer subagent per task with 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 same session with no context switch, dispatches fresh subagents per task, and iterates faster without human-in-the-loop between tasks. Executing plans uses a separate parallel session with a handoff.

When should I not use subagent-driven development?▼

Avoid it when tasks are tightly coupled and cannot be split into independent units, when no implementation plan exists yet, or when you prefer a parallel session workflow. Tightly coupled work is better handled manually or by brainstorming first.

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

Assess the blocker: provide more context and re-dispatch if it is a context problem, use a more capable model if it needs more reasoning, 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 verifies the implementation matches requirements exactly, 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.