skills.rest
macintorsten
macintorstenCOMMUNITY
Explore all skills by this author →
GitHub

subagent-driven-development

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

Updated Dec 23, 2025
Search Tags:#workflow#tdd#code review#implementation plan#subagent#spec compliance#task orchestration
One-click install
npx skills add https://github.com/macintorsten/aurapod --skill subagent-driven-development-macintorsten
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/macintorsten/aurapod/tree/main/.github/skills/subagent-driven-development
Command: npx skills add https://github.com/macintorsten/aurapod --skill subagent-driven-development-macintorsten

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Executing a multi-task implementation plan manually leads to context pollution, inconsistent quality, and skipped reviews. This Skill orchestrates plan execution by dispatching a fresh subagent for each task and enforcing spec compliance and code quality reviews after every task. ## Core Features & Use Cases - Fresh Subagent Per Task: Each task runs in an isolated subagent context, preventing confusion and cross-task interference. - Two-Stage Review Gates: A spec compliance reviewer verifies the code matches requirements before a code quality reviewer assesses maintainability, with fix-and-re-review loops until approval. - Prompt Templates Included: Ready-to-use templates for implementer, spec reviewer, and code quality reviewer subagents. - Use Case: You have a written plan with 5 independent tasks. Use this Skill to dispatch an implementer subagent per task, run both review stages after each, and finish with a final whole-implementation code 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.

Frequently Asked Questions about subagent-driven-development

High-intent search queries and answers about installing and using this skill.

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

Subagent-driven development stays 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 different coordination needs.

When should I not use subagent-driven development?▼

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

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

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

What happens when a reviewer subagent finds issues?▼

The same implementer subagent fixes the reported issues, then the reviewer reviews again. This fix-and-re-review loop repeats until approval, and the workflow never moves to the next task while either review has open issues.

Related Skills

Explore More Software Engineering Skills→
norrbackanorrbacka

requesting-code-review

Review completed code changes against requirements before merge.

Community
Intermediate
GuicedEEGuicedEE
5

finishing-a-development-branch

Verify tests, clean diffs, and prepare a development branch for review.

Official
Intermediate
mokhtarabadimokhtarabadi
6

testing-strategy

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

Community
Intermediate
erikstmartinerikstmartin
16

executing-plans

Coordinates end-to-end plan execution across sessions with batched tasks and logging checkpoints.

Community
Advanced