What problem does it solve? The Sonder Runtime repository contains over 600 markdown files governed by strict rules: every fact has exactly one home, generated catalogs must never be hand-edited, and four checker scripts fail the build when documentation drifts. This Skill tells you exactly where each kind of fact belongs and how to write it without tripping a CI gate. ## Core Features & Use Cases - Document taxonomy routing: Maps each type of fact (contracts, requirements, decisions, procedures, concepts) to its single authoritative location, from ARCHITECTURE.md to docs/runbooks/ to the 19-page wiki. - Gate-compliant writing: Provides templates and naming rules for ADRs, evidence documents, runbooks, and wiki pages that pass check_documentation_authority.py, check_evidence_documents.py, and check_requirement_evidence.py. - Ledger and checkbox discipline: Enforces the append-only requirements.jsonl workflow so master-spec checkboxes are only flipped with a verified evidence record. - Use Case: When asked to "write an ADR" for a new architectural decision, the Skill produces a correctly named docs/adr/ADR-YYYY-MM-DD-slug.md file matching the enforced regex and template, then runs the pre-commit checker suite to confirm all gates pass. ## Quick Start Ask the assistant to write an ADR documenting a new architectural decision and place it in the correct docs directory following the repository conventions.
