What problem does it solve? When a project maintains several documents (README.md, PLAN.md, CLAUDE.md, TECH-DEBT.md, folder READMEs), the same fact tends to get written in two places, and the copies drift apart. This Skill decides which single document each fact belongs in and how to add it without duplicating or contradicting what other files already say. ## Core Features & Use Cases - Fact routing table: Classifies a fact by kind (user-facing behavior, spec invariant, coding rule, procedure, tech debt) and assigns exactly one home document, with every other file linking to it by anchor. - Four-step edit procedure: Search before writing, search for what the new fact makes false (including grepping old wording and skill frontmatter), write once in the named home, then run the docs-check gate. - Drift and deletion safeguards: Rules for dating data claims, verifying moved sentences land somewhere, respecting line budgets, and re-reading cited stories before quoting them. - Use Case: At the end of a development phase that changed bot behavior, use this Skill to decide whether each new fact goes in README.md, PLAN.md, or a skill, and to catch the stale sentences the change invalidated. ## Quick Start Use the write-a-doc skill to decide where this new rule about the merge command belongs and update the documentation without duplicating it.
