deepwork-subagent-driven-development

Coordinates focused subagent workers to execute approved implementation plans with evidence-based verification.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Executing a multi-task implementation plan in a single context often leads to lost focus, context bloat, and unverified results. This Skill orchestrates focused subagent workers with self-contained briefs so each task gets isolated execution context while the controller verifies actual outcomes against acceptance criteria. ## Core Features & Use Cases - Outcome-Oriented Delegation: Dispatch workers with self-contained briefs covering goals, acceptance criteria, owned files, and constraints, while allowing bounded evidence-based equivalent implementations. - Evidence-Based Verification: Inspect actual changed files and run proportionate checks instead of relying on status labels, mandatory review gates, or universal test transcripts. - Git and Safety Boundaries: Enforce strict rules so workers never commit, push, or perform Git writes without explicit user authorization, and escalate decisions affecting scope, security, or public APIs. - Use Case: You have an approved plan with five independent tasks. Dispatch focused workers per task or wave, integrate their returned diffs, run targeted verification, and request review only where risk warrants it. ## Quick Start Use the deepwork-subagent-driven-development skill to execute the approved implementation plan by dispatching focused workers for each independent task.

Frequently Asked Questions about deepwork-subagent-driven-development

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

FAQPage Schema
How do I execute an implementation plan with subagents?▼

Give each worker a self-contained brief with the goal, acceptance criteria, owned files, dependencies, and constraints. After work returns, inspect the actual changed files and evidence, resolve integration issues, and verify the outcome with proportionate checks.

When should I use subagent-driven development versus direct execution?▼

Use delegation when tasks benefit from isolated execution context and have clear boundaries. Direct execution is valid when a task is small, tightly coupled to controller context, or cheaper to complete than to brief and reconcile.

Can subagent workers commit or push code changes?▼

No. Workers do not stage, commit, push, tag, rebase, or release unless the user explicitly authorized that exact operation and the worker policy permits it. Implement or fix requests never imply commit authorization.

Is a code review required after every subagent task?▼

No. Review is requested only when risk, uncertainty, change shape, or user instruction makes independent review useful. A proven low-risk result need not wait for an optional reviewer, and reviewer approval is not a substitute for evidence.

What happens when a subagent worker reports BLOCKED or NEEDS_CONTEXT?▼

Status labels are informational, not gates. Resolve correctness concerns from code and requirements, supply missing context, change the model or task boundary if the work exceeds the worker, and escalate decisions in the defined stop classes.