What problem does it solve? Documentation prose often reads as machine-generated or carries normative statements whose force is ambiguous, leaving readers unable to tell what is required of them. This Skill standardizes how Markdown prose is written across docs pages, SKILL.md files, and README files. ## Core Features & Use Cases - House Voice Rules: Enforces plain, declarative, third-person prose with one claim per sentence, tables for parallel content, and calibrated hedging. - RFC 2119 Convention: Applies MUST/SHOULD/MAY keywords on normative pages with the required shortcode invocation, and forbids unfalsifiable phrasing like "MUST do its best to". - Authorship Provenance: Manages the params.author and params.agent frontmatter fields, including the rule that agents stamp new pages but never touch existing fields unless an edit rewrites over half the page. - Use Case: When drafting a new stability policy page under docs/content/, apply the voice rules, invoke the rfc-2119 shortcode, stamp the agent field, and verify the page against the review checklist. ## Quick Start Review this Markdown page against the docs-writing voice rules and RFC 2119 conventions, then fix any violations.
