sadd-subagent-driven-development

Dispatch independent subagents for sequential and parallel task execution with automated code reviews.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/Gamezar/opencode-cek --skill sadd-subagent-driven-development-gamezar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sadd-subagent-driven-development
Source: https://github.com/Gamezar/opencode-cek/tree/main/plugins/sadd/skills/sadd-subagent-driven-development
Command: npx skills add https://github.com/Gamezar/opencode-cek --skill sadd-subagent-driven-development-gamezar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of executing complex plans or handling multiple independent issues efficiently by leveraging independent subagents for each task, ensuring focused execution and quality control through integrated code reviews.

Core Features & Use Cases

  • Sequential Execution: For tightly coupled tasks that must be done in order, dispatching agents one by one with reviews in between.
  • Parallel Execution: For unrelated tasks or issues, dispatching multiple agents concurrently to work on different domains simultaneously.
  • Integrated Code Review: Automatically triggers a code reviewer agent after each task or batch of tasks to catch issues early.
  • Use Case: Implementing a new feature with several distinct components. Each component can be developed by a dedicated subagent, with code reviews ensuring quality before moving to the next component or before final integration.

Quick Start

Use the sadd-subagent-driven-development skill to execute the tasks outlined in the plan file located at '/path/to/your/plan.md'.

Frequently Asked Questions about sadd-subagent-driven-development

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

FAQPage Schema
How do I automate parallel execution of independent development tasks?

Automate parallel execution by dispatching independent subagents concurrently to handle unrelated tasks or issues, which accelerates iteration cycles by working on different domains simultaneously.

What is the best way to manage sequential task execution for tightly coupled components?

Sequential task execution is managed by dispatching subagents one by one in order, ensuring tightly coupled components are developed sequentially with automated code reviews triggered between task completions.

How do code reviews work in an automated iterative development workflow?

Automated code reviews in an iterative development workflow trigger automatically after each task or batch of tasks completes, catching issues early before moving to the next component or final integration.

Can I use subagents to implement a new feature with several distinct components?

You can use subagents to implement a new feature with several distinct components by assigning each component to a dedicated subagent, utilizing specialized agent prompts for focused debugging and implementation.

How do I execute tasks outlined in a markdown plan file using subagents?

Execute tasks outlined in a plan file by providing the file path to the subagent driven development workflow, which facilitates iterative development by dispatching independent subagents for each discrete task.

When should I not use parallel execution for my development workflow?

Avoid parallel execution when tasks are tightly coupled and must be done in a specific order; instead, use sequential execution flows to manage dependencies and ensure proper implementation sequence.