← ClaudeAtlas

recordlisted

The project's record of work and why. `--wss-todo` parks what is not being built now: task to the TODO LIST, reasoning to the decision log. `--wss-log` records a decision already made. Also on "park this", a decision announced as settled ("we're going with X"), pasted standup notes, or when you judge something premature. Not on a decision mentioned in passing.
qupunto/wss · ★ 1 · Data & Documents · score 72
Install: claude install-skill qupunto/wss
# The project record This skill owns the project's task and decision records, and one idea: **nothing that was decided should survive only in a chat log.** | Flag | Means | Writes | |---|---|---| | `--wss-todo` | park this; we are not building it now | `WSS.record.todo` **and** `WSS.record.decisions` — a deferral is a decision | | `--wss-log` | we decided this; record the reasoning | `WSS.record.decisions` only | Both go through the same routing table, the same file rules, and the same index regeneration. **Project facts come from `.claude/WSS.WORKFLOW.json`**: `WSS.record.todo`, `WSS.record.decisions`, `WSS.record.decisionsIndex`, `WSS.record.openDecisions`, and `WSS.commands.indexRegen`. Where a `.claude/WSS.LANE` selector names a lane, `WSS.lanes.named.<lane>.records.X` overrides `WSS.record.X` for whichever of those are splittable — [`WSS.LANE-CONTRACT.md`](../../wss/workflow/WSS.LANE-CONTRACT.md)'s resolution rule; `WSS.record.decisions` never splits, and under lanes it is fed by promotion, per the same file. The fallbacks when a key is absent are [`WSS.MANIFEST.md`](../../wss/workflow/WSS.MANIFEST.md)'s, not this file's — say which ones you used. `WSS.record.decisionsIndex` is the one with no fallback: without it, append to the decision log and say the index was not regenerated. This skill is the **sole writer** of every one of them. Who owns everything else is [`wss/workflow/WSS.OWNERSHIP.md`](../../wss/workflow/WSS.OWNERSHIP.md); what each record may and may not