skills.rest
Shubh2310-developer
Shubh2310-developerCOMMUNITY
Explore all skills by this author →
GitHub

subagent-driven-development

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

2|Updated Jan 10, 2026
Search Tags:#tdd#code review#workflow orchestration#implementation plan#task execution#subagent#spec compliance
One-click install
npx skills add https://github.com/Shubh2310-developer/ENGUNITYCORE --skill subagent-driven-development-shubh2310-developer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/Shubh2310-developer/ENGUNITYCORE/tree/main/.claude/skills/subagent-driven-development
Command: npx skills add https://github.com/Shubh2310-developer/ENGUNITYCORE --skill subagent-driven-development-shubh2310-developer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Executing a multi-task implementation plan manually risks context pollution, skipped reviews, and inconsistent quality across tasks. This Skill orchestrates plan execution by dispatching a fresh subagent for each task and enforcing a two-stage review (spec compliance, then code quality) after every task. ## Core Features & Use Cases - Fresh Subagent Per Task: Each task runs in an isolated subagent context, preventing cross-task confusion and context pollution. - Two-Stage Review Gates: A spec compliance reviewer verifies the code matches requirements exactly, then a code quality reviewer assesses maintainability before the task is marked complete. - Prompt Templates Included: Ready-to-use templates for the implementer, spec reviewer, and code quality reviewer subagents. - Use Case: You have a written plan with 5 independent tasks. This Skill extracts all tasks into a todo list, dispatches an implementer subagent per task, runs both review loops until approved, and finishes with a final whole-implementation code review. ## Quick Start Use subagent-driven development to execute the implementation plan in 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?▼

Extract all tasks from the plan into a todo list, then dispatch a fresh implementer subagent per task with the full 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?▼

Subagent-driven development runs in the same session with a fresh subagent per task and automatic two-stage reviews, enabling faster iteration. Executing plans runs in a parallel session with a handoff, which suits work you want isolated from the current context.

When should I not use subagent-driven development?▼

Avoid it when tasks are tightly coupled and cannot be implemented independently, when no written implementation plan exists yet, or when you prefer a parallel session. In those cases, brainstorm or write the plan first, or use the executing-plans workflow.

Why run spec compliance review before code quality review?▼

Spec compliance confirms the implementer built exactly what was requested, nothing missing and nothing extra. Reviewing code quality first wastes effort if the implementation must change to match the spec, so quality review only starts after spec compliance passes.

What happens when a reviewer subagent finds issues?▼

The same implementer subagent fixes the reported issues, then the reviewer reviews again. This loop repeats until the reviewer approves, and the task is never marked complete while either review has open issues.

Related Skills

Explore More Software Engineering Skills→
tanveerriaztanveerriaz
1

prd-to-build-plan

Converts PRDs and feature requests into phased build plans with acceptance criteria.

Community
Basic
HexSleevesHexSleeves

staff-finishing-a-development-branch

Verify tests and present merge, pull request, keep, or discard options for a finished branch.

Community
Advanced
mokhtarabadimokhtarabadi
6

testing-strategy

Enforces test-driven development order and coverage gates for implementation tasks.

Community
Intermediate
nimeshgurungnimeshgurung

subagent-driven-development

Execute implementation plans by dispatching subagents with automated code reviews between tasks.

Community
Advanced