Documentation
README
Worktree Isolation
Use one worktree per independent implementation concern. This keeps peers from editing the same files blindly and makes review/cleanup tractable.
When to isolate
Create or select an isolated worktree when:
- Two peers may implement in parallel.
- The change is large enough to outlive the current session.
- The work is speculative, risky, or likely to need review.
- The main worktree has unrelated dirty state.
Use the current worktree for small, direct, low-risk edits when it is clean enough and no other peer owns the same files.
Before dispatch
Check:
git status --short --branch
git worktree list
repowire peer list
Tell the peer which worktree and branch it owns, what files are likely in scope, and whether it may commit or only report.
This is the opening of the README. Read the full README on GitHub.