lane-record-synclisted

Reconcile every lane's records at once — conflicts between them, and work one lane's plans imply for another. Every finding needs an explicit ruling: accept, accept as critical, defer or decline. What is accepted goes to the addressed lane's transfer queue, never its records. Invoke only as its own slash command; it has no flag.
qupunto/wss · ★ 1 · Data & Documents · score 75

Install: claude install-skill qupunto/wss

# Synchronising the lanes Lanes divide one project so sessions cannot collide. What they cannot divide is the **dependencies between the work** — a plan in one lane changes a data shape, an endpoint or a contract another lane builds against, and nothing in the ordinary flow surfaces that until someone hits it. This skill reads every lane's records together, which no other session can do, and turns what it finds into entries in the lanes' transfer queues. **It is slash-invoked and nothing else.** No flag, no `commands/` wrapper, no dispatch from another skill. Who owns what is [`wss/workflow/WSS.OWNERSHIP.md`](../../wss/workflow/WSS.OWNERSHIP.md); what a queue holds, and every other lane rule, is [`WSS.LANE-CONTRACT.md`](../../wss/workflow/WSS.LANE-CONTRACT.md); what a record holds is [`WSS.RECORD-CONTRACT.md`](../../wss/workflow/WSS.RECORD-CONTRACT.md); the keys are [`WSS.MANIFEST.md`](../../wss/workflow/WSS.MANIFEST.md). ## Two hard preconditions **1. The main checkout, never a lane worktree.** If `.claude/WSS.LANE` names a lane, **stop and say so.** **2. `WSS.lanes.named` must declare more than one lane.** With none or one, **say so and stop.** ## What it costs, said before it runs State, in three or four lines: how many lanes, how many record files that is, and that every finding will need a decision from the user. Then run. This is the run the user should be able to stop before it starts. It reads every lane's `todo`, `openDecisions` and `roadmap`, and the cross