AI开发团队

Requirements

The core framework (15-agent core team + optional specialists) works with just Claude Code — no additional dependencies.

---

1. Install

Claude Code — as a plugin (recommended). Nothing to clone, and no ~/.claude setup: declare it per project and it reaches every session, including cloud sessions and anyone else who clones the repository.

// <your-project>/.claude/settings.json
{
  "extraKnownMarketplaces": {
    "aidevteam": {
      "source": { "source": "github", "repo": "olehsvyrydov/AI-development-team" }
    }
  },
  "enabledPlugins": { "ai-dev-team@aidevteam": true }
}

Trust the directory when prompted; the plugin installs on the next session. Verify with claude plugin details ai-dev-team, which lists the component inventory and its token cost.

Skills arrive namespaced — ai-dev-team:arch, ai-dev-team:rev — and the short aliases (/arch, /rev) keep working. The always-on contract ships as the ai-dev-team skill; a plugin cannot install a global CLAUDE.md, so that skill carries what a session needs to know about how work runs here.

To try it before declaring it: claude --plugin-dir ./claude from a clone of this repository.

Any editor — the installer. Still supported, and the only path for Cursor, Kiro and VS Code.

git clone https://github.com/olehsvyrydov/AI-development-team.git
cd AI-development-team
./install.sh                       # interactive: pick your editor(s)

The universal installer wires up whichever editors you choose and emits the right config for each — no lock-in:

./install.sh --editors=all --preset=solo --yes  # non-interactive (preset: solo|small-team|parallel-team|regulated)
./install.sh --editors=claude --scope=user    # global ~/.claude (Claude Code)
./install.sh --dry-run                        # preview, change nothing
./install.sh --link                           # symlink content (dev mode)
./install.sh --uninstall                      # remove what it installed

Optional advanced Claude backends (Atlassian, memory MCP, hooks): scripts/setup-claude-backends.sh.

What Gets Installed

As a plugin, nothing is copied into your project. The repository is the plugin:

AI-development-team/
├── .claude-plugin/
│   └── marketplace.json         # the catalogue — points at ./claude
└── claude/                      # ← the plugin root
    ├── .claude-plugin/
    │   └── plugin.json          # the manifest. `version` is deliberately omitted,
    │                            #   so the commit SHA is the version and every push
    │                            #   is an update
    ├── skills/                  # loaded as ai-dev-team:<name>, short aliases intact
    ├── commands/
    ├── templates/
    └── workflow/

CLAUDE.md and AGENTS.md at the plugin root are readable mirrors — a plugin cannot load either, so the always-on contract ships as the ai-dev-team skill instead.

Via install.sh, content is copied (or symlinked with --link) into the target scope. Only skills/, commands/, templates/ and workflow/ are deployed; the instructions file is generated at the destination:

~/.claude/
├── CLAUDE.md                    # generated pointer (TDD workflow, approval gates)
├── TEAM_WORKFLOW.md             # Complete team process documentation
│
├── skills/                      # 43 agent skill files (15 core + specialists + language + process skills)
│   ├── management/              # Product Owner, Scrum Master, Business Analyst
│   ├── architecture/            # Solution Architect, GraphQL Developer
│   ├── development/
│   │   ├── backend/             # Java/Spring, Kotlin, PHP/Laravel, Python/FastAPI
│   │   ├── frontend/            # React/Next.js, Angular, Vue, Flutter
│   │   ├── languages/           # Rust, Java, TypeScript, SQL (auto-loading knowledge skills, no persona)
│   │   └── mobile/              # Native iOS/Android
│   ├── quality/
│   │   ├── review/              # Full-stack, Backend, Frontend, PHP reviewers
│   │   ├── testing/             # QA, E2E (Playwright/Detox), BDD/Cucumber, unit testers
│   │   └── verify/              # Completion auditor (gate)
│   ├── operations/              # DevOps, SecOps, MLOps, SRE, Terraform
│   ├── design/                  # UI/UX Designer, UX Research, JavaFX Designer
│   ├── compliance/              # Accountant, Legal (generic + UK regional variants)
│   ├── marketing/               # Product Marketing Strategist
│   ├── specialized/             # Technical Writer, Kai (self-improving meta-agent)
│   │
│   ├── ai-dev-team/             # ─┐ cross-cutting process skills — judgement, not a role.
│   ├── workflow-engine/         #  │ They sit at the top level because they apply across
│   ├── fid-lifecycle/           #  │ every role: the gate contract, the always-on framework
│   ├── verify-landed/           #  │ contract, work-item lifecycle, proving a change landed,
│   ├── review-tier/             #  │ how much review to buy, which model tier to spend,
│   ├── model-selection/         #  │ how to investigate, how to audit a grounded answer,
│   ├── research-method/         #  │ and how to run a PR to a mergeable state.
│   ├── answer-audit/            #  │
│   ├── parallel-delivery/       #  │ claiming, isolating and reporting back a ticket
│   └── pull-request/            # ─┘ worked by a separate session.
│
├── commands/                    # 50 slash commands
│   ├── [role-based]             # /po, /sm, /ba, /arch, /fe, /be, /rev, /qa, /e2e ...
│   ├── [persona aliases]        # /max, /luda, /jorge, /finn, /james, /adam ...
│   └── [utility]                # /agents, /bug, /issue, /memory, /all, /kai ...
│
├── templates/                   # 6 document templates
│   ├── adr-template.md          # Architecture Decision Records
│   ├── user-story-template.md   # User stories with Given/When/Then AC
│   ├── sprint-template.md       # Sprint planning & tracking
│   ├── code-review-template.md  # Structured code review reports
│   ├── investigation-report-template.md
│   └── retrospective-template.md
│
└── workflow/                    # workflow.yaml + schema + optional MCP adapters

---

Quick Start

Jira & Confluence (optional overlay)

By default the team is file-based — Backlog.md tickets + a markdown knowledge base, zero paid accounts. Jira/Confluence are an optional overlay: enable them in workflow.yaml and connect the Atlassian MCP server:

claude mcp add --scope user --transport http atlassian https://mcp.atlassian.com/v1/mcp

• Jira: Kanban board for issue tracking, ticket lifecycle, sprint management
• Confluence: Architecture decisions, security reviews, investigation reports, sprint documentation
• Git conventions: Branch names (feature/PROJ-123-description), commit messages (PROJ-123: Implement feature)

---

Optional Add-Ons

Agent Reference

Technology Extensions

These activate alongside core agents when working with specific technologies:

---

Workflow

Bug Workflow

/bug Login button doesn't work on mobile Safari

Creates a structured investigation → reproduction test → TDD fix → code review → E2E test.

vs. a single "do everything" agent

---