subagent-driven-development

Installation
SKILL.md

Subagent-Driven Development

An orchestration pattern for executing multi-task implementation plans by dispatching one fresh subagent per task, reviewing each task through two gates (spec compliance, then code quality), and advancing only after both gates pass. The orchestrator stays lean -- it coordinates, briefs, reviews, and hands off. It never implements.

Core Principles

Principle Meaning
One fresh agent per task Each task gets a new subagent with curated context. No inherited conversation history, no accumulated drift. The agent sees only what the brief provides.
Two-stage review Every task passes through spec compliance (does it match the brief?) and then code quality (is it correct, clean, and tested?). Both must pass before advancing.
Structured hand-offs When task N produces artifacts that task N+1 needs, pass a compressed summary (diff, test manifest, notes) -- never raw conversation history.
Orchestrator stays lean The orchestrator reads the plan, dispatches agents, reviews output, and decides next steps. It does not implement, debug, or accumulate working-memory bloat.
Fail fast, fix forward When a review gate fails, return specific feedback to the subagent for a focused fix cycle. After two failed fix attempts, re-scope or escalate -- do not loop indefinitely.

When to Use

Situation Why this pattern fits
Written plan with 3+ sequential tasks Each task benefits from isolated execution and a review checkpoint
Related skills

More from krzysztofsurdy/code-virtuoso

Installs
12
GitHub Stars
17
First Seen
Apr 14, 2026