subagent-driven-development

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

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/danieliudi/trackforge-os --skill subagent-driven-development-danieliudi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/danieliudi/trackforge-os/tree/main/.cursor/skills/subagent-driven-development
Command: npx skills add https://github.com/danieliudi/trackforge-os --skill subagent-driven-development-danieliudi

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 the whole plan: a fresh implementer subagent per task, a spec-and-quality review after each, a bounded fix loop, and a final whole-branch review, with a ledger file tracking every decision. ## Core Features & Use Cases - Per-task subagent dispatch: Each task gets a fresh implementer with an extracted brief file, isolated context, and an explicit model choice, so no task inherits session history. - Two-gate review loop: Every task passes a spec-compliance and code-quality review, with up to five fix rounds, model escalation on rounds 4-5, and adjudication of residual findings at the cap. - Ledger-based recovery: A per-plan workspace (.superpowers/sdd/<plan>/) holds briefs, reports, review packages, and a progress ledger, so work resumes correctly even after context compaction. - Use Case: You have a written implementation plan with eight tasks. Run this Skill to dispatch each task to an implementer, review every diff, fix findings through the loop, and finish with a whole-branch review before merging. ## 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 one fresh implementer subagent per task with a task brief file, then dispatch a task reviewer against the diff. Track progress in a ledger file and run a final whole-branch review when all tasks complete.

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 do I choose which model for each subagent task?

Match the model to task complexity: cheap models for mechanical single-file work, standard models for multi-file integration, and the most capable model for architecture and the final review. Always specify the model explicitly when dispatching.

What happens when a task review finds problems?

Findings enter a fix loop of up to five rounds: rounds 1-3 resume the original implementer, rounds 4-5 dispatch a fresh implementer on a more capable model. At the cap, remaining findings are adjudicated and recorded in the ledger.

How does progress survive context compaction?

A per-plan workspace under .superpowers/sdd stores a progress ledger, task briefs, reports, and review packages. After compaction, the ledger and git log are the source of truth for which tasks are complete.

Can implementer subagents spawn their own reviewers?

No. The process forbids implementers from dispatching any subagents, including reviewers. Review arrives only from the controller after the implementer reports, so worker-spawned reviews are treated as defects.