subagent-driven-development

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

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/marcocpt/trae_skills --skill subagent-driven-development-marcocpt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/marcocpt/trae_skills/tree/main/subagent-driven-development
Command: npx skills add https://github.com/marcocpt/trae_skills --skill subagent-driven-development-marcocpt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Executing a multi-task implementation plan in a single context leads to context pollution, inconsistent quality, and skipped reviews. This Skill orchestrates plan execution by dispatching a fresh subagent for each independent task, enforcing a two-stage review (spec compliance, then code quality) before any task is marked complete. ## Core Features & Use Cases - Isolated Task Execution: Each task runs in a fresh subagent with precisely curated context, preventing cross-task contamination and preserving the controller's coordination context. - Two-Stage Review Gates: Every task passes a spec-compliance review (verifying nothing missing or extra) followed by a code-quality review, with fix-and-re-review loops until both pass. - Status-Based Handling: Implementer subagents report DONE, DONE_WITH_CONCERNS, NEEDS_CONTEXT, or BLOCKED, and the controller responds with targeted actions such as re-dispatching with a stronger model or splitting oversized tasks. - Use Case: You have a written plan with five independent tasks. The controller extracts all task text upfront, dispatches an implementer subagent per task, runs both review stages after each, and finishes with a final whole-implementation code review. ## Quick Start Use subagent-driven development to execute the implementation plan in docs/plans/feature-plan.md, dispatching a fresh subagent for each task with spec and quality 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?

Extract the full text of every task from the plan upfront, then dispatch a fresh implementer subagent per task with complete 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 in parallel sessions?

Subagent-driven development runs in the same session with no context switching, dispatching fresh subagents per task with automated review checkpoints. Parallel-session execution hands tasks to separate sessions, requiring manual handoffs between them.

When should I not use subagent-driven development?

Avoid it when tasks are tightly coupled and cannot be executed independently, or when no written implementation plan exists yet. In those cases, brainstorm or write the plan first, or execute manually.

Why should spec review come before code quality review?

Spec compliance confirms the right thing was built before evaluating how well it was built. Reviewing code quality first wastes effort on code that may need to change to meet the spec, so the order is strictly enforced.

What happens when an implementer subagent reports BLOCKED?

The controller evaluates the cause: provide more context and re-dispatch, re-dispatch with a stronger model, split the task into smaller parts, or escalate to a human if the plan itself is flawed. Never retry unchanged.