technical-writinglisted

# Technical writing Help a defined reader complete a task or understand a technical subject without changing technical truth. ## Core contract Apply these priorities in order: 1. Preserve facts, uncertainty, intent, and documented constraints. 2. Serve the intended reader and their goal. 3. Make the document accurate, navigable, and reproducible. 4. Improve sentences without flattening the author's useful voice. 5. Avoid style churn: correct prose does not need different wording merely to match a preference. Never invent behavior, output, prerequisites, compatibility, measurements, citations, decisions, or rationale. ## Scope and boundaries Use this skill for substantial technical documentation and design artifacts. Do not use it for code-only tasks, marketing copy, product UI strings, controlled or verbatim text, release notes, PR descriptions, commit messages, or a small wording cleanup. Related skills: - When available, use `brainstorm` for consequential design exploration; otherwise use the host's workflow and mark unresolved decisions. - When available, use `unslop` for small style edits and the final pass after substantial prose changes. - When available, use `explain-code` to establish current mechanics for a document; otherwise inspect local evidence here. - When available, use `clarify` for unresolved behavior mismatches or rationale; otherwise report the uncertainty instead of inventing an answer. ## Load references only when needed - Read [references/do