subagent-driven-development

Name: subagent-driven-development
Availability: InStock
Author: ReinaMacCredy

Dispatch per-task subagents and enforce two-stage reviews for implementation plans.

223|23|Updated Dec 19, 2025

Search Tags:#subagents #code-quality #plan-execution #spec-compliance #two-stage-review

Ready to run

npx skills add https://github.com/ReinaMacCredy/maestro --skill subagent-driven-development-reinamaccredy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/ReinaMacCredy/maestro/tree/main/skills/subagent-driven-development
Command: npx skills add https://github.com/ReinaMacCredy/maestro --skill subagent-driven-development-reinamaccredy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates context pollution and quality drift by using specialized subagents for implementation and review.

Quick Start

Use this skill when you have an implementation plan and want to execute tasks with independent quality reviews.

Quick Start

Execute the plan in 'conductor/tracks/auth_20241215/plan.md' by dispatching implementer, spec reviewer, and code quality reviewer subagents for each task.

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 implementation plans with independent task reviews?▼

Dispatch specialized subagents for each task—one for implementation, one for spec compliance review, and one for code quality review. This approach isolates context, prevents quality drift, and enforces structured verification across your development plan.

What's the best way to prevent context pollution during multi-task development?▼

Use fresh subagent instances per task instead of maintaining a single agent across all work. Each subagent starts clean, reducing accumulated context drift and improving precision in both implementation and review stages.

How do I track task execution and maintain traceability in a multi-subagent workflow?▼

Implement TodoWrite-based task tracking to log each subagent's work, decisions, and review outcomes. This creates an auditable record that ties implementation tasks to their spec and code-quality verification results.

When should I use subagent-driven development instead of a single continuous agent?▼

Use this approach when your implementation plan has largely independent tasks requiring fast iteration and structured verification. It's most effective for complex projects where quality checks and spec compliance must be separated from coding work.

Do I need to define explicit prompts for spec compliance and code quality reviews?▼

Yes. This Skill requires explicit reviewer prompts tailored to your spec and code standards. Each subagent needs clear instructions to enforce consistent compliance and catch quality issues before they accumulate across tasks.

What are the limitations of dispatching multiple subagents per task?▼

Coordination overhead increases with task count, and subagent consistency depends on prompt clarity. This approach works best for medium-to-large plans with well-defined tasks; small, tightly coupled projects may not justify the added structure.