devteam
michael-harris · michael-harris/devteam
DevTeam là một plugin Claude Code với 127 tác tử AI chuyên biệt tự động hóa quy trình làm việc phát triển, bao gồm lập kế hoạch, thực thi và kiểm soát chất lượng.
Một workflow phát triển Claude Code đa tác nhân để lập kế hoạch và thực hiện các sprint một cách hoàn toàn tự động.
Xem trước
Bạn có thể làm gì với nó
- Tự động hóa toàn bộ quá trình phát triển phần mềm từ yêu cầu đến triển khai.
- Sử dụng "Hội đồng Sửa lỗi" gồm 5 tác tử để chẩn đoán và giải quyết các vấn đề phức tạp.
- Thực thi chất lượng mã, bảo mật và độ bao phủ thông qua các cổng kiểm soát chất lượng tự động.
Kiểm tra an toàn
Không thấy dấu hiệu rủi ro trong các file đã quét.
Quét tự động các file trong repo. Luôn xem lại code trước khi chạy.
Trích từ README
DevTeam: Multi-Agent Autonomous Development System
A Claude Code plugin providing 127 specialized AI agents with:
- Interview-driven planning - Clarify requirements before work begins
- Codebase research - Investigate patterns and blockers before implementation
- SQLite state management - Reliable session tracking and cost analytics
- Model escalation - Automatic haiku → sonnet → opus progression
- Bug Council - 5-agent diagnostic team for complex issues
- Eco mode - Cost-optimized execution mode for simpler tasks
- Quality gates - Tests, types, lint, security, coverage enforcement
How This Works
This is a Claude Code plugin composed of:
- Markdown agent instructions (
agents/*.md) — Claude Code reads these and follows them as subagent prompts via the Task tool - YAML configuration (
.devteam/*.yaml) — defines capabilities, thresholds, and agent selection triggers - Shell scripts (
scripts/*.sh,hooks/*.sh) — handle state persistence (SQLite), event logging, hook lifecycle, and database management - Slash commands (
commands/*.md,skills/*/SKILL.md) — user-facing commands that orchestrate agent workflows
There is no separate executable orchestrator. Claude Code itself is the runtime — it reads the agent markdown files, selects appropriate agents based on task characteristics, and executes them as subagents. The shell scripts provide supporting infrastructure (database, hooks, state tracking) but the orchestration logic lives in the agent instructions themselves.
Key Features
Autonomous Development with Task Loop
Task Loop is the iterative quality enforcement system that ensures every task is completed to specification:
┌─────────────────────────────────────────────────────────────┐
│ TASK LOOP │
│ │
│ Execute → Quality Gates → Pass? → Complete │
│ ↑ │ │
│ │ Fail │
│ │ ↓ │
│ └─── Fix Tasks ← Model Escalation (if needed) │
│ │
│ Loop until: ALL QUALITY GATES PASS │
└─────────────────────────────────────────────────────────────┘
Features:
- Automatic model escalation (haiku → sonnet → opus) after failures
- Stuck loop detection with Bug Council activation
- Quality gates: tests, types, lint, security, coverage
- Anti-abandonment system prevents agents from giving up
- Maximum 10 iterations with human notification
Intelligent Agent Selection
The /devteam:implement command automatically selects the best agents for your task:
/devteam:implement "Add user authentication with JWT tokens"
The /devteam:implement command analyzes your task description, file types involved, and project context to select appropriate agents. It considers keyword matches, file extensions, task type (feature vs. bug), and detected language/framework.
Bug Council: Multi-Perspective Debugging
For complex bugs, the Bug Council convenes 5 specialized analysts:
┌─────────────────────────────────────────────────────────────┐
│ BUG COUNCIL │
├─────────────────────────────────────────────────────────────┤
│ Root Cause Analyst │ Error analysis, stack traces │
│ Code Archaeologist │ Git history, regression detection │
│ Pattern Matcher │ Similar bugs, anti-patterns │
│ Systems Thinker │ Dependencies, integration issues │
│ Adversarial Tester │ Edge cases, security vectors │
└─────────────────────────────────────────────────────────────┘
↓
Synthesized Solution
Activation Triggers:
- Critical/high severity bugs
- 3+ failed opus attempts
- Complexity score ≥ 10
- Explicit
bug_council: trueflag
Scope Enforcement
Agents are strictly confined to their assigned scope:
scope:
allowed_files:
- "src/auth/*.py"
forbidden_directories:
- "src/billing/"
max_files_changed: 5
6 Enforcement Layers:
- Task scope definition in YAML
- Agent prompt constraints
- Scope validator agent with VETO power
- Pre-commit hook blocking
- Runtime file access control
- Out-of-scope observations logging
Anti-Abandonment System
Agents cannot give up. The persistence system ensures completion:
Abandonment Attempt → Detected → Re-engagement Prompt
↓
Still stuck?
↓
Model Escalation (haiku → sonnet → opus)
↓
Still stuck?
↓
Bug Council Activation
↓
Still stuck?
↓
Human Notification (but keep trying)
127 Specialized Agents
Enterprise Roles
| Category | Agents | Capabilities |
|---|---|---|
| SRE | Site Reliability Engineer | SLOs, incident response, chaos engineering |
| SRE | Platform Engineer | Internal developer platforms, golden paths |
| SRE | Observability Engineer | Metrics, logging, tracing, alerting |
| Security | Penetration Tester | OWASP testing, API security, vuln assessment |
| Security | Compliance Engineer | SOC2, HIPAA, GDPR, PCI-DSS |
| Product | Product Manager | PRDs, roadmaps, user research |
| Quality | Accessibility Specialist | WCAG 2.1, screen readers, inclusive design |
| DevRel | Developer Advocate | Technical content, community, DX |
Orchestration Agents
| Agent | Purpose |
|---|---|
| Autonomous Controller | Execution loop management, state transitions, circuit breaker |
| Bug Council Orchestrator | Multi-perspective bug analysis |
| Code Review Coordinator | Cross-agent code review orchestration |
| **Quality Gate Enforc |