What problem does it solve? Repository documentation rots when genres are mixed: decisions get edited away, reference pages go stale, and wikis lose trust. This Skill enforces a disciplined docs tree where every page has a clear genre, lifecycle, and machine-checkable freshness signal. ## Core Features & Use Cases - Genre Selection: Decides whether content belongs as an ADR, dated note, reference page, guide, or MOC based on the receipts-vs-state maintenance rule. - Docs Tree Conventions: Defines directory roles (reference/, notes/, guides/, diagrams/), frontmatter contracts (status, updated), dated correction banners, and probe blocks for automated staleness verification. - Domain Modeling: Governs CONTEXT.md glossaries and docs/adr/ decision records with lazy-creation and term-sharpening protocols. - Mermaid Diagrams: Provides a full reference catalog for class, sequence, ER, C4, and architecture diagrams. - Use Case: When asked to document why a team rejected a design alternative, the Skill routes the content to a new ADR in docs/adr/ rather than burying it in a living reference page. ## Quick Start Ask the agent to write or audit documentation for your repository's docs tree, for example by requesting an ADR recording a rejected design decision.
