rule-workflow-spinelisted

# The spine A skill library has two failure modes and only one of them is discussed. The discussed one is a missing skill. The other is **fifty skills and no order**, where the model picks by description similarity and the pick is a lottery. This file is the order. It adds no capability; it decides what fires when. Four steps. Each ends on a condition you can check, not on a feeling that the step is finished. ## 1. Isolate: before the first edit Load `isolate`. Work happens in a git worktree branched from the remote default branch, never in a tree another session is using. **Ends when** `git branch --show-current` prints something other than the default branch, and `git status --porcelain` in the new tree is clean. Skip only when the repo has one working copy and one session in it. A repo running parallel agents has no exemption: two agents in one tree produce a collision whose symptom is a lost edit, and a lost edit is not reported by anything. ## 2. Build: the work itself No skill owns this step. The repo's own conventions do, plus whichever rule skills the paths you touch pull in. **Ends when** the change compiles and the thing you set out to change behaves differently. Not when it is correct. That is step 3's job, and merging the two is how a build declares itself proven. ## 3. Prove: evidence, not assertion Load `prove`. The before state is captured **while the defect still reproduces**, which is the only moment it is free, and the after state once the change