delegated-development — Claude Code skill: setup
The delegated-development skill runs a development plan through fresh subagents, with a specification check and a code-quality review after each task.
LicenseRef-Proprietary 142 installs ★ 50 updated 2026-01-05
npx skills add qodex-ai/ai-agent-skills --skill delegated-development -a claude-codeWhat delegated-development does
delegated-development turns an implementation plan into a sequence of separate tasks. A fresh subagent handles each one with its full task text and context, then implements the change, runs tests, reviews its own work, and commits the result.
Each completed task goes through two reviews. The first checks whether the implementation follows the specification; the second looks at code quality. A failed review sends the task back for fixes and another review. Once all tasks are done, a final reviewer checks the whole implementation, followed by superpowers:finishing-a-development-branch.
The workflow assumes a prepared plan, mostly independent tasks, and one active session. It is the wrong fit for tightly coupled work or a plan that still needs to be developed. Its prompt templates are ./implementer-prompt.md, ./spec-reviewer-prompt.md, and ./code-quality-reviewer-prompt.md.
What it helps with
- split an implementation plan into separate tasks
- give each task to a fresh subagent
- check changes against the specification
- send failed reviews back for correction
- review the completed implementation as a whole
Example prompts for the agent
- Execute
docs/plans/feature-plan.mdwith a fresh subagent for each task and track the work in TodoWrite. - Review every completed task for specification compliance first, then for code quality, and repeat the review after fixes.
- Take the independent tasks from this plan, implement them in sequence, and run a final review of the whole implementation.
How to install delegated-development
1Skills CLI (Vercel)
npx skills add qodex-ai/ai-agent-skills --skill delegated-development -a claude-code2Manually: put the files in place
~/.claude/skills/delegated-development/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/delegated-development/
1Skills CLI (Vercel)
npx skills add qodex-ai/ai-agent-skills --skill delegated-development -a codex2Manually: put the files in place
.agents/skills/delegated-development/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add qodex-ai/ai-agent-skills --skill delegated-development -a cursor2Manually: put the files in place
.cursor/skills/delegated-development/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install qodex-ai/ai-agent-skills skills/delegated-development2Manually: put the files in place
.github/skills/delegated-development/SKILL.md1Skills CLI (Vercel)
npx skills add qodex-ai/ai-agent-skills --skill delegated-development -a gemini-cli2Platform CLI
gemini skills install https://github.com/qodex-ai/ai-agent-skills --path skills/delegated-developmentManually: put the files in place
.devin/skills/delegated-development/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add qodex-ai/ai-agent-skills --skill delegated-development -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about delegated-development
How do I install delegated-development in Claude Code?
Run npx skills add qodex-ai/ai-agent-skills --skill delegated-development -a claude-code, then check ~/.claude/skills/delegated-development/SKILL.md.
What does delegated-development do?
It coordinates a plan through a new subagent for each task. Every result passes a specification review and a code-quality review, with fixes and another review when needed.
When should I use delegated-development?
Use this workflow with a prepared plan whose tasks are mostly independent and can stay in one session. Tightly coupled tasks do not match its process.