Team Coordination

When you've got multiple Claude Code sessions hitting the same codebase, you need shared state or you'll trip over each other. This sets up a coordination layer with team state files, todo claiming, and handoff notes so developers know who's touching what files and what decisions have already been made. The workflow is deliberate: check state.md before starting, claim your todo, push updates every couple hours, write a handoff note if you're passing work mid-flight. It's not glamorous but it prevents the "wait, weren't you refactoring auth too?" problem. Best for teams actually using Claude to collaborate, not just occasionally pair programming.

skills.sh installs: 221
GitHub stars: 685
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add alinaqi/claude-bootstrap --skill team-coordination --agent claude-code

Installs into .claude/skills of the current project.

Files

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.                          │
└─────────────────────────────────────────────────────────────────┘