subagent-driven-development

Executes approved implementation plans task-by-task with bounded subagent delegation and review gates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Implementing a large approved plan in one pass often leads to skipped verification, uncontrolled delegation, and subagents making unauthorized git changes. This Skill enforces a disciplined task-by-task execution loop with safe subagent delegation and review gates. ## Core Features & Use Cases - Sequential Task Execution: Works through an approved plan one task at a time, requiring each task to be integrated and checked before starting the next. - Bounded Subagent Delegation: Delegates only independent implementation or investigation work, giving each subagent the task, relevant files, acceptance criteria, and a verification command. - Git Safety Controls: Restricts subagents from git writes so staging, committing, tagging, pushing, and history edits stay with the user-approved coordinator. - Use Case: After approving a multi-task refactoring plan in dsmm deepwork mode, use this Skill to delegate each bounded task to subagents, inspect their changes, run per-task verification, and request final review when all tasks complete. ## Quick Start Use the subagent-driven-development skill to execute my approved implementation plan task by task with delegated subagents and verification after 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 an approved implementation plan with subagents?▼

Work through the plan one task at a time, delegating only bounded, independent work to subagents with the task, relevant files, acceptance criteria, and a verification command. Inspect each subagent's changes and run verification before marking the task complete.

How to delegate coding tasks to subagents safely?▼

Give each subagent a bounded task with explicit acceptance criteria and a verification command, and forbid git writes. Staging, committing, tagging, pushing, rebasing, and history edits remain with the user-approved coordinator.

Can subagents commit or push code changes with this workflow?▼

No. Subagents must avoid all git writes including staging, committing, tagging, pushing, rebasing, and history edits. Those operations stay exclusively with the user-approved coordinator to preserve control over the repository.

When should I use subagent-driven development?▼

Use it in dsmm deepwork mode after an implementation plan has been approved. It is designed for multi-task plans where each task can be delegated, independently verified, and integrated sequentially before final review.

What happens if a subagent's changes conflict with the plan?▼

After each subagent returns, the coordinator inspects the changed files, resolves any conflicts or mismatches, and runs the task's verification command. The task is only marked complete once verification passes.