subagent-driven-development

Distribute plan tasks to fresh subagents with two-stage reviews.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/AngelWings1997/altas --skill subagent-driven-development-angelwings1997
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/AngelWings1997/altas/tree/main/altas-workflow/references/superpowers/subagent-driven-development
Command: npx skills add https://github.com/AngelWings1997/altas --skill subagent-driven-development-angelwings1997

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables efficient execution of implementation plans by delegating each task to a fresh subagent within a single session, preventing context leakage and speeding iteration.

Core Features & Use Cases

  • Fresh subagent per task with isolated context
  • Two-stage review: spec compliance, then code quality
  • Guided task-flow templates for implementer, spec reviewer, and code-quality reviewer
  • End-to-end coordination from plan extraction to completion in the same session

Quick Start

Provide an implementation plan and let the system dispatch a fresh subagent per task, with per-task spec and quality 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 execute implementation plans efficiently using subagents?

Execute implementation plans by distributing independent tasks to fresh subagents within a single session. This approach prevents context leakage and speeds up iteration by isolating each task's execution environment.

What is the best way to automate iterative AI plan execution with per-task reviews?

Automated iterative AI plan execution is best handled by dispatching fresh subagents per task. The workflow enforces a two-stage review after each task, checking spec compliance first and then code quality.

Why use fresh subagents for independent plan tasks instead of a single context?

Fresh subagents prevent context leakage and speed up iteration when executing largely independent tasks. Each subagent operates with isolated context, ensuring that previous task data does not corrupt subsequent implementations.

How do I coordinate an end-to-end workflow from plan extraction to completion in one session?

Coordinate an end-to-end workflow by providing an implementation plan to the system. It dispatches fresh subagents per task, applies two-stage spec and quality reviews, and manages the entire flow to completion within the same session.

What are the limitations of using fresh subagents for plan execution?

The fresh subagent approach applies primarily to iterative plan execution where tasks are largely independent. If your implementation tasks require extensive shared context or complex cross-task dependencies, this isolated dispatch model may be limiting.

Do I need prompt templates to guide implementer and reviewer subagents?

Guided task-flow templates for the implementer, spec reviewer, and code-quality reviewer are provided natively. These templates structure the two-stage review process and ensure consistent spec compliance and code quality checks.