Edspencer Claude Agents
edspencer-claude-agents is a Claude Code plugin for the Build phase that provides a comprehensive multi-agent development workflow including planning, GitHub integration, implementation, and testing.
by edspencer · github.com/edspencer/claude-agents
Run a bundled multi-role agent workflow covering planning, implementation, GitHub, testing, and product writing from one Claude Code plugin.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install edspencer-claude-agents@edspencer/claude-agentsBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:edspencer/claude-agents") and the paste-ready config with skillselion.get_install_config("plugin:edspencer/claude-agents").
What it does
edspencer-claude-agents is a Claude Code plugin collection pitched as a comprehensive development agent setup. Catalog metadata highlights agents, planning, product, team workflows, implementation, GitHub integration, and testing—signals that it is meant to span how a solo builder moves from intent to merged code, not just answer one-off prompts. Journey-wide use is honest: the same multi-agent pattern can support validate-time prototypes, build-time features, and ship-time test passes, even though Skillselion shelves it under build agent-tooling as the primary sort key. It suits builders who want orchestrated roles inside Claude Code instead of assembling many single-purpose skills. It is less ideal if you need a deep specialist skill for one vendor API or a pure security audit pipeline with no breadth.
Highlights
- Comprehensive development-oriented Claude agents in one plugin bundle
- Workflow coverage: planning, implementation, testing, and writing
- GitHub integration for repo-aware agent tasks
- Product and team-style role keywords for end-to-end delivery
- Single plugin entry with multi-discipline agent surface
Why builders use it
One general chat session forces you to re-explain context when you jump from planning to code, PRs, and tests.
You get a structured agent team workflow inside Claude Code that carries product and engineering tasks across roles.
At a glance
- Type - Plugin in AI Agents.
- Adoption - 0 installs, 0 stars, 0 votes.
FAQ
Who is edspencer-claude-agents for?
It is for Claude Code users who want bundled agents for planning, implementation, GitHub work, testing, and product writing in one workflow.
When should I use edspencer-claude-agents?
Use it whenever you are driving a feature from spec through code and tests, especially when you want role-separated agent steps instead of one flat prompt.
How do I add edspencer-claude-agents to my agent?
Install the plugin from edspencer/claude-agents into Claude Code and follow the repo workflow to invoke planning, implementation, and testing agents as documented.
Comments
Share how you use edspencer-claude-agents, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.