Software Development
Coordinate Peer Sessions
Coordinate safely with a peer interactive session sharing the same git worktree — check first whether a separate worktree removes the problem, then declare path and branch scope before the first edit, survive a contended index lock, and review the whole branch before opening a PR. Activate when starting work in a repository that may already be occupied, when a git command fails with `index.lock: File exists`, when `guard:snapshot` refuses because a snapshot already exists, or when a commit turns out to contain a file this session never edited. When one session leads and the other supports, divide the labour by shape and re-derive every reported number against a named revision before citing it. Distinct from subagent concurrency: a peer session cannot be bracketed, because no baseline exists from before its edits.
- Publisher / source
- pjt222/agent-almanac (found on the CSV list)
- Upstream record
- pjt222/agent-almanac
- Version
- Version 1
- Published
- Publication review
- Approved for publication
- Content fingerprint
7422afe482390ff898c1da106a72890c50f677693af4aacb7ea17f728139e6ac