feat: create team-templates skill with reusable team configurations

[JacobPEvans-personal]

Parent

Part of #14 (epic: migrate workaround orchestration patterns to native Claude Agent Teams)

Summary

Create a team-templates skill that defines reusable team configurations for common workflows - code review, debugging, feature development, and multi-repo operations.

Problem

Every time a user wants an Agent Team, they must describe the team structure from scratch. Common patterns like "3-reviewer PR review" or "hypothesis-testing debug session" should be templates that can be invoked with minimal configuration.

Proposed Solution

Skill Structure

agent-teams-orchestrator/skills/
├── team-lifecycle.md
├── teammate-communication.md
└── team-templates.md          # NEW

Template Catalog

1. review-team - Multi-perspective code review

Roles: security-reviewer, performance-reviewer, test-reviewer, quality-reviewer
Models: 3x sonnet + 1x haiku
Mode: Delegate, no plan approval
Tasks: Review PR from assigned perspective, debate findings, synthesize

2. debug-team - Competing hypothesis debugging

Roles: 3-5 investigators (dynamic based on hypotheses)
Models: All sonnet
Mode: Delegate
Tasks: Each investigator tests one hypothesis, debate to disprove

3. feature-team - Parallel feature development

Roles: architect (plan approval), implementers (2-3), tester
Models: 1x opus (architect), 2-3x sonnet, 1x haiku (tester)
Mode: Delegate with plan approval
Tasks: Architect plans, implementers build in parallel, tester validates

4. repo-ops-team - Multi-repository operations

Roles: N repo-specialists (1 per repo group), 1 reporter
Models: All sonnet
Mode: Delegate
Tasks: Each specialist handles their repos, reporter aggregates

5. refactor-team - Large-scale refactoring

Roles: architect (plan approval), refactorers (2-4), reviewer
Models: 1x opus, 2-4x sonnet, 1x sonnet
Mode: Delegate with plan approval
Tasks: Architect designs, refactorers own file sets, reviewer cross-checks

Template Format

Each template defines:

• Roles: Named teammate roles with responsibilities
• Models: Recommended model per role
• Mode: Delegate mode and plan approval settings
• Task patterns: How work should be divided
• Communication patterns: When to use write vs broadcast
• File ownership: How to avoid conflicts
• Sizing guidance: When to add/remove teammates

Usage

Templates are referenced by commands and skills:

Use the `review-team` template from the team-templates skill.
Spawn with PR #142 as context.

Acceptance Criteria

• 5 team templates defined with complete specifications
• Each template includes model routing, task patterns, and communication guidance
• Templates are actionable (not just documentation)
• File ownership patterns prevent conflicts
• Token cost estimates per template
• Passes markdownlint and token limit validation

Dependencies

• Depends on: agent-teams-orchestrator plugin (feat: create agent-teams-orchestrator plugin with team lifecycle management #15)
• Informs: all other child issues in the epic

[JacobPEvans-personal]

Parent epic: #14 | Depends on: #15

[claude]

This issue has had no activity for 30+ days. Is this still relevant?

[JacobPEvans-personal]

This is all built-in to Claude now