atdd-team

# Team-Based ATDD Workflow Orchestrate an agent team that follows the Acceptance Test Driven Development workflow. The team lead coordinates specialist agents through six phases. Each phase is run by a **fresh agent invocation** — no agent persists across phases. ## Why fresh per phase A long-lived agent's context compacts as a feature runs for hours. Compaction silently erodes role identity and discipline: agents lose their role, invent constraints that do not exist, and skip expensive-but-required steps. A fresh per-phase agent reloads its instructions clean — the same insight as the engineer plugin's per-skill model. The "team" exists for **parallelism** across features, not for keeping agents alive within one feature. ## Team Detection Before spawning phase agents, check for existing teams: 1. Read `~/.claude/teams/` to list active teams. 2. If a team exists, present the user with a choice: - **Extend** — run the ATDD phases for this feature alongside the existing team. - **Replace** — shut down the existing team and run ATDD fresh. - **New team** — run the ATDD pipeline as a separate team. If no team exists, proceed directly. ## Roles Each phase is run by a fresh agent invocation scoped to that phase, then ended. | Role | Maps to | Owns phase | |------|---------|-----------| | `spec-writer` | discuss, discover-acs, atdd spec step | 1 Spec Writing | | `reviewer` | spec-guardian agent | 2 Spec Review | | `implementer` | atdd impl, pipeline-builder | 3 Pi...