What problem does it solve? Documentation drifts from code and architectural decisions get re-litigated by every fresh agent or contributor because nothing records what was decided and why. This Skill enforces a single documentation standard — Markdown + Mermaid only, docs placed next to the code they describe — plus a governed ADR practice so decisions stay durable and discoverable. ## Core Features & Use Cases - General documentation standard: All docs are Markdown with Mermaid diagrams (no static images), with placement rules (a docs/ folder per deployable unit), diagram-type guidance (flowchart, erDiagram, sequenceDiagram), and expected content per file. - ADR practice (MADR): A significance gate decides when an ADR is owed, MADR format records context, options, and consequences, with per-library zero-padded numbering and a proposed → accepted → superseded status lifecycle. - Record disposition rules: Four governed dispositions for retiring or relocating records (delete with History row, fold context into the superseding record, keep, or absorb into a governing document), including the current-codebase rule that replaced supersede-never-delete. - Licensing rule: Every repo carries an MIT LICENSE file with matching manifest fields. - Use Case: A change touches infrastructure in a repo — the Skill tells you an ADR is owed, which library it belongs in (methodology vs product), how to number and format it, and how to retire the record it reverses. ## Quick Start Ask the agent to write an ADR for the infrastructure change in this repo following the documentation-standard skill, or to review the README and architecture docs against the Markdown + Mermaid standard.
