technical-writinglisted

# Technical Writing ## Iron Law `THE READER'S UNDERSTANDING IS THE DELIVERABLE: PLAIN WORDS, ONE THEME, EVIDENCED CLAIMS.` The style this skill produces is named load-bearing prose: technical writing that is more Hemingway than David Foster Wallace. Every sentence carries evidence, advances the document's one theme, or builds the reader's knowledge; a sentence doing none of those is cut. Its opposite is signpost language: words that point at the structure without holding any weight. ## When to Use - A forward-looking document is the deliverable: one that records a decision or proposes a future. Design docs, ADRs, RFCs, tech specs, PRDs, requirements and acceptance criteria, system analyses, transition plans, technical strategy, proposals. - Another skill (`specify`, `architecture`, `documentation`) produced a document whose readers were not in the room when the work happened. - Reviewing or editing an existing document for voice, structure, knowledge build-up, or theme drift. ## When NOT to Use - Documentation that describes code and systems as they exist (READMEs, runbooks, tutorials, reference docs, module docs, code comments), and doc placement, ownership, lifecycle, and rot; use `documentation`. - The design decisions the document records; use `specify` and `architecture`. This skill owns how the document reads, not what it decides. - Commit messages; use `commit`. - CHANGELOG, release notes, and migration notes; use `release`. - People-management