doc-organization

Review documentation against information organization principles: keep current state separate from change history, define identifiers before use, define each conclusion in exactly one place, and write for readers who lack your current context. This Skill applies those five principles as judgment, not mechanical rules.

Markdown linting checks markup usage such as heading levels, code block languages, and punctuation spacing. Document organization review checks where information lives: whether conclusions are duplicated across files, whether introductions guide reading decisions, and whether deprecated items are left undefined.

No. Deliberate duplication can be justified, such as test cases quoting requirement text for local readability or runbooks staying self-contained offline. The requirement is knowing the synchronization cost you are paying, not mechanically removing every repetition.

No. When a document references a numbered item that was never defined, no one can reconstruct what it pointed to after the fact, and AI would only be guessing. Definitions must be written at the moment the identifier is first introduced.

Change rationale belongs in a changelog or ADR section while the body states only the current position. Mixing them makes it impossible to tell which statement is authoritative, but rationale should stay near the content it explains rather than being dumped at the end.