subagent-driven-development

Orchestrates subagents to execute plan tasks with two-stage reviews.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/aRustyDev/git-atomic --skill subagent-driven-development-arustydev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/aRustyDev/git-atomic/tree/main/.claude/skills/method-subagent-dev-eng
Command: npx skills add https://github.com/aRustyDev/git-atomic --skill subagent-driven-development-arustydev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill orchestrates independent subagents to execute plan tasks with a two-stage review process, enabling fast iteration while maintaining quality.

Core Features & Use Cases

  • Two-stage review: spec compliance review followed by code quality review for every task.
  • Fresh subagents per task: isolates context to avoid cross-task contamination.
  • Plan-driven execution: derives tasks from a defined plan and tracks progress end-to-end.
  • Use Case: When implementing a multi-step feature, the skill splits work into independent tasks, runs them in sequence or parallel as appropriate, and validates results before proceeding.

Quick Start

Start by providing an implementation plan and a list of tasks to the skill, then let it dispatch subagents to perform each task with built-in reviews.

Frequently Asked Questions about subagent-driven-development

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

FAQPage Schema
How do I automate task orchestration for complex multi-step plans?

Task orchestration for complex plans is automated by dispatching independent subagents to execute individual tasks with a two-stage review process. This approach isolates context, validates spec compliance and code quality, and tracks progress until all tasks are approved.

What is a two-stage review process for plan execution?

A two-stage review process evaluates plan execution by first running a spec compliance review, followed by a code quality review for every task. This mechanism ensures implementation meets requirements before checking code standards, maintaining quality during rapid iteration.

How do I prevent cross-task context contamination when running parallel tasks?

Cross-task context contamination is prevented by dispatching fresh subagents for each individual task. Isolating subagent context ensures that independent tasks execute without interfering with each other, enabling clean incremental validation across the same session.

Can I use subagent-driven task execution for rapid feature iteration?

Subagent-driven task execution supports rapid feature iteration by splitting multi-step features into independent tasks, running them sequentially or in parallel, and validating results through automated reviews before proceeding to the next task.

What is the best way to track progress across multiple independent tasks?

Progress across multiple independent tasks is tracked end-to-end by deriving tasks from a defined plan and monitoring the two-stage review status. The system re-reviews failed tasks until approved, ensuring complete plan execution visibility.

Do I need a predefined implementation plan before starting subagent orchestration?

A predefined implementation plan and a list of tasks are required before starting subagent orchestration. The skill uses these inputs to dispatch implementer, spec-compliance reviewer, and code-quality reviewer subagents for each task.