loom-git-workspace-isolationlisted

# loom-git-workspace-isolation Git workspace isolation is a safety playbook for code-facing Loom work. It detects the current Git/workspace state, chooses the least surprising isolation mechanism, verifies a clean baseline, and records provenance for later finish or cleanup. ## Loom Routing Common routes use these Loom skills for durable records or follow-up workflow: `loom-tickets`, `loom-plans`, `loom-ralph`, `loom-evidence`, and `loom-audit`. Follow any named Loom skill fully. This playbook adds workflow pressure; it does not shorten target-skill requirements. It does not replace ticket scope, branch policy, evidence, or operator approval. ## Use This Playbook When Use this playbook when: - starting non-trivial implementation work - executing a plan with multiple tickets or ticket-defined worker scopes - the current branch contains unrelated work - a worker needs an isolated write scope - baseline tests or setup need to distinguish pre-existing failure from new failure - cleanup or branch finish later depends on knowing who owns the workspace Skip it when the operator explicitly wants in-place editing and the ticket scope is small enough that isolation would not reduce risk. ## Route Use this route: ```text detect -> decide -> isolate -> setup -> baseline -> record -> proceed ``` ## Detect Before creating anything, inspect the current workspace state. Check: - current branch or detached state - uncommitted changes and whether they are related to the ticket