subagent-driven-development

Executes implementation plans by dispatching fresh implementer and reviewer subagents per task.

Updated Jul 15, 2026
One-click install
npx skills add https://github.com/em411/supercodex --skill subagent-driven-development-em411
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/em411/supercodex/tree/main/skills/subagent-driven-development
Command: npx skills add https://github.com/em411/supercodex --skill subagent-driven-development-em411

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Executing a multi-task implementation plan in one session risks context pollution, skipped reviews, and lost progress after compaction. This Skill orchestrates plan execution by dispatching a fresh implementer subagent per task, a task reviewer after each, and a final whole-branch review, with a durable progress ledger for recovery. ## Core Features & Use Cases - Per-task subagent dispatch: Each task gets a fresh Codex or Claude implementer with a file-based task brief, keeping the controller's context clean. - Two-gate review loop: Every task passes spec-compliance and code-quality review by a Claude reviewer reading a generated diff package, with fix cycles for Critical/Important findings. - Durable progress ledger: Completed tasks are recorded in a git-ignored ledger file so work is never re-dispatched after context compaction. - Use Case: You have a 6-task implementation plan from a planning session. This Skill extracts each task brief to a file, dispatches Codex implementers with tiered model selection, reviews each diff, and finishes with a whole-branch review before merge. ## Quick Start Use subagent-driven development to execute the implementation plan in docs/plans/feature-plan.md task by task with review after each task.

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 an implementation plan with subagents?

Read the plan once, create todos for all tasks, then dispatch a fresh implementer subagent per task using a file-based task brief. After each task, generate a diff package and dispatch a task reviewer, looping on fixes until approved.

What is the difference between subagent-driven development and executing plans?

Subagent-driven development stays in the current session with a fresh subagent per task and continuous execution. Executing plans runs in a parallel session with human-in-the-loop checkpoints between tasks.

How does the skill recover progress after context compaction?

It maintains a progress ledger at .superpowers/sdd/progress.md recording each completed task with its commit range. After compaction, the controller trusts the ledger and git log over its own memory and resumes at the first incomplete task.

What happens when the Codex implementer fails or is unavailable?

The failure ladder retries once via --resume-last, then falls back to a Claude implementer subagent with the substitution announced and the ledger entry marked claude-fallback. A failed preflight switches the whole plan to Claude implementers.

When should I not use subagent-driven development?

Avoid it when tasks are tightly coupled and cannot be implemented independently, when no implementation plan exists yet, or when you prefer a parallel session with human checkpoints between tasks.