team-coordinationlisted

# Team Coordination Skill **Purpose:** Enable multiple Claude Code sessions across a team to coordinate and work together without conflicts. Manages shared state, todo claiming, decision syncing, and session awareness. --- ## Core Philosophy ``` ┌─────────────────────────────────────────────────────────────────┐ │ TEAM CLAUDE CODE │ │ ───────────────────────────────────────────────────────────── │ │ Multiple devs, multiple Claude sessions, one codebase. │ │ Coordination > Speed. Communication > Assumptions. │ │ │ │ Before you start: Check who's working on what. │ │ Before you claim: Make sure nobody else has it. │ │ Before you decide: Check if it's already decided. │ │ Before you push: Pull and sync state. │ └─────────────────────────────────────────────────────────────────┘ ``` --- ## Team State Structure When a project becomes multi-person, create this structure: ``` _project_specs/ ├── team/ │ ├── state.md # Who's working on what right now │ ├── contributors.md # Team members and their focus areas │ └── handoffs/ # Notes when passing work to others │ └── [feature]-handoff.md ├── session/ │ ├── current-state.md # YOUR session state (personal) │ ├── decisions.md # SHARED - architectural decisions │ └