subagent-driven-development

Dispatch fresh subagents for each task with code reviews between tasks.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/Khoiwall/be_vidify --skill subagent-driven-development-khoiwall
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/Khoiwall/be_vidify/tree/main/.opencode/skill/subagent-driven-development
Command: npx skills add https://github.com/Khoiwall/be_vidify --skill subagent-driven-development-khoiwall

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates task execution by dispatching fresh subagents for each task with code reviews between tasks.

Core Features & Use Cases

  • Fresh subagent per task ensures isolation and prevents context pollution.
  • Integrated code-review checkpoints after each task to catch issues early.
  • End-to-end plan-driven execution with automatic coordination and final validation.

Quick Start

Run the subagent-driven-development workflow to execute a plan and iterate with per-task reviews.

Frequently Asked Questions about subagent-driven-development

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

FAQPage Schema
How does subagent-driven development orchestrate task execution?

Subagent-driven development orchestrates task execution by dispatching a fresh subagent for each task, followed by code-review checkpoints to catch issues early and ensure quality gates.

How do I automate code reviews between independent development tasks?

You automate code reviews by loading a plan and spawning implementation subagents for each task; the workflow collects reports, performs reviews, and applies fixes before proceeding.

Why use a fresh subagent per task in a plan-driven workflow?

Using a fresh subagent per task ensures isolation and prevents context pollution, allowing rapid iteration on largely independent tasks without degrading execution quality.

What's the best way to structure planning-heavy workflows with quality gates?

For planning-heavy workflows, the best approach is end-to-end plan-driven execution with automatic subagent coordination, integrated review checkpoints, and final validation.

When should I not use subagent-driven development for task automation?

You should avoid subagent-driven development for tasks that are heavily interdependent rather than largely independent, as the workflow is optimized for isolated subagent iteration.