engineering-writinglisted

# Engineering writing Write clear, brief, accurate and useful engineering prose in Australian English. Cut first. Add only what serves the reader's job and belongs in this document. This skill is a specialization of the `natural-writing` hub: it owns codebase/README/commit/PR artefact types and links to the hub for the Australian English default, the anti-AI taxonomy and the condense pass. See `references/process.md`, `references/style-standard.md` and `references/engineer-voice.md` for where each hub link applies. ## Workflow 1. Name the audience, prior knowledge, required action or decision, and format constraint. If the reader's job is unclear, flag it before drafting. 2. Choose one relevant pattern: [document patterns](references/document-patterns.md) for codebase/short-form prose, [requirements and planning](references/requirements-and-planning.md) for already-decided pre-build content, or [architecture and communication](references/architecture-and-presentations.md) for approved designs, ADRs, presentations and briefs. Do not load all three. 3. Structure before sentences: front-load the point, use decision-oriented headings and one idea or requirement per unit, then move wrong-home material. 4. Lock facts, logic, stance, evidence, obligations, behaviour, identifiers, paths, commands, flags, parameters, keys, error codes, numbers, units, dates, citations and quoted terms. 5. Revise in separate structure, accuracy, clarity/concision, voice and