What problem does it solve? TinySocs documentation drifts: design-doc status headers contradict CLAUDE.md, rule counts disagree across files, and the two TinyDocs artifacts list different rule IDs. This Skill tells you which document to trust first, catalogs every known inconsistency with file:line evidence, and enforces the writing rules that prevent new drift. ## Core Features & Use Cases - Source-of-truth routing: Establishes the priority order docs/roadmap.md > design-doc status headers > CLAUDE.md when documents disagree about feature status. - Doc-drift ledger: A maintained table of 12 known inconsistencies (stale rule counts, wrong version strings, mismatched scheduled-task names, dead rule IDs in shipped docs) with an assigned fix owner for each. - TinyDocs synchronization rules: Keeps tinydocs/*.md and packaging/detection/rule_docs.yml aligned with the 19-rule enabled set whenever rules are enabled, disabled, or renamed. - Writing discipline: Date-stamp volatile numbers, no prices in docs, ASCII-only near PowerShell 5.1 content, cross-reference instead of restating facts. - Use Case: When asked to update docs/design/continuous-validation.md, you first learn its "not yet implemented" header is stale — the pipeline is built but blocked on a harness bug — and write the accurate status instead of trusting the header. ## Quick Start Ask the assistant to check whether CLAUDE.md's claim about rule signing being greenfield is still true and reconcile it against the design docs.
