Multi-agent development workflow using Agent Teams. Supports five modes: plan (architect teammate + PM teammate debate → plan.md), dev (developer teammate + code-tester teammate + qa-tester teammate + reviewer teammate iterate → code), full (plan → approval gate → dev), auto (plan → dev, no gate), and bugfix (tester + developer + reviewer TDD triad → fix + PR). Use when tasks benefit from collaborative agent teammates with peer messaging.
From cdtnpx claudepluginhub rube-de/cc-skills --plugin cdtThis skill is limited to using the following tools:
references/bugfix-workflow.mdreferences/dev-workflow.mdreferences/plan-workflow.mdreferences/researcher-prompt.mdSearches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Multi-agent development workflow with five modes. Pick one based on the user's needs:
| Mode | When to use |
|---|---|
| plan | Need architecture/design before coding |
| dev | Have an approved plan, ready to implement |
| full | End-to-end with user approval gate between plan and dev |
| auto | End-to-end without approval gate |
| bugfix | Well-specified, reproducible bug (root cause may be unknown) — TDD fix cycle |
Before executing any mode, read the relevant workflow file:
Plan Phase (plan/full/auto) Dev Phase (dev/full/auto) Bugfix Phase (bugfix)
Lead (You) Lead (You) Lead (You)
├── architect [teammate] ├── developer [teammate] ├── tester [teammate]
├── product-manager [teammate] ├── code-tester [teammate] ├── developer [teammate]
└── researcher [subagent] ├── qa-tester [teammate] ├── reviewer [teammate]
├── reviewer [teammate] └── researcher [subagent]
└── researcher [subagent]
│ │
└──── plan.md (handoff) ─────────┘
Teammates message each other directly (Architect teammate↔PM teammate, Developer teammate↔Code-tester teammate, Developer teammate↔QA-tester teammate, Developer teammate↔Reviewer teammate). In bugfix mode: Tester teammate↔Developer teammate, Reviewer teammate↔Developer teammate. Researcher is a subagent — Lead relays results.
Research specialist for doc lookups. Queries Context7 for library docs, searches web for best practices, returns structured findings with code examples. Bundled as agents/researcher.md in this plugin — Context7 MCP is auto-configured via .mcp.json.
Writes the failing regression test BEFORE the developer touches the code (TDD red phase). Verifies the fix passes and re-verifies after refactoring. Iterates directly with developer on failures (max 3 cycles for fix, max 2 for refactor).
Discovers codebase structure using the Explore agent (preferred) or repomix-explorer (if available) for broad understanding, then targets specific files with Glob/Grep/Read for detailed inspection. Reads existing Architecture Decision Records (ADRs) from docs/adrs/ before designing. Designs architecture: components, interfaces, file changes, data flow, testing strategy. Writes new ADRs to docs/adrs/adr-NNNN-<slug>.md for each significant decision. References existing ADRs when relevant and supersedes old ones when decisions change. Debates tradeoffs with PM teammate. Messages design to lead and PM teammate. Writes the plan file as their final deliverable.
Validates architecture against requirements. Challenges design with concerns. Produces verdict: APPROVED or NEEDS_REVISION with specifics.
Implements tasks from plan (dev) or minimal fix from bug spec (bugfix). No stubs, no TODOs. Matches existing patterns. In dev mode: iterates with code-tester teammate on failures, qa-tester teammate on QA issues, reviewer teammate on code quality. In bugfix mode: iterates with tester teammate on failures and reviewer teammate on code quality. Updates project documentation (README.md, AGENTS.md, CLAUDE.md) to reflect implementation changes.
Unit/integration tests. Messages developer teammate with failures + root cause. Max 3 cycles.
Always spawned. Adapts testing approach based on task type: for UI tasks, writes Storybook stories and tests user flows via npx agent-browser; for non-UI tasks, runs integration/smoke tests, verifies regression safety, and tests API contracts. Messages developer teammate with issues + evidence. Max 3 cycles.
Reviews changed files for completeness, correctness, security, quality, and plan adherence (dev) or bug spec adherence (bugfix). Validates review with /council (quick quality for routine, review security or review architecture for critical concerns). Scans for stubs. Messages developer teammate with file:line + fix suggestions. Max 3 cycles. Messages lead with verdict, review cycles, issues found/fixed, and known limitations after approval.
type (impl|test|docs) and depends_on; parallel within waves, sequential betweenYou are a coordinator, not an implementer. During active team phases:
*.ts, *.js, *.py, *.go, *.rs, *.tsx, *.jsx, *.vue, *.svelte, *.css, *.scss, *.html)*.test.*, *.spec.*, __tests__/*) — delegate to code-tester teammate (or tester teammate in bugfix mode)*.md) — delegate to the teammate with context (architect for plans/ADRs, reviewer for reports, developer for project docs)