subagent-driven-development

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

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/CYRUS-pinto/pi-bot --skill subagent-driven-development-cyrus-pinto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/CYRUS-pinto/pi-bot/tree/main/.agents/skills/subagent-driven-development
Command: npx skills add https://github.com/CYRUS-pinto/pi-bot --skill subagent-driven-development-cyrus-pinto

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 a fresh subagent with isolated context, enforcing review gates, and tracking progress in a persistent ledger. ## Core Features & Use Cases - Per-task subagent dispatch: Each plan task gets a fresh implementer subagent with a file-based task brief, keeping the controller's context clean for coordination. - Two-stage review gates: Every task diff is reviewed for spec compliance and code quality, followed by a whole-branch final review on the most capable model. - Bounded fix loop with escalation: Up to five fix rounds per task, resuming the original implementer for rounds 1-3 and escalating to a more capable model for rounds 4-5, with adjudicated rulings recorded in a ledger. - Use Case: You have a written implementation plan with eight independent tasks. This Skill creates a git worktree, dispatches implementer and reviewer subagents per task, logs progress to a ledger that survives context compaction, and finishes with a whole-branch review before merge. ## Quick Start Use the subagent-driven-development skill 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 AI subagents?

Dispatch a fresh implementer subagent per task with a file-based task brief, then dispatch a task reviewer against the diff. Track completions in a ledger file and run a whole-branch review after all tasks finish.

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?

Critical and Important findings trigger up to five fix rounds. Rounds 1-3 resume the original implementer; rounds 4-5 dispatch a fresh implementer on a more capable model. Each round ends with a scoped re-review of the fix diff.

Why does the skill use a ledger file instead of todos alone?

Conversation memory does not survive context compaction, and controllers without a ledger have re-dispatched completed task sequences. The ledger records task completions, fix rounds, and rulings so progress is recoverable from git history.

Can implementer subagents spawn their own reviewers?

No. The dispatch contract forbids implementers from spawning any subagents, including reviewers. Review arrives only from the controller after the implementer reports, since worker-spawned reviewers duplicate the task review at full cost.

What are the limitations of subagent-driven development?

It requires a written implementation plan with mostly independent tasks and does not support parallel implementation dispatches due to conflict risk. It stops only for destructive operations, security-sensitive actions, external side effects, or unrecoverable plan defects.