| name | technical-communication |
| description | Technical writing, engineering specifications, reports, presentations, and documentation standards for engineering practice. Covers document types (requirements documents, test reports, design rationale, operations manuals), writing style, data visualization, engineering drawing standards, and oral presentation techniques. Use when writing engineering documents, presenting technical results, creating specifications, or learning documentation best practices. |
| type | skill |
| category | engineering |
| status | stable |
| origin | tibsfox |
| modified | false |
| first_seen | "2026-04-12T00:00:00.000Z" |
| first_path | examples/skills/engineering/technical-communication/SKILL.md |
| superseded_by | null |
Technical Communication
Engineering that cannot be communicated is engineering that does not exist. The finest analysis is useless if the reader cannot follow it. The most thorough test is wasted if the report does not document what was tested, how, and what was found. Technical communication is not a soft skill appended to engineering -- it is a core engineering competency. This skill covers the full range of engineering communication: written documents, visual presentations, engineering drawings, and oral delivery.
Agent affinity: polya-e (pedagogical communication, scaffolded explanation), johnson-k (technical precision, NASA documentation standards)
Concept IDs: engr-design-communication, engr-testing-methodology, engr-data-from-experiments, engr-codes-of-ethics
Principles of Engineering Writing
Clarity
Engineering writing serves one purpose: to transfer technical information from the writer's mind to the reader's mind with minimum distortion. Every sentence should advance this transfer. Sentences that do not transfer information are noise.
Bad: "It is important to note that the utilization of advanced computational methodologies was employed in the determination of stress distribution."
Good: "We computed stress distribution using finite element analysis."
The good version says the same thing in half the words with double the clarity.
Precision
Engineering writing is precise. Numbers have units. Claims have evidence. Conclusions follow from data.
Imprecise: "The beam was strong enough."
Precise: "The beam sustained a 50 kN point load at midspan with 12 mm deflection, within the L/360 serviceability limit of 14 mm."
Structure
Engineering documents follow predictable structures because readers need to find information quickly. An engineer reviewing a test report at 2 AM during an integration crisis does not want a narrative -- they want the result in a predictable location.
Audience Awareness
The same technical result is communicated differently to different audiences:
| Audience | What they need | How to write |
|---|
| Fellow engineers | Full technical detail, assumptions, limitations | Formal, precise, equations and data tables |
| Management | Summary, implications, decisions needed | Executive summary, key findings, recommendations |
| Regulators | Compliance evidence, traceability |
