simplified-technical-englishlisted

# Simplified Technical English for software documentation ## What this is Simplified Technical English (STE) is a controlled natural language: a restricted vocabulary plus a set of writing rules. The authors built it so that a maintenance technician in Jakarta and one in Toulouse read the same sentence and reach the same conclusion. It removes ambiguity rather than making prose pretty. This skill adapts those principles to software documentation. It is an independent adaptation, not the specification. Rule numbers such as `[3.6]` point back to ASD-STE100 Issue 9 (© ASD) for traceability. ASD holds the copyright on the official dictionary and on the rule text, so this skill does not reproduce them. See `references/rule-index.md` for the full tag list. ## When to apply it, and when not to Apply it to: PR descriptions, commit bodies, ADRs, READMEs, API reference, runbooks, incident postmortems, migration guides, error and log messages, changelogs, code comments, onboarding docs. Do not apply it to: marketing copy, blog posts, conference talks, anything where voice and rhythm matter more than a single interpretation. STE deliberately sounds flat. The flatness is the point. STE is the wrong tool for persuasion. Half-application is worse than none. If a document is in scope, apply the rules throughout it, not to selected paragraphs. ## How to use this skill Choose the workflow that matches the request. **The user writes something new.** Apply the core rules below as you d