Claude Code Dev Team

English · 繁體中文

An entire engineering team for Claude Code — 12 specialized agents, 15 automation hooks, and the P7/P9/P10 methodology that keeps them disciplined.

Most people use Claude Code as a single coder. This config turns it into a full engineering org: planner, fullstack-engineer, refactor-specialist, migration-engineer, frontend-designer, critic, vuln-verifier, debugger, db-expert, onboarder, tool-expert, web-researcher — each agent owns a role, each has its own tool permissions, and a strict delegation rulebook decides who touches what.

Backed by corporate-culture-inspired discipline (closure, fact-driven, exhaustiveness) and battle-tested hooks that catch debugger statements, hardcoded secrets, cost overruns, and MCP outages before they hit main.

---

The Team

Role	Agent	What they do	When they ship
📋 Tech Lead	planner	Breaks down fuzzy requirements into parallelizable Task Prompts with a six-element contract (goal / scope / input / output / acceptance / boundaries). Never writes code.	Task touches 3+ files or 2+ modules
🛠 Senior Engineer	fullstack-engineer	Ships features using the P7 methodology: read reality → design solution → impact analysis → implement → three-question self-review → [P7-COMPLETION] delivery.	Single-feature or cross-module implementation
🔄 Refactor Lead	refactor-specialist	Large-scale safe refactors. Atomic commits, full callsite verification, single-revert rollback.	Renames, file moves, module extraction across 10+ files
🚀 Migration Lead	migration-engineer	Framework / library major-version upgrades. Reads upstream changelog, executes incrementally, verifies at every step.	Next.js 13→14, Vue 2→3, Tailwind 3→4, etc.
🎨 Designer	frontend-designer	Builds landing pages, dashboards, and UI that doesn't look like AI slop. Opinionated aesthetic direction, refuses generic output.	New pages, UI redesigns, visual upgrades
🔍 Code Reviewer	critic	Finds bugs, security holes, logic errors, edge cases, performance issues. Every finding with file path + line number. No "looks good to me".	Pre-commit, pre-deploy, pre-merge
🧪 Pentester	vuln-verifier	Takes the critic's findings and writes actual PoC tests to prove the vulnerability is real — no false positives, no hand-waving.	After critic flags a security issue
🐛 Debug Engineer	debugger	Reads logs, constructs hypotheses, verifies, fixes. Never guesses, always traces root cause. Includes log-analyzer.	Bug reports, service incidents, test failures
🗄 DB Specialist	db-expert	Reviews schemas, migrations, queries for safety, indexes, locks, race conditions. Paranoid about data loss.	Schema changes, migrations, query optimization
🗺 Onboarder	onboarder	First-time codebase exploration. Produces a structured mental model — architecture, entry points, suspicious areas.	Joining a new project, evaluating an open-source repo
⚙️ Tool Expert	tool-expert	Picks the right MCP tools, chains complex workflows, troubleshoots tool failures. Knows every integration in your stack.	MCP tool failures, complex tool chaining
📚 Researcher	web-researcher	Fetches and synthesizes official docs, API specs, error code meanings. The antidote to hallucination.	Uncertain API usage, error code lookups

Each agent is a markdown file under agents/ with its own system prompt, tool permissions, and model selection. Customize them. Fork them. Replace the ones you don't need.

---

The Workflow

           ┌─────────────┐
           │  Your Task  │
           └──────┬──────┘
                  │
         ┌────────▼────────┐
         │   📋 planner    │  ← Breaks into parallel subtasks
         │    (Tech Lead)   │    if touches 3+ files
         └────────┬────────┘
                  │
        ┌─────────┼─────────┐
        ▼         ▼         ▼
  ┌─────────┐ ┌─────────┐ ┌─────────┐
  │ fullstk │ │ fullstk │ │ fullstk │  ← Parallel execution
  │   × N   │ │   × N   │ │   × N   │    P7 methodology
  └────┬────┘ └────┬────┘ └────┬────┘
       └───────────┼───────────┘
                   ▼
           ┌──────────────┐
           │  🔍 critic   │  ← Mandatory pre-deploy review
           │   (reviewer)  │
           └───────┬──────┘
                   │
          ┌────────┴────────┐
          │                 │
          ▼                 ▼
   ┌──────────────┐  ┌─────────────┐
   │ 🐛 debugger  │  │   Deploy    │
   │ (if issues)  │  │             │
   └──────────────┘  └─────────────┘

Security-sensitive work takes a detour: critic flags → vuln-verifier writes PoC → fix or file PR.

---

The Methodology

Three Red Lines

Every agent enforces these. No exceptions. No "close enough".

• 🔒 Closure Discipline — Every task has a clear Definition of Done. "This is probably enough" is not an ending.
• 📎 Fact-Driven — Every judgment must cite actual code with paths and line numbers. "I guess" / "probably" / "should be" are violations.
• ✅ Exhaustiveness — Checklists cannot be skipped. Clean items must be explicitly marked "checked, no problems" — never silently ignored.

P7/P9/P10 Mode Switching

Not role-play. Operating modes that Claude switches between based on task scope:

Scope	Mode	Behavior
Single feature	P7 (Senior Engineer)	Design → Impact analysis → Implement → Three-question self-review → [P7-COMPLETION]
Multi-module, 3+ files	P9 (Tech Lead)	Decompose into Task Prompts with six elements. Coding is forbidden — your output is prompts, not code.
Cross-team, 5+ sprints	P10 (CTO)	Output strategy docs. Goals, success metrics, risks, ti