What problem does it solve? Writing contract-bound documentation by hand leads to drift: sections go missing, enum values get misspelled, and coverage claims go unverified. This Skill ensures every documentation artifact — a docs/contracts/ schema, a frontmatter-bearing record, or a template rendering into one — validates against its contract before being called done. ## Core Features & Use Cases - Contract-derived structure: Authors every required section in the contract's exact order and spelling, deriving structure from the contract itself rather than a drift-prone parallel copy. - Exact machine-readable frontmatter: Places status, phase, and enum fields in YAML frontmatter with character-for-character fidelity to the contract's enumerated values. - Mechanical coverage checks: Adds grep-based assertions that verify every item of a source set appears in the document, and flags genuine gaps explicitly instead of fabricating coverage. - Use Case: When writing a completion report or findings document governed by a docs/contracts/ schema, use this Skill to produce an artifact whose normative core validates cleanly, with appendices fenced outside the validated core. ## Quick Start Author a completion report that validates against its docs/contracts schema, with exact frontmatter enums and a mechanical coverage check for every required item.
