subagent-driven-development

Executes implementation plans by dispatching fresh subagents per task with staged reviews.

Updated Aug 13, 2026
One-click install
npx skills add https://github.com/Viranya2006/Lumen --skill subagent-driven-development-viranya2006
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/Viranya2006/Lumen/tree/main/SKILLS/subagent-driven-development
Command: npx skills add https://github.com/Viranya2006/Lumen --skill subagent-driven-development-viranya2006

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Executing a multi-task implementation plan in one session often pollutes context, skips verification, and loses progress after compaction. This Skill orchestrates plan execution by delegating each task to an isolated subagent, enforcing per-task spec and quality reviews, and tracking progress in a persistent ledger. ## Core Features & Use Cases - Fresh subagent per task: Dispatch implementer subagents with task briefs extracted to files, keeping the controller context clean for coordination. - Two-stage review gates: Run a task-scoped review (spec compliance plus code quality) after each task and a broad whole-branch review at the end, with a bounded five-round fix loop and escalation to more capable models. - Crash-safe progress ledger: Record completions, fix rounds, and parked findings in a per-plan workspace so work resumes correctly after context compaction. - Use Case: Given a written implementation plan with eight independent tasks, execute all of them in one session: each task is implemented, tested, reviewed, and committed by subagents while you only handle escalations and the final branch review. ## Quick Start Ask the AI to execute your implementation plan using subagent-driven development, pointing it at the plan file path.

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 a todo per task, then dispatch a fresh implementer subagent per task with a task brief file. After each task, generate a review package and dispatch a task reviewer before moving on.

When should I use subagent-driven development instead of executing a plan myself?

Use it when you have an implementation plan with mostly independent tasks and want to stay in the current session. If tasks are tightly coupled or no plan exists, manual execution or brainstorming first is the better path.

How does the review and fix loop work for each task?

Each task gets a spec-compliance and code-quality review. Findings trigger up to five fix rounds: rounds 1-3 resume the original implementer, rounds 4-5 use a fresh implementer on a more capable model, each followed by a scoped re-review.

What happens if my session context gets compacted mid-plan?

Progress is tracked in a per-plan ledger file under .superpowers/sdd/, not just in memory. After compaction, the controller reads the ledger and git log to resume at the first incomplete task instead of re-dispatching finished work.

Which model should I choose for implementer and reviewer subagents?

Always specify the model explicitly. Use cheap models for mechanical single-file tasks, standard models for multi-file integration, and the most capable model for architecture work and the final whole-branch review.

What are the limitations of subagent-driven development?

It requires a written implementation plan with mostly independent tasks and does not support parallel implementation subagents due to conflict risk. Structural failures that survive five fix rounds must be escalated to a human rather than resolved automatically.