feat: create agent-teams-orchestrator plugin with team lifecycle management

[JacobPEvans]

Parent

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

Summary

Create a new agent-teams-orchestrator plugin that provides reusable commands and skills for managing Agent Team lifecycles. This is the foundational plugin that other team-based plugins will depend on.

Problem

Currently, the repo's orchestration philosophy (CLAUDE.md) describes manual delegation patterns:

• "Think of yourself as a conductor, not a musician"
• Manual subagent dispatch via Task tool
• No shared state or inter-agent messaging
• Each subagent reports back independently

Agent Teams replaces this with native peer-to-peer coordination, but there's no plugin to help users manage teams consistently.

Proposed Solution

Plugin Structure

agent-teams-orchestrator/
├── .claude-plugin/plugin.json
├── commands/
│   └── spawn-team.md          # /spawn-team command
├── skills/
│   ├── team-lifecycle.md       # Team creation/cleanup patterns
│   └── teammate-communication.md  # Messaging best practices
├── hooks/
│   └── hooks.json              # Team cleanup guard
└── README.md

Components

Command: /spawn-team

• Accepts natural language description of work
• Classifies task into team roles (researcher, implementer, reviewer, etc.)
• Spawns team with appropriate models per role
• Sets up shared task list with dependencies
• Enables delegate mode when appropriate

Skill: team-lifecycle

• Canonical patterns for creating, monitoring, and cleaning up teams
• Model selection guidelines (Opus for lead, Sonnet for workers, Haiku for simple tasks)
• Task sizing recommendations (5-6 tasks per teammate)
• Graceful shutdown sequence

Skill: teammate-communication

• When to use write vs broadcast
• Message formatting conventions
• Plan approval workflows
• Task claiming patterns

Hook: Team cleanup guard

• PostToolUse hook on Bash
• Detects orphaned tmux sessions from teams
• Warns when team resources exist without active lead

Graceful Degradation

When CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS is not enabled:

• /spawn-team falls back to parallel subagent dispatch via Task tool
• Skills still apply (communication patterns useful for subagents too)
• Hook silently passes (no teams to guard)

Acceptance Criteria

• Plugin validates with cclint
• /spawn-team creates a functional agent team
• Skills document all TeammateTool operations
• Graceful fallback when agent teams disabled
• README with usage examples
• Token cost guidance documented

Model Routing

Component	Model	Reasoning
/spawn-team command	sonnet	Orchestration logic
Team lead	opus	Complex coordination
Default teammates	sonnet	Balance of capability/cost
Simple tasks	haiku	Cost efficiency

[JacobPEvans]

Parent epic: #14