I love Claude Code's subagents. But I kept noticing the same chore: every new project, I'd hand-write the same crew again — a builder, a reviewer, someone to keep the stack conventions straight. Good setups, but they lived in one repo and never got reused.

So I built ccteams — a package manager for agent teams. One command drops a ready-made team of Claude Code subagents into your project.

npm install -g ccteams
ccteams use go-api // apply your favourite team

That applies a Go builder + reviewer, tuned for net/http, to the current project. Switch when the work changes:

ccteams use next-ts     # Next.js App Router + TypeScript + Tailwind
ccteams use generalist  # scope -> design -> build -> QA -> ship, any stack

Are you not sure which team you need? Don't worry, you can use /ccteams:choose-team and AI will choose the best team for you!

/plugin marketplace add toffyui/ccteams
/plugin install ccteams@ccteams
/ccteams:choose-team I want to create a todo app.

What's a "team"?

A team is just a curated bundle of Claude Code subagents — each a markdown file with the usual name / description / tools frontmatter and a system prompt — plus an orchestration.md that gets merged into your project's CLAUDE.md. Nothing magic, nothing proprietary. It's the setup you'd build by hand, except already built and ready to reuse.

ccteams ships with 8 teams:

• generalist — stack-agnostic, takes a feature scope → design → build → QA → ship
• next-ts — Next.js App Router + TypeScript + Tailwind
• frontend — framework-agnostic UI/UX and accessibility
• go-api — idiomatic Go HTTP APIs
• python-fastapi — FastAPI + Pydantic v2
• rails — Ruby on Rails
• debug — reproduce → root-cause → fix → regression test
• research — compares options and recommends; writes no code

What use actually does

No black box. ccteams use <team>:

1. Copies the team's agents into .claude/agents/
2. Writes .claude/active-team.md and adds an @.claude/active-team.md import to your CLAUDE.md
3. Tracks everything in .claude/.ccteams-manifest.json so switching teams is clean
4. Won't overwrite agents you wrote by hand — there's a collision guard

Switching to another team removes only what ccteams placed last time. Your own files are never touched.

The one catch: restart

Being honest, because this trips people up: Claude Code loads subagents at session start. So after ccteams use, you have to restart Claude Code for the team to take effect. It is not instant. Run the command, then /exit and relaunch.

Optional: do it from inside Claude Code

There's an optional plugin that adds slash commands, so you don't have to leave Claude Code:

/plugin marketplace add toffyui/ccteams
/plugin install ccteams@ccteams

Then /ccteams:list-teams, /ccteams:use-team <team>, and the fun one — /ccteams:choose-team — where you describe what you need in plain text and it picks the team for you.

Power users: parallel teammates

If you want the team members to run in parallel and message each other instead of one-at-a-time delegation, opt in:

ccteams use generalist --agent-teams

That turns on Claude Code's experimental agent-teams mode for the project. It's experimental, so treat it as a power-user option, not the default.

Try it

npm install -g ccteams
ccteams list

It's open source (MIT): github.com/toffyui/ccteams. If it's useful, a star helps a lot.

One real question for you: which stack should I add a team for next? I'm weighing Spring Boot, Django, and SwiftUI — tell me in the comments what you'd actually use.