subagent-driven-development

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

Updated Jul 21, 2026
One-click install
npx skills add https://github.com/afonsoft/gamehub --skill subagent-driven-development-afonsoft
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/afonsoft/gamehub/tree/main/.claude/skills/subagent-driven-development
Command: npx skills add https://github.com/afonsoft/gamehub --skill subagent-driven-development-afonsoft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Executing a multi-task implementation plan manually pollutes your context, skips quality checks, and stalls between tasks. This Skill orchestrates plan execution by dispatching a fresh subagent per task with enforced spec compliance and code quality reviews after each one. ## Core Features & Use Cases - Fresh Subagent Per Task: Each task runs in an isolated subagent context with curated instructions, preventing context pollution and keeping the controller focused on coordination. - 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 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: You have a written plan with 5 independent tasks. The Skill extracts all tasks, dispatches an implementer subagent for each, runs both reviewers, and finishes with a final whole-implementation code review before merging the development branch. ## Quick Start Ask the AI to execute the implementation plan at docs/plans/feature-plan.md using subagent-driven development with per-task spec and quality 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?▼

Read the plan once, extract all tasks with full text into 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 a fresh subagent per task, and iterates faster without human check-ins between tasks. Parallel session execution hands off the plan to a separate session instead.

When should I not use subagent-driven development?▼

Avoid it for tightly coupled tasks requiring shared state, when no implementation plan exists, or when subagent support is unavailable. In those cases use manual execution, brainstorm first, or fall back to an executing-plans workflow.

What happens when an implementer subagent reports BLOCKED status?▼

The controller assesses the blocker: provide more context and re-dispatch for context problems, use a more capable model for reasoning-heavy tasks, break oversized tasks into smaller pieces, or escalate to the human if the plan itself is wrong.

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

Spec compliance verifies the implementer built exactly what was requested with nothing missing or extra. Reviewing code quality first wastes effort on code that may need rework to match the spec, so quality review only starts after compliance passes.