subagent-driven-development
From the author
Executes an approved implementation plan through fresh implementer and reviewer agents for each task, with explicit handoffs, focused tests, and task-by-task integration. Use for multi-task work where independent agent context improves implementation and review quality. Not for a single small edit, an unresolved design, or a failure that still needs root-cause analysis.
Install
npx skills add thiientv/godmode --skill subagent-driven-development -a claude-code
Installs to .claude/skills/subagent-driven-development/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 81
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- executing-plansGanyuanRan/AegisUse when executing a written implementation plan across sessions or with review checkpoints. Small or single-slice plans stay inline. For same-session independent tasks, use subagent-driven-development instead.Planning★ 1.4K
- dothedotmack/claude-memExecute a phased implementation plan using subagents. Use when asked to execute, run, or carry out a plan — especially one created by make-plan.Planning★ 102.7K
- subagent-driven-analysisK-Dense-AI/science-superpowersUse when executing a pre-registered analysis plan with mostly independent steps in the current sessionPlanning★ 361
- test-driven-developmentjnMetaCode/superpowers-zh在实现任何功能或修复 bug 时使用，在编写实现代码之前Testing★ 8.4K
- autonomous-builderforyourhealth111-pixel/Vibe-SkillsFull-stack software development agent for design, implementation, testing, and deployment. Use when the user explicitly asks for end-to-end project creation, feature development, bug fixing, or code refactoring.Testing★ 3.8K
- implementation-planningcbrock84/headcountTurns a spec or requirement into a written plan a separate session or agent can execute, then drives that plan through review checkpoints. Use this before touching code on any multi-step task, when work needs handing to someone else, when a task keeps sprawling mid-implementation, or when a plan exists and needs executing in order with verification between steps.Planning★ 2.1K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in