feat: create team-based multi-repo sync and CI fix plugin

[JacobPEvans-personal]

Parent

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

Summary

Create a team-repo-ops plugin that uses Agent Teams to coordinate work across multiple repositories simultaneously - syncing branches, fixing CI failures, and managing PRs in parallel.

Problem

Current multi-repo commands in the ecosystem (from parent CLAUDE.md):

• /ready-player-one - Orchestrates PR finalization across repos serially
• /fix-pr-ci all - Fixes CI across all PRs but dispatches sequentially
• /sync-main all - Syncs main across all open PRs sequentially
• /auto-claude - Autonomous maintenance that runs serially

These commands process repos one at a time. With 10+ repos, this is slow and can't react to cross-repo dependencies.

Proposed Solution

Plugin Structure

team-repo-ops/
├── .claude-plugin/plugin.json
├── commands/
│   ├── team-sync.md            # /team-sync command
│   └── team-fix-ci.md          # /team-fix-ci command
├── skills/
│   └── repo-coordination.md    # Cross-repo coordination patterns
└── README.md

Team Architecture (team-sync)

/team-sync (team lead - delegate mode)
├── terraform-specialist (teammate)
│   ├── Owns: terraform-proxmox, terraform-aws worktrees
│   ├── cwd: ~/git/terraform-proxmox/main
│   └── Tasks: sync main, rebase open PRs, report conflicts
├── ansible-specialist (teammate)
│   ├── Owns: ansible-proxmox, ansible-splunk worktrees
│   ├── cwd: ~/git/ansible-proxmox/main
│   └── Tasks: sync main, rebase open PRs, report conflicts
├── app-specialist (teammate)
│   ├── Owns: nix-config, claude-code-plugins
│   ├── cwd: ~/git/nix-config/main
│   └── Tasks: sync main, rebase open PRs, report conflicts
└── reporter (teammate)
    ├── Collects: results from all specialists
    └── Produces: unified status report

Team Architecture (team-fix-ci)

/team-fix-ci (team lead - plan approval required)
├── ci-fixer-1 (teammate, plan approval required)
│   ├── Owns: first batch of failing PRs
│   ├── Must get plan approved before making changes
│   └── Messages: lead with fix proposals
├── ci-fixer-2 (teammate, plan approval required)
│   ├── Owns: second batch of failing PRs
│   └── Messages: other fixers about shared dependencies
└── ci-fixer-3 (teammate, plan approval required)
    ├── Owns: third batch of failing PRs
    └── Cross-checks: fixes for conflicts

Key Features

1. Parallel repo processing: Each teammate owns a set of repos
2. Cross-repo awareness: Teammates can message about shared dependencies
3. Plan approval for CI fixes: Lead reviews fix plans before implementation
4. Unified reporting: Reporter teammate aggregates all results
5. Worktree-aware: Teammates work in correct worktree paths

Worktree Integration

Each teammate is spawned with the correct cwd for their repos. The skill documents the worktree structure:

~/git/<repo>/main/           # Always use main worktree for sync
~/git/<repo>/feat/<branch>/  # Use feature worktree for CI fixes

Acceptance Criteria

• /team-sync processes multiple repos in parallel
• /team-fix-ci uses plan approval for safe CI fixes
• Teammates work in correct worktree paths
• Cross-repo dependency detection via messaging
• Unified status report generated
• Graceful fallback to sequential when teams disabled
• Works with the existing worktree structure from CLAUDE.md

Dependencies

• Depends on: agent-teams-orchestrator plugin (feat: create agent-teams-orchestrator plugin with team lifecycle management #15) for lifecycle patterns

[JacobPEvans-personal]

Parent epic: #14 | Depends on: #15

[claude]

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

[JacobPEvans-personal]

Closing: Claude Code's Agent Teams feature works natively without custom plugins, skills, hooks, or orchestration. The custom Agent-Teams plugin work tracked here is no longer needed — native primitives cover these patterns. No follow-up planned.