project-recordlisted

# 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 | |---|---|---| | `--todo` | park this; we are not building it now | `record.todo` **and** `record.decisions` — a deferral is a decision | | `--log` | we decided this; record the reasoning | `record.decisions` only | Both go through the same routing table, the same file rules, and the same index regeneration. Two flags rather than one because the skill does two jobs that feel different to whoever is typing, not because the logic differs. **Project facts come from `.claude/workflow.json`**: `record.todo`, `record.decisions`, `record.decisionsIndex`, `record.openDecisions`, and `commands.indexRegen`. The fallbacks when a key is absent are [`manifest.md`](../../workflow/manifest.md)'s, not this file's — say which ones you used. `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 [`~/.claude/workflow/ownership.md`](../../workflow/ownership.md); what each record may and may not hold is [`record-contract.md`](../../workflow/record-contract.md), which is the authority if this file and that one ever disagree. ## Routing: which file, and why it matters ``` Is it settled? ├─ No — we cannot start until someone chooses → record.openDecisions │