subagent-driven-development

Delegate independent implementation tasks to fresh subagents with automated reviews.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/sammy9322/ventura-dental-facturacion --skill subagent-driven-development-sammy9322
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/sammy9322/ventura-dental-facturacion/tree/main/.agents/skills/subagent-driven-development
Command: npx skills add https://github.com/sammy9322/ventura-dental-facturacion --skill subagent-driven-development-sammy9322

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manually executing multi-task implementation plans causes context pollution, inconsistent quality, and slow iteration as developers juggle multiple workstreams and inherited session history. This skill eliminates those inefficiencies by automating task delegation, isolated execution, and structured reviews for implementation plans.

Core Features & Use Cases

  • Isolated Per-Task Subagents: Dispatches a fresh, focused subagent for each independent task, so no task inherits irrelevant session context or history.
  • Automated Review Gates: Runs a spec compliance and code quality review after every task, with fix loops for issues, plus a final whole-branch review before merge.
  • End-to-End Workflow Management: Handles plan parsing, progress tracking, task brief generation, and review package creation, so you only need to provide the implementation plan.
  • Use Case: A development team with a 12-task feature plan can use this skill to execute all tasks in sequence without manual context switching, catching spec gaps and quality issues early to reduce post-merge bugs by 30% or more.

Quick Start

Use the subagent-driven-development skill to execute my attached implementation plan by delegating each independent task to a fresh isolated subagent, running a review after each task, and delivering a final merged, reviewed branch.

Frequently Asked Questions about subagent-driven-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate multi-task implementation plans without context pollution across sessions?

Automating multi-task implementation plans without context pollution is achieved by delegating each independent task to a fresh, isolated subagent, ensuring no inherited session history interferes with the current execution. This approach eliminates manual context switching and maintains consistent execution quality across all tasks.

What is the best way to run automated code reviews after each task in a development workflow?

Running automated code reviews after each task is handled by built-in review gates that check spec compliance and code quality immediately after subagent execution. The system automatically generates fix loops for any identified issues before moving to the next task, ensuring quality control throughout the development workflow.

How does progress tracking work for multi-task development workflows when sessions get compacted?

Progress tracking for multi-task development workflows uses durable tracking mechanisms that persist across context compactions, ensuring no task state is lost during long execution runs. It automatically parses the implementation plan, updates task completion status, and manages brief generation without manual intervention.

Can I use isolated subagents to execute a 12-task feature plan without manual coordination?

Using isolated subagents to execute a 12-task feature plan without manual coordination is the primary use case for this approach. It manages plan parsing, dispatches fresh subagents sequentially, runs per-task review gates, and delivers a final merged, reviewed branch automatically.

Does subagent delegation support model selection optimization to balance cost and performance?

Subagent delegation supports model selection optimization to balance cost and performance for different task types within the implementation plan. This allows you to assign appropriate models based on task complexity, reducing overall execution costs while maintaining the required code quality and spec compliance.

Why does manually executing multiple development tasks cause inconsistent code quality and slow iteration?

Manually executing multiple development tasks causes inconsistent quality and slow iteration because developers juggle multiple workstreams while inheriting unrelated session history, leading to context pollution. Automating task delegation and isolated execution eliminates these inefficiencies by enforcing structured, focused reviews after every task.