subagent-driven-development

Dispatch isolated subagents to implement plan tasks with per-task reviews.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/seankao31/dotfiles --skill subagent-driven-development-seankao31
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/seankao31/dotfiles/tree/main/agent-config/superpowers-overrides/subagent-driven-development
Command: npx skills add https://github.com/seankao31/dotfiles --skill subagent-driven-development-seankao31

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables executing complex implementation plans by dispatching independent subagents for each task within the same session, ensuring isolated context and structured progress.

Core Features & Use Cases

  • Per-task subagent orchestration: spawn dedicated implementer, spec-reviewer, and code-quality reviewer subagents for every task.
  • Three-stage review: enforce spec compliance, code quality, and codex cross-model review after each task.
  • Plan-to-delivery flow: supports parallel task handling while maintaining strict quality gates.

Quick Start

Dispatch an implementer subagent for each task and apply the three-stage review workflow.

Frequently Asked Questions about subagent-driven-development

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

FAQPage Schema
How do I orchestrate autonomous subagents for development tasks?

Autonomous subagent orchestration dispatches isolated implementer agents for each task within a single session. It coordinates per-task roles including spec reviewers and code-quality reviewers to ensure structured progress and strict quality gates.

What is the best way to automate code review during plan implementation?

Automated code review during implementation uses a three-stage workflow. It enforces spec compliance, checks code quality, and performs cross-model validation by dispatching dedicated reviewer subagents after every individual task is completed.

How does subagent-driven development maintain context isolation across tasks?

Subagent-driven development maintains context isolation by spawning independent subagents for each task within the same session. This ensures structured progress without cross-contamination of context between concurrent implementation tasks.

Can I use multiple reviewer roles for spec compliance and code quality checks?

Multiple reviewer roles are supported through dedicated spec-reviewer and code-quality reviewer subagents. These roles enforce spec compliance and code quality respectively, providing cross-model validation after each task implementation.

Do I need a predefined plan to dispatch implementer subagents?

A predefined plan is required to dispatch implementer subagents. The workflow supports a plan-to-delivery flow where tasks from the implementation plan are dispatched to isolated subagents with structured three-stage reviews.

When should I use subagent orchestration instead of sequential task execution?

Subagent orchestration should be used for complex implementation plans requiring parallel task handling and strict quality gates. It provides isolated context per task and three-stage reviews, unlike sequential execution which lacks autonomous role coordination.