Your agent team, explained from the top.
You have 43 specialist agents and 33 reusable skills sitting in this workspace, organized into 10 categories. Most projects don't need all of them — they need the right two or three, in the right order. This page is the playbook for how to pick.
The 30-second version
Don't pick agents. Describe the project. Tell Claude Code what you want done — the agency-manager picks the team, the agents do the work, the qa-expert checks it before it ships to you.
Use one agent for a single craft task ("write me a landing page"). Use a team when the deliverable crosses domains (research + strategy + design + copy + numbers).
The mental model
How something thinks
An agent is a way of deciding. A cmo always thinks like a CMO. A regulatory-analyst always thinks about FDA risk. The reasoning style is stable across every project.
creative-director will always pull every visual decision back to brand promise — whether you ask about a logo, a deck, or a packaging label.What something knows
A skill is a swappable knowledge pack — domain reference material, frameworks, taxonomies. You load skills onto agents based on the project. The agent stays the same; the briefcase it carries changes.
data-analyst agent loads the peptide-domain skill for a Genesis project, and the market-research skill for a sizing study.Who works together
A team template is a pre-baked recipe: "for a peptide fundraise model, you need these 9 agents with these skills loaded, running in these phases." The agency-manager reads it and assembles the team.
peptide-sku-architecture template auto-assembles CMO + CRO + 4 researchers + data-analyst + QA-expert, and runs them in a 5-phase sequence.How a project actually flows
Brief
agency-manager asks clarifying questions, picks a template, customizes the team, and lays out the phase plan.Discovery
Strategy
Build
QA + Ship
qa-expert runs a sweep (numbers parity, source citations, internal-leak grep, structural integrity). If anything fails, it goes back. If it passes, the agency-manager packages a handoff doc and ships to you.One agent or a full team?
The task is one craft, one decision
The deliverable lives entirely inside one specialist's head. You don't need synthesis across domains.
- Single skill needed — copy, design, code, sizing
- You already know the angle — you just need it executed well
- Tight scope — under a day of work, one document or asset
- No QA gate required — you'll review it yourself
marketing-director"Fix this bug" →
fullstack-developer"Review my deck for brand polish" →
creative-director"Should this peptide claim survive FTC review?" →
regulatory-analyst
The deliverable crosses domains
No single agent can produce this alone. Output requires research → strategy → build → QA, with handoffs.
- Multi-day scope — anything that takes more than a day
- External audience — investors, partners, regulators, the public
- Numbers + narrative — analysis paired with how to talk about it
- Reputational risk — claim accuracy, brand consistency, legal exposure
"Launch this peptide product" → research + medical + regulatory + copy
"Redesign the brand site" → CMO + creative-director + UX + dev
"Evaluate this acquisition target" → CRO + data-analyst + competitive-intel
The shortcut
If you'd hire just one freelancer to do it → one agent. If you'd hire an agency → spawn the agency-manager and let it pick the team. When in doubt, talk to agency-manager; it'll downsize to a single agent if the project doesn't need the team.
Project recipes
Peptide SKU & fundraise model
Investor-grade SKU portfolio analysis with financial modeling backup.
Lead: agency-manager
Strategy: cmo cro
Research: market-researcher competitive-intel-analyst regulatory-analyst scientific-researcher
Build: data-analyst + spreadsheet-craft + sku-modeling
QA: qa-expert
Marketing site / landing page
Brand site, product landing, lead-gen page.
Lead: marketing-director
Strategy: cmo
Design: creative-director visual-designer ui-ux-designer
Build: fullstack-developer + react-frontend + seo
QA: qa-expert
Brand identity / rebrand
New brand creation, rebrand, visual identity system.
Lead: creative-director
Strategy: cmo cco + brand-strategy
Research: ux-researcher market-researcher
Build: visual-designer + color-systems + design-token-pipeline
Web application build
Greenfield SaaS, web app with database backend.
Lead: product-manager
Architecture: system-architect cto
Design: ui-ux-designer visual-designer
Build: fullstack-developer devops-engineer
QA: qa-expert security-auditor
Ecommerce store
Online store, product catalog, checkout optimization.
Lead: marketing-director
Strategy: cmo + ecommerce-cro + conversion-copy
Design: ui-ux-designer visual-designer
Build: fullstack-developer + ecommerce-cro
Content + SEO campaign
Editorial calendar, blog buildout, organic search program.
Lead: marketing-director
Skills loaded: content-marketing + seo + conversion-copy
Domain: health-copywriter / peptide-copywriter / genetics-copywriter as needed
Strategic decision (M&A, pivot, market entry)
Major capital allocation or directional decision needing C-suite synthesis.
Lead: agency-manager
C-suite: cro cmo cpo cto as relevant
Research: market-researcher competitive-intel-analyst
Build: data-analyst + financial-modeling
Data product / dashboard
Analytics dashboard, reporting system, data pipeline.
Lead: data-analyst
Architecture: system-architect
Design: ui-ux-designer + ux-strategy
Build: fullstack-developer
Security audit
Pre-launch security review, penetration test prep.
Lead: security-auditor
Support: system-architect devops-engineer qa-expert
User research sprint
Generative discovery, usability testing, persona development.
Lead: ux-researcher
Strategy: cpo ui-ux-designer
Production incident / RCA
Live bug, performance regression, security incident.
Lead: root-cause-analyst
Support: fullstack-developer devops-engineer qa-expert
The full roster
The skills library
How to actually use this
Pattern 1 — Just describe the project
You're allowed to be high-level. Claude Code's job is to translate "I want X" into "spawn agents A, B, C, run them in this order." You should not be picking agent names.
YOU: I need a fundraise data room for the Dubai peptide play. Investor-grade. Numbers must hold up. CLAUDE CODE: [picks peptide-sku-architecture template, spawns 9 agents, runs 5 phases, returns finished workbook + handoff doc]
Why this works: the agency-manager exists specifically to absorb that translation step. Talking to it directly skips the cognitive load of agent-shopping.
Pattern 2 — Name the agent if you know it
If you already know which specialist you want, say so. Saves a round trip. This is the right move for one-craft tasks.
YOU: Have the creative-director review this deck and tell me where the brand drifts. CLAUDE CODE: [spawns creative-director with the deck attached, returns the review]
When to use: you've worked with this agent before, you know the question, you don't need an opinion on whether it's the right question.
Pattern 3 — Ask "who should do this?"
If you're not sure who the right agent is, ask. Claude Code will name one or two candidates and explain the difference. No commitment yet.
YOU: Should the genetic-counselor or the clinical-geneticist write the patient-facing copy for the BRCA results page? CLAUDE CODE: [explains the split: genetic-counselor owns the communication discipline, genetics-copywriter writes the actual copy. Recommends a hand-off.]
Why this matters: the medical cluster has 15 specialists and the lines between them are subtle. Asking is faster than reading.
Pattern 4 — The handoff
Every multi-agent project ends with a handoff doc. Don't accept "the team is done" — ask for the package. It's the agency-manager's job.
YOU: Wrap it up — give me a handoff doc. CLAUDE CODE: [agency-manager produces HANDOFF.md with: what was built, what each agent contributed, what passed QA, what's open, what's next.]
Why: you don't sell after handoff (per your standing instruction). The handoff doc is what you carry into the next conversation, the deck, or the partner meeting.
Two rules that change everything
1. Don't shop for agents. Describe the project. Every minute you spend choosing the right agent is a minute the agency-manager would have spent better. That's its whole job.
2. Don't skip QA. When the team says "done," ask the qa-expert to run a sweep. The reason templates have a quality gate is that "looks good" and "passes the sweep" are different sentences.