working-in-worktreeslisted

# Working in Worktrees ## Overview This skill governs **workspace isolation** for code work in DorkOS — a repo that is routinely worked by several agents and sessions at once. It teaches the one decision rule (_one checkout, one writer_), the concrete failure mode that makes isolation non-optional, the exact mechanics for creating, entering, and cleaning up a worktree without losing anyone's work — and the half that isolation does **not** buy you, because worktrees separate working trees but share every ref. The repo-wide rule lives in `AGENTS.md` → **Worktrees**. This skill is the mechanics and the _why_. ## When to Use - You are about to make a code change and the checkout **may be shared** with another agent or session. - You are running the `/flow:execute` stage (the workspace-choice phase of the flow plugin's `executing-specs` skill) — the unified `/flow` execution gate. - You are running parallel work that mutates tracked files. - You are comparing your branch against `main` across **more than one command** — a conflict investigation, a red-before drill, a changelog gate, a "what did `main` change" question. - You need to create, enter, exit, or remove a worktree and want the safe procedure. - You are _unsure_ whether to isolate — the default answer for code work in this repo is **yes**. ## Key Concepts ### The rule: one checkout, one writer `main` is the **clean integration tree**, not a shared scratchpad. Code changes default to an **isolated worktree**; `main