What problem does it solve? AI-generated output often arrives as unreadable walls of prose, broken markdown tables, or jargon-heavy status reports that force readers to decode internal references. This Skill standardizes how all human-facing output is rendered and validates drafts against those rules. ## Core Features & Use Cases - House style definition: Establishes the visual-vs-prose split, a closed catalogue of canonical visual forms (cycle brackets, queue partition grids, workstream lanes, gate tables), density caps, and prose skimmability rules. - Validation and normalisation: Reviews draft output and flags or rewrites violations such as markdown tables that should be definition lists, ungrounded issue IDs, buried load-bearing statements, and token-wasting preamble. - Issue gloss contract: Enforces a synthesis contract where every tracker issue is rendered with an ID, a plain-English gloss, and unlock-chain consequences, with jargon like "principle 6" or "ADR-N" banned from user-facing text. - Use Case: A delivery agent drafts a morning brief listing held issues as a dense paragraph; run the normalise pass to rewrite it into bold-lead bullets with grounded glosses and release instructions. ## Quick Start Normalise this draft status update to house style and list any violations you fix.
