subagent-driven-development

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

1|Updated Aug 27, 2025
One-click install
npx skills add https://github.com/IgorGanapolsky/Random-Timer --skill subagent-driven-development-igorganapolsky
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/IgorGanapolsky/Random-Timer/tree/main/.cursor/skills/subagent-driven-development
Command: npx skills add https://github.com/IgorGanapolsky/Random-Timer --skill subagent-driven-development-igorganapolsky

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Executing a multi-task implementation plan in one AI session leads to context pollution, skipped reviews, and lost progress after compaction. This Skill orchestrates plan execution by delegating each task to an isolated subagent with its own brief, enforcing a review gate after every task, and tracking progress in a persistent ledger. ## Core Features & Use Cases - Per-task subagent dispatch: Each plan task gets a fresh implementer subagent with an extracted task brief, a report file contract, and an explicit model choice, keeping the controller's context clean for coordination. - Two-stage review loop: Every task passes a spec-compliance and code-quality review, with a bounded five-round fix loop, scoped re-reviews, and adjudication rules for findings that survive the cap. - Ledger-based recovery: A per-plan workspace under .superpowers/sdd/ stores briefs, reports, review packages, and a progress ledger so work resumes correctly after context compaction. - Use Case: Given a written implementation plan with eight independent tasks, run this Skill to implement, test, review, and commit each task in a git worktree, then finish with a whole-branch review before merging. ## Quick Start Use the subagent-driven-development skill to execute the implementation plan at docs/superpowers/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 AI subagents?▼

Dispatch one fresh implementer subagent per task with an extracted task brief and report file, then dispatch a separate reviewer against the task diff. Track completions in a ledger file so progress survives context compaction.

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

Subagent-driven development runs in the same session but gives each task a fresh subagent with isolated context, plus a review after every task. Direct plan execution keeps everything in one context, which risks pollution and skipped reviews on long plans.

How many fix rounds should a code review loop allow?▼

This workflow caps the fix loop at five rounds per task: rounds one to three resume the original implementer, rounds four and five use a fresh implementer on a more capable model. After round five, remaining findings are adjudicated and parked with recorded rulings.

When should I not use subagent-driven development?▼

Avoid it when tasks are tightly coupled and cannot be implemented independently, when no written implementation plan exists, or when the work needs a parallel session instead of same-session coordination. Brainstorm or plan first in those cases.

How does the progress ledger prevent repeated work after compaction?▼

The ledger's first line names the plan file, and each completed task gets a completion line with its commit range. After compaction, the controller trusts the ledger and git log over memory, so finished tasks are never re-dispatched.