subagent-driven-development

Executes implementation plans by dispatching fresh subagents per task with two-stage review.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/NT-boop-star/BRMV-tract --skill subagent-driven-development-nt-boop-star
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/NT-boop-star/BRMV-tract/tree/main/antigravity/skills/subagent-driven-development
Command: npx skills add https://github.com/NT-boop-star/BRMV-tract --skill subagent-driven-development-nt-boop-star

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Executing a multi-task implementation plan in a single session often leads to context pollution, skipped reviews, and inconsistent quality. This Skill orchestrates plan execution by dispatching a fresh subagent for each task and enforcing a two-stage review (spec compliance, then code quality) after every task. ## Core Features & Use Cases - Fresh Subagent Per Task: Each task runs in an isolated subagent context with curated instructions, preventing context pollution and preserving the controller's context for coordination. - Two-Stage Review Gates: A spec compliance reviewer verifies the code matches requirements before a code quality reviewer assesses maintainability, with fix-and-re-review loops until approval. - Status-Based Escalation Handling: Implementer subagents report DONE, DONE_WITH_CONCERNS, NEEDS_CONTEXT, or BLOCKED, and the controller responds with more context, a more capable model, or task decomposition. - Use Case: You have a written implementation plan with 5 mostly independent tasks. This Skill extracts all tasks, dispatches an implementer subagent for each, runs spec and quality reviews after each, and finishes with a final whole-implementation review before merging the branch. ## Quick Start Use subagent-driven development to execute the implementation plan at docs/plans/feature-plan.md task by task in this session.

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?

Read the plan once, extract all tasks with full text into a todo list, then dispatch a fresh implementer subagent per task with the complete task text and context. After each task, run a spec compliance review followed by a code quality review before marking it complete.

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

Subagent-driven development runs in the same session with a fresh subagent per task and automatic two-stage reviews, enabling faster iteration. Executing plans uses a parallel session with a handoff, which suits work you want isolated from your current context.

When should I not use subagent-driven development?

Avoid it when tasks are tightly coupled and cannot be implemented independently, when no implementation plan exists yet, or when you want execution in a separate parallel session. In those cases, brainstorm or write a plan first, or use the executing-plans workflow.

What happens when an implementer subagent reports BLOCKED?

The controller assesses the blocker: provide more context and re-dispatch for context problems, re-dispatch with a more capable model for reasoning-heavy tasks, break oversized tasks into smaller pieces, or escalate to the human if the plan itself is wrong.

Why must spec compliance review come before code quality review?

Spec compliance confirms the implementation matches requirements with nothing missing or extra, which must be established before judging code quality. Reviewing quality first wastes effort on code that may need to change to meet the spec.