subagent-driven-development

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

2|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/MoofonLi/dev-ready --skill subagent-driven-development-moofonli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/MoofonLi/dev-ready/tree/main/src/dev_ready/templates/claude/skills/subagent-driven-development
Command: npx skills add https://github.com/MoofonLi/dev-ready --skill subagent-driven-development-moofonli

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 coordinates the whole run: a fresh implementer subagent per task, a spec-and-quality review after each task, 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 a brief file, a report file, and explicit model selection, keeping the controller's context clean for coordination. - Two-stage review pipeline: A task reviewer checks spec compliance and code quality per task; a final whole-branch reviewer audits the complete diff before merge. - Bounded fix loop with adjudication: Up to five fix rounds per task with scoped re-reviews; unresolved findings are ruled on and recorded in the ledger rather than silently dropped. - Use Case: You have a written implementation plan with eight tasks. Run this Skill to execute every task autonomously, reviewing and fixing each diff, and finish with a clean reviewed branch plus a rulings report. ## Quick Start Ask your agent to use subagent-driven development to execute the implementation plan at docs/plans/feature-plan.md.

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 a task brief file and report file, then dispatch a task reviewer against the diff. Track progress in a ledger file so completed tasks are never re-dispatched after context compaction.

What is the difference between subagent-driven development and executing plans in a parallel session?

Subagent-driven development stays in the current session with a fresh subagent per task and review after each task, giving faster iteration without human-in-loop between tasks. Parallel session execution suits work that should run independently of your session.

How many fix rounds should a code review loop allow?

This workflow caps the fix loop at five rounds per task: rounds 1-3 resume the original implementer, rounds 4-5 dispatch a fresh implementer on a more capable model. After round 5, remaining findings are adjudicated and recorded with rulings.

Which model should I use for implementation subagents?

Use the cheapest model that fits the task: cheap tiers for mechanical single-file work or transcription from complete plan text, standard models for multi-file integration, and the most capable model for architecture and the final whole-branch review. Always specify the model explicitly when dispatching.

When should I not use subagent-driven development?

Avoid it when tasks are tightly coupled and cannot be split into independent units, when no implementation plan exists yet, or when the work needs a parallel session instead of the current one. Tightly coupled work is better done manually or after brainstorming.