Michael Harris Devteam
- 16 repo stars
- Updated February 26, 2026
- michael-harris/devteam
michael-harris-devteam is a Claude Code plugin that runs a multi-agent devteam workflow to plan and execute sprints with automated quality gates.
About
michael-harris-devteam is a Claude Code plugin entry that packages one plugin describing a multi-agent development workflow: planning and executing sprints in a largely automated way. Catalog metadata positions it as a devteam system with council agents, execution gates, quality controls, and diagnostics—language that maps to how developers wish they had a tiny autonomous squad instead of one chat thread. With only one plugin in the bundle, the value is depth on process rather than breadth of unrelated utilities. It fits developers who already use Claude Code for implementation and want repeatable sprint rituals: scope work, run agents through tasks, and stop when gates fail. Complexity is intermediate; you need tolerance for multi-step agent flows and trust in automated execution. Tag it multi-phase because planning bleeds into Validate and review gates into Ship, while the primary discovery path remains Build → pm for sprint-oriented agent tooling.
- Single-plugin bundle focused on a full devteam multi-agent development system
- Automated sprint planning and execution inside Claude Code
- Council-style agents with execution gates and quality checks
- Keywords emphasize autonomous teams, diagnostics, and structured delivery
- Suited to replacing manual ‘you are the PM and dev’ ping-pong with a workflow skill
Michael Harris Devteam by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin install michael-harris-devteam@michael-harris/devteamAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| repo stars | ★ 16 |
|---|---|
| Last updated | February 26, 2026 |
| Repository | michael-harris/devteam ↗ |
What it does
Install when you want an automated multi-agent “dev team” inside Claude Code to plan sprints, execute work, and pass quality gates without manually coordinating every step.
Who is it for?
Best when you want sprint-like automation and a council of agents without standing up a separate project-management stack.
Skip if: Skip if you only need occasional one-off code edits or and do not want autonomous multi-step agent execution.
What you get
After installation, Claude Code can follow a structured devteam system that plans sprints, executes work through agents, and enforces gates before you call a slice done.
- One devteam-oriented plugin for structured sprint cycles
- Multi-agent planning and execution flow with quality gates
- Diagnostics-oriented checkpoints during automated development
By the numbers
- [object Object]
- [object Object]
Recommended Plugins
0pg Cc MarketplacePersonal Claude Code plugins collection
1shot Labs Squadron Comms PluginVoice communication system with ElevenLabs TTS for multi-agent coordination in Claude Code3
23blocks Os Ai MaestroAI Agent Orchestrator with Skills System - Give AI Agents superpowers: memory search, code graph queries, agent-to-agent messaging.733
3commas Io Commas ClaudeThis is a repo with shared agents and skills used company-wide4
884js Agent Plugins1 plugin
A5c Ai BabysitterBabysitter enforces obedience to agentic workforces and enables them to manage extremely complex tasks and workflows through deterministic, hallucination-free self-orchestration1.6kHow it compares
Sprint-oriented multi-agent workflow plugin, not a 27-plugin DevOps catalog or a markdown checkbox task tracker.
FAQ
Who is Michael Harris Devteam for?
It is for Claude Code users who treat development as sprints and want a bundled multi-agent devteam with gates and quality checks rather than improvising each session.
When should I use Michael Harris Devteam?
Use it when you are ready to hand a defined body of work to an automated planning-and-execution loop and review output at quality gates.
How do I add Michael Harris Devteam to my agent?
Add the michael-harris/devteam plugin from the Claude Code plugin source, enable the devteam plugin, then invoke it per the repository’s commands for sprint planning and execution.