Team Templates Catalog

This skill provides a library of pre-built team configuration blueprints for common work scenarios. Each template defines the team composition, member roles, model assignments, prompt templates, and workflow phases needed to accomplish specific types of work.

Templates are blueprints, not final team configurations. They contain patterns and templates that team-builder uses to generate actual team configs in ~/.claude/teams/.

Quick Reference

Template Locations

All templates live under team-templates/templates/ organized by category:

templates/
  software-dev/   fullstack.json, backend-api.json, frontend-app.json, mobile-app.json
  content/        article-writing.json, documentation.json, marketing-campaign.json
  research/       market-research.json, code-analysis.json, data-science.json
  devops/         cicd-pipeline.json, monitoring-setup.json, incident-response.json
  quality/        code-review.json, testing.json, security-audit.json
  project-mgmt/   sprint-planning.json, project-reporting.json

Usage with team-builder

Templates are designed to be consumed by the team-builder skill. To create a team from a template:

1. •

   List available templates: Reference this catalog to find the right template for your scenario.

2. •

   Apply a template: Tell team-builder which template to use and provide the project name:

   code

   Use the fullstack template to create a team for my "ecommerce-app" project
   

3. •

   Customize before applying: You can request modifications:

   code

   Use the backend-api template for "payment-service" but replace the security-auditor
   with a payment-integration specialist
   

4. •

   Combine templates: For larger projects, apply multiple templates:

   code

   Create teams from both fullstack and cicd-pipeline templates for "saas-platform"
   

Blueprint Format

Each template JSON file follows this structure:

• •template: Metadata (name, category, description, version)
• •team: Name pattern and description template with {project} placeholders
• •members: Array of role definitions with agent type, model tier, color, prompt template, and responsibilities
• •workflow: Phases and task templates with dependencies

The {project} placeholder in name_pattern and prompt templates gets replaced with the actual project name when the team is created.

Model Strategy

Templates use a tiered model strategy to balance capability and cost:

• •opus: Team leads and roles requiring complex reasoning, architectural decisions, or cross-cutting coordination
• •sonnet: Implementation-focused roles that need strong coding or writing ability
• •haiku: Repetitive tasks, simple checks, or high-volume work where speed matters more than depth

Color Convention

Member colors follow a fixed assignment order for visual consistency:

1. •green - Team lead (always first)
2. •yellow - Second member
3. •purple - Third member
4. •orange - Fourth member
5. •pink - Fifth member
6. •Colors cycle for teams with more than five members

Categories

Software Development (4 templates)

For teams building software. Covers the full spectrum from full-stack web apps to mobile development. Each template includes testing and review roles to enforce quality from the start.

Content (3 templates)

For teams producing written content. Whether it is technical documentation, marketing copy, or SEO articles, these templates pair writers with editors, researchers, and specialists.

Research (3 templates)

For teams performing analysis work. Includes market research, codebase analysis, and data science templates that combine domain expertise with analytical tools.

DevOps (3 templates)

For infrastructure and operations work. Covers CI/CD pipelines, monitoring setup, and incident response with appropriate tooling expertise.

Quality (3 templates)

For teams focused on software quality. Dedicated code review, testing, and security audit templates that provide multi-angle quality assurance.

Project Management (2 templates)

For planning and reporting work. Sprint planning and project reporting templates that combine analytical and communication skills.

Customization

See references/customization-guide.md for detailed instructions on:

• •Adding or removing team members
• •Swapping agent types for different specializations
• •Adjusting model tiers for cost optimization
• •Modifying prompt templates for project-specific needs
• •Creating entirely new templates from scratch

Extended Template Details

See references/template-catalog.md for in-depth descriptions of each template including:

• •Detailed use cases and when to choose each template
• •Team composition rationale explaining why each role was included
• •Expected workflow walkthroughs
• •Common customization patterns for each template

Related Skills

• •team-builder -- Takes these templates and creates actual running teams
• •team-architect -- Design custom teams when no template fits your needs
• •team-lifecycle -- Understand the full lifecycle from template selection to shutdown