What problem does it solve? Keeping project documentation synchronized with code is a persistent challenge: ADRs get duplicate numbers across parallel branches, docs drift out of sync with the code they describe, and facts get scattered across multiple files. This Skill routes every fact to its single owning document, scaffolds Architecture Decision Records with collision-safe numbering, and audits diffs to prove the docs still match the code. ## Core Features & Use Cases - ADR scaffolding with number reservation: Claims the next ADR number via a coordination branch using compare-and-swap writes, preventing collisions when multiple sessions branch from the same preprod tip. - Diff-based docs audit: Maps every changed file against the ownership table in docs/README.md, applies mechanical updates (env vars, surface tables, index rows), and runs the check-docs script to catch errors. - Fact routing: Places any topic in exactly one owning doc, moves duplicated facts, and escalates tradeoffs with non-obvious rationale into full ADRs. - Use Case: After implementing a new authentication flow, run the check mode to automatically update SECURITY.md, add new environment variables to .env.example, and verify the docs checker passes before merging. ## Quick Start Ask the assistant to write an ADR for your latest architectural decision or to check that the documentation still matches your current branch's changes.
