subagent-driven-development

Executes implementation plans by dispatching fresh subagents per task with per-task and final code reviews.

1|Updated Sep 10, 2026
One-click install
npx skills add https://github.com/thienty1207/Hotel_Staff --skill subagent-driven-development-thienty1207
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/thienty1207/Hotel_Staff/tree/main/.baron/core/skills/superpowers/subagent-driven-development
Command: npx skills add https://github.com/thienty1207/Hotel_Staff --skill subagent-driven-development-thienty1207

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 verification, and lost progress after compaction. This Skill orchestrates plan execution by delegating each task to an isolated subagent, gating every task behind a spec-compliance and code-quality review, 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's context clean for coordination. - Structured review loop: Run a task reviewer after each task, a bounded five-round fix loop with scoped re-reviews, and a final whole-branch review on the most capable model. - Ledger-based recovery: Track completions, fix rounds, and parked findings in a per-plan workspace ledger so progress survives context compaction. - Use Case: Given a written implementation plan with eight independent tasks, execute all of them in the current session: each task is implemented, tested, reviewed, and committed by subagents, ending with a clean final review before finishing the branch. ## Quick Start Use subagent-driven development to execute the implementation plan at docs/plans/feature-plan.md task by task with 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 an implementation plan with subagents?

Dispatch a fresh implementer subagent per task with a task brief file, then run a task reviewer on the diff after each task. Track completions in a ledger file and finish with a whole-branch review on the most capable model.

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

Use it when you have an implementation plan with mostly independent tasks and want to stay in the current session. Tightly coupled tasks or missing plans call for manual execution or brainstorming first.

How does the fix loop work when a task review finds issues?

Rounds one through three resume the original implementer with the findings; rounds four and five dispatch a fresh implementer on a more capable model. Each round ends with a scoped re-review, and after five rounds open findings are adjudicated and parked or escalated.

What happens if the session loses context or gets compacted mid-plan?

Progress is tracked in a per-plan ledger file under .superpowers/sdd/, so completed tasks are never re-dispatched. After compaction, trust the ledger and git log over recollection to resume at the first incomplete task.

Which model should implementer and reviewer subagents use?

Always specify the model explicitly: 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.

Can I dispatch multiple implementation subagents in parallel?

No. Implementation subagents must run sequentially because parallel implementers create conflicting changes. Reviews and fix dispatches also run one at a time per task.