ledger-flow

Designate exactly one file as the ledger you reconcile, and convert all other documents that mirror the same work into references pointing to it. Never update plan documents, test lists, and STATUS files in parallel, since one will always lag and contradict the others.

Use a three-state legend defined once at the top of the ledger: `[ ]` for not started or unverified, `[~]` for partial completion with the remainder noted inline, and `[x]` only when both implementation and verification evidence exist. Do not invent custom markers like `[対象外]`, which break machine checks.

Every `[x]` or PASS record must carry an evidence pointer on the same line or immediately after: a log file path, test name, commit hash, or CI run URL. Verify the log actually exists before recording, and never mark items complete before the corresponding commit.

Close any completed or obsolete document by adding a `closed (YYYY-MM-DD), successor: <doc or none>` line at the top. Leaving documents open lets stale checkboxes and 'in progress' statements fossilize, forcing later readers to guess whether the document is still alive.

No. The superpowers SDD ledger at `.superpowers/sdd/<plan>/progress.md` is owned by superpowers and keeps its own line format. This Skill governs hymme-side ledgers such as T-ID ledgers, todo files, and STATUS documents, and forbids rewriting SDD ledger notation.

Manual counting of unchecked items and ID gaps is error-prone, so the Skill recommends deterministic machine checks such as PreToolUse hooks that block on remaining `- [ ]` items or numbering gaps. It also forbids inventing new ledger formats when plain Markdown checkboxes suffice.