team-coordination

Create a shared _project_specs/team directory with state.md and contributors.md files tracked in git. Each session reads the state file at start, claims todos with annotations, and pushes state updates so other sessions stay aware of active work.

Track files touched per active session in the team state.md file and check it before modifying code. If a conflict area overlaps, coordinate with the other contributor first and log the overlap in the Conflicts to Watch section.

Create a handoff markdown file in _project_specs/team/handoffs describing status, completed work, remaining tasks, key decisions, and files to start with. Commit and push it so the receiving developer's next session can pick up context immediately.

Yes, coordination relies entirely on markdown files committed to the git repository. Sessions sync by pulling before starting and pushing state updates every one to two hours, so no external service is required.

State can become stale between pushes, and simultaneous edits to state.md may cause merge conflicts. It works best for small teams with disciplined pull-and-push habits rather than large teams needing real-time locking.