skills.rest
lciacci
lciacciCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

team-coordination

Coordinate shared development work across parallel Claude Code sessions.

Updated Jun 19, 2026
Search Tags:#claude code#todo management#team coordination#shared state#conflict prevention#collaborative coding#work handoffs
One-click install
npx skills add https://github.com/lciacci/tessera --skill team-coordination-lciacci
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: team-coordination
Source: https://github.com/lciacci/tessera/tree/main/skills/team-coordination
Command: npx skills add https://github.com/lciacci/tessera --skill team-coordination-lciacci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents conflicts, duplicated effort, and lost context when multiple developers or Claude Code sessions work on the same repository.

Core Features & Use Cases

  • Shared Team State: Track active contributors, touched files, claimed todos, announcements, and conflicts.
  • Work Handoffs: Document progress, remaining tasks, key decisions, files, and cautions when transferring work.
  • Decision and Todo Syncing: Claim tasks, record architectural decisions, coordinate ownership, and maintain shared project context.
  • Use Case: When several developers are implementing authentication, payments, and infrastructure changes concurrently, use this Skill to coordinate file ownership, synchronize decisions, and create reliable handoffs.

Quick Start

Ask the team-coordination skill to review the current team state, identify conflicts, and help claim an unassigned todo.

Frequently Asked Questions about team-coordination

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent conflicts when multiple developers work on the same repository?▼

To prevent conflicts in collaborative coding, use shared project-state files to track active contributors, touched files, and claimed todos so parallel sessions avoid duplicated effort and overlapping changes.

What is the best way to track todo ownership across a multi-person development team?▼

Tracking todo ownership across a team requires shared project-state files where contributors make explicit claims on tasks, record architectural decisions, and synchronize updates through Git-based integration.

Do I need shared project-state files to coordinate concurrent development work?▼

Yes, shared project-state files are required to coordinate concurrent development work, providing the structured basis for disciplined synchronization, explicit claims, and decision records across the team.

How do I synchronize architectural decisions across multiple developers?▼

Synchronizing architectural decisions across developers requires recording decisions in a shared project-state file, ensuring all parallel Claude Code sessions maintain shared project context and consistent coordination.

Related Skills

Explore More Software Engineering Skills→
chaimtchaimt

speckit-git-initialize

Initialize a Git repository with an initial commit in the current directory.

Community
Intermediate
aadorianaadorian

merge-changes

Merge a topic branch into its merge base branch with conflict resolution.

Community
Intermediate
AnveioAnveio
1

claude-agent-sdk

Build autonomous coding agents with the Claude Agent SDK for TypeScript.

Community
Advanced
Thanh-aperoThanh-apero
1

project-management

Manage project tasks and track progress using Claude native tasks and plan files.

Community
Advanced