subagent-driven-development
NewUse when executing implementation plans with independent tasks in the current session
Summary
This skill enables Claude Code to break down complex implementation plans into independent sub-tasks and execute them in parallel within the current session.
- It is useful for developers who need to efficiently manage and complete multi-step coding projects without manual task switching.
Install & Usage
~/.claude.jsonAdd the configuration to "mcpServers": { "subagent-driven-development": { "command": "...", "args": [] } }
/mcpUse Cases
Usage Examples
/subagent-driven-development Implement the user authentication module and the payment gateway integration as separate sub-tasks.
Use subagent-driven development to refactor the database layer and the API layer independently.
Run subagent-driven development to generate unit tests for the auth, billing, and notification services in parallel.
Security Audits
Frequently Asked Questions
What is subagent-driven-development?
This skill enables Claude Code to break down complex implementation plans into independent sub-tasks and execute them in parallel within the current session. It is useful for developers who need to efficiently manage and complete multi-step coding projects without manual task switching.
How to install subagent-driven-development?
To install subagent-driven-development: open your mcp config (~/.claude.json), then add the config to "mcpServers": { "subagent-driven-development": { "command": "...", "args": [] } }. Finally, /mcp in Claude Code.
What is subagent-driven-development best for?
subagent-driven-development is a mcp categorized under General. It is designed for: agent, productivity. Created by obra.
What can I use subagent-driven-development for?
subagent-driven-development is useful for: Breaking a large feature implementation into independent sub-tasks and executing them concurrently.; Refactoring multiple modules simultaneously by assigning each refactor to a separate sub-agent.; Running unit tests for different components in parallel to speed up the testing phase.; Generating documentation for multiple APIs at the same time while the main agent handles other work.; Performing code reviews on separate files concurrently to reduce review turnaround time.; Implementing a set of independent bug fixes across different parts of the codebase in one session..