Agent skill · software engineering · aiskillstore
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
Why this skill is useful
Adds a detailed multi-step workflow for subagent-driven development that enhances task execution and quality assurance.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Subagent-Driven Development Execute plan by dispatching fresh subagent per task, with two-stage review after each: spec compliance review first, then code quality review. Core principle: Fresh subagent per task + two-stage review (spec then quality) = high quality, fast iteration When to Use vs. Executing Plans (parallel session): Same session (no context switch) Fresh subagent per task (no context pollution) Two-stage review after each task: spec compliance first, then code quality Faster iteration (no human-in-loop between tasks) The Process Prompt Templates ./implementer-prompt.md - Dispatch implementer subagent ./spec-reviewer-prompt.md - Dispatch spec compliance reviewer subagent ./code-quality-reviewer-prompt.md - Dispatch code quality reviewer subagent Example Workflow Advantages vs. Manual execution: Subagents follow TDD naturally Fresh context per task (no confusion) Parallel-safe (subagents don't interfere) Subagent can ask questions (before AND during work) vs. Executing Plans: Same session (no handoff) Continuous progress (no waiting) Review checkpoints automatic Efficiency gains: No file reading overhead (controller provides full text) Controller curates exactly what context is needed Subagent gets complete information upfront Questions surfaced before work begins (not after) Quality gates: Self-review catches issues before handoff Two-stage review: spec compliance, then code quality Review loops ensure fixes actually work Spec compliance prevents over/under-building Code quality ensures implementation is well-built Cost: More subagent invocations (implementer + 2 reviewers per task) Controller does more prep work (extracting all tasks upfront) Review loops add iterations But catches issues early (cheaper than debugging later) Red Flags Never: Skip reviews (spec compliance OR code quality) Proceed with unfixed issues Dispatch multiple implementation subagents in parallel (conflicts) Make subagent read plan file (provide full text instead) Skip scene-set …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/subagent-driven-development--6eab3f