parallel-worklisted

______________________________________________________________________ ## parallel-work Manage parallel development streams. Each stream is an isolated copy of the project (a git worktree) on its own branch, so multiple Claude Code sessions can build different stories at the same time without touching each other's files. ## When Parallel Work Makes Sense (and When It Doesn't) Parallel work is **opt-in, never required**. The default workflow is one branch, one story at a time — that keeps the user fully aware of every change. **Good fit:** - Stories are self-contained: no dependencies on each other, no shared hot files - Each story is a complete outcome on its own (outcome over output) - The user is comfortable reviewing several streams of change **Bad fit — advise sequential work instead:** - Stories depend on each other (one needs the other's code or schema) - Stories touch the same files or the same module's core - The stories are parts of one mechanism (they should be ONE story, not parallel streams) The `start` command checks this before creating anything (see below). When in doubt, recommend sequential: merging conflicting parallel work costs more than it saves. ## Commands ### Status (default, or "status"/"list") Run the status script: ```bash bash "${CLAUDE_PLUGIN_ROOT:-.claude}/skills/parallel-work/scripts/worktree-status.sh" ``` Show all active streams with their branches, their parent (from `git config branch.<name>.exosuitParent`), and ahead/behind coun