What problem does it solve? Technical documents often become bloated with implementation details, stale line references, and narrative filler, making them slow to read and quick to rot. This Skill enforces a disciplined writing style so design docs, investigation writeups, and PR descriptions stay precise, scannable, and durable as systems evolve. ## Core Features & Use Cases - Altitude control: Keeps prose at the concept level — behavior and intent over control flow — with rules for when code symbols, links, and pseudocode are appropriate. - Structure and visual aids: Summary-first doc structure (TL;DR, context, detail, open questions) plus guidance on tables, Mermaid diagrams, and hand-authored SVGs, including rendering via mmdc. - Prose mechanics: Newspaper-headline brevity, symbol conventions (→, ⇒, ~), list formatting, and living-doc discipline that forbids changelogs and retrospective framing. - Use Case: Draft a design doc for a service migration: lead with a terse TL;DR table, describe behavior at the system level, attach code links to prose anchors, then publish to Google Docs via the companion md-to-gdoc and gdoc-upsert skills. ## Quick Start Use the authoring-technical-docs skill to write a design doc for the proposed caching layer migration, following its structure and style rules.
