skill CX Codex

subagent-driven-development · neolabhq — Claude Code skill: one subagent per task

Q: How do I install subagent-driven-development in Claude?

With the skills CLI: `npx skills add NeoLabHQ/context-engineering-kit --skill subagent-driven-development -a claude-code`. The skill file lands at `~/.claude/skills/subagent-driven-development/SKILL.md`.

Runs an implementation plan through fresh subagents and puts code review between tasks, so context stays clean and issues surface early.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓

npx skills add NeoLabHQ/context-engineering-kit --skill subagent-driven-development -a claude-code

Open on GitHub

What subagent-driven-development does

The skill takes a plan file and executes it with subagents: one agent per task or issue, then a review of the code and output after each task or batch. The parent session keeps its context clean because every subagent starts fresh. No human sits between tasks, which is where the speed comes from.

Two modes. Sequential is for tasks that depend on each other: one agent per task, review after each one. Parallel is for unrelated work — different files, subsystems, bugs — with one agent per problem domain and review after a batch. For batches the skill advises starting with the first three tasks, then reporting back and waiting for feedback.

Red flags are spelled out: never skip review between tasks, never dispatch several implementation subagents in parallel because they conflict, and never fix a failed task by hand — that is what a fix subagent is for. Hit a blocker mid-batch and the skill tells you to stop and ask instead of guessing. Finishing the work requires the superpowers:finishing-a-development-branch sub-skill; without it the last step does not run.

What it helps with

execute a plan of independent tasks without polluting session context
review code after every task instead of at the end
run several unrelated bugs in parallel across subsystems
fix review findings with a dedicated subagent
close out the branch through finishing-a-development-branch

Example prompts for the agent

Use subagent-driven-development to execute the plan in plan.md
Run these three independent bugs through subagent-driven-development in parallel
Execute the plan with subagent-driven-development and review after each task

How to install subagent-driven-development

1Skills CLI (Vercel)

npx skills add NeoLabHQ/context-engineering-kit --skill subagent-driven-development -a claude-code

2Manually: put the files in place

~/.claude/skills/subagent-driven-development/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/subagent-driven-development/

1Skills CLI (Vercel)

npx skills add NeoLabHQ/context-engineering-kit --skill subagent-driven-development -a codex

2Manually: put the files in place

.agents/skills/subagent-driven-development/SKILL.md

For all projects use ~/.agents/skills/

1Skills CLI (Vercel)

npx skills add NeoLabHQ/context-engineering-kit --skill subagent-driven-development -a cursor

2Manually: put the files in place

.cursor/skills/subagent-driven-development/SKILL.md

Cursor also reads .agents/skills/ and .claude/skills/

1GitHub CLI

gh skill install NeoLabHQ/context-engineering-kit subagent-driven-development

2Manually: put the files in place

.github/skills/subagent-driven-development/SKILL.md

1Skills CLI (Vercel)

npx skills add NeoLabHQ/context-engineering-kit --skill subagent-driven-development -a gemini-cli

2Platform CLI

gemini skills install https://github.com/NeoLabHQ/context-engineering-kit --path skills/subagent-driven-development

Manually: put the files in place

.devin/skills/subagent-driven-development/SKILL.md

The legacy .windsurf/skills/ path still works

Skills CLI (Vercel)

npx skills add NeoLabHQ/context-engineering-kit --skill subagent-driven-development -a opencode

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about subagent-driven-development

How do I install subagent-driven-development in Claude?

With the skills CLI: npx skills add NeoLabHQ/context-engineering-kit --skill subagent-driven-development -a claude-code. The skill file lands at ~/.claude/skills/subagent-driven-development/SKILL.md.

What does subagent-driven-development do?

It executes an implementation plan by dispatching a fresh subagent per task and running code review between tasks or after a batch. Iteration gets faster and problems show up sooner.

How do sequential and parallel execution differ?

Sequential uses one agent per task with review after each, for coupled tasks. Parallel uses one agent per independent domain with review after a batch, for work with no shared files or dependencies.

subagent-driven-development by other authors comes first.

subagent-driven-development Jesse Vincent This skill runs an implementation plan through fresh subagents for independent tasks and reviews each result. Use it for multi-step work in one session. CX Codex 237,746installs subagent-driven-development GanyuanRan Runs a written implementation plan by dispatching a fresh subagent for each task, then reviewing it twice: spec compliance first, code quality second. CX Codex +1 ★ 1,384repo stars doubt-driven-development addyosmani This skill sends non-trivial decisions to a fresh-context reviewer looking for flaws. Use it before changes that are hard to undo or costly to debug later. CX Codex +1 56,700installs test-driven-development Jesse Vincent This skill guides an agent through test-first development: verify a test fails, write the smallest passing change, then refactor. It covers features, bug fixes, and behavior changes. CX Codex 259,292installs source-driven-development addyosmani Grounds agent coding decisions in official documentation. It helps verify framework APIs against detected versions and avoids outdated patterns from model training data. CX Codex +1 58,200installs content-driven-development adobe A skill for AEM Edge Delivery Services work: find or create test content first, then write the code. Useful for blocks, styling and scripts.js changes. CX Codex +1 1,600installs context-driven-development Seth Hobson This skill keeps project context in conductor/, creates and checks its documents, and syncs them as work changes. Use it for setup or codebase onboarding. CX Codex 11,099installs hate LilMGenius Tears down a design, plan, or argument before you spend real effort on it. Pinpoints the single fatal flaw and the cheapest check to verify it. CX Codex +1 1,300installs

From the same set64

prompt-engineering Guides prompt design for agents, subagents, and LLM integrations. Helpful when building production templates, chain-of-thought prompts, or agent hooks. CX Codex +1 1,400installs agent-evaluation Framework for testing agents, prompts, and skills using multi-dimensional scoring rubrics and LLM-as-judge prompts. CX Codex +1 1,300installs plan-task Turns a rough task spec into a plan with acceptance criteria, an architecture overview and verifiable phases, each gated by a judge. CX Codex +1 1,300installs memorize Transfers insights from agent reflections and critique sessions into CLAUDE.md. Keeps your context file sharp by structuring lessons instead of bloating it with raw logs. CX Codex +1 1,300installs judge-with-debate The skill runs three independent judges who argue over a solution's score until they agree. Useful when a single pass feels too thin for a real verdict. CX Codex +1 1,300installs update-docs Updates project documentation based on uncommitted git changes or the latest commit. Keeps README files, docs/, and JSDoc comments synchronized with your codebase. CX Codex +1 1,300installs root-cause-tracing A skill that walks the agent backward through the call stack until it finds the original trigger, then fixes there instead of at the crash site. CX Codex +1 1,300installs critique The critique skill runs finished work past several AI judges: they review it independently, debate their findings, and agree on a shared list of issues. CX Codex +1 1,300installs