Writing Simplified Technical English

by PostHog469d1773e9cbNo licenseListed Oct 8, 2026Updated Oct 8, 2026

Write English that a reader cannot misread: one meaning per word, active voice, simple tenses, one idea per sentence, short sentences. Based on ASD-STE100 (Simplified Technical English), the controlled-language standard written for aircraft maintenance manuals. Use it for any prose an agent produces that someone else acts on. That covers reports and findings, PR descriptions and commit messages, instructions handed to another agent, tool descriptions, error messages, status summaries, and prompts. Also use it on request, with triggers like "simplify this", "make this readable", "too dense", "rewrite in STE", "simplified technical english", "ASD-STE100".

Instructions onlyWriting & Content
AI-generated overview

Applies ASD-STE100 simplified technical English rules to make agent-written prose unambiguous and actionable.

What it does
Provides a rule set for writing clear English: one meaning per word, active voice, simple tenses, one idea per sentence, and short sentences. It includes a rewrite procedure, a self-check list, and reference files with detailed rules and worked before-and-after examples. It is applied while writing rather than as a cleanup pass afterward.
When to use it
Use it for prose that a person or another agent must act on, such as reports, findings, PR descriptions, commit messages, instructions, tool descriptions, error messages, and prompts. It is also used on request with triggers like "simplify this" or "rewrite in STE". It is not meant for persuasive or voice-driven writing such as marketing copy or blog posts.
Requirements
No scripts or tools; it is instructions only. It references two bundled markdown files for detailed rules and examples.

Writing simplified technical English

ASD-STE100 is a controlled-language standard. The aerospace and defense industry wrote it so that a technician cannot misread a maintenance instruction. It removes the two biggest sources of misreading: words that carry more than one meaning, and sentences that support more than one structure.

The same discipline fixes the usual failure of agent-written prose. Agent output is often correct and unreadable: long sentences, stacked hedges, passive voice, and a synonym rotation that makes one action look like three. The reader has no author to ask, so ambiguity costs them a re-read at best and a wrong action at worst.

Apply the rules below as you write. Do not write a dense draft and clean it up afterward.

When to use this

Use it for text that a person or another agent must act on:

  • Reports, findings, and summaries.
  • PR descriptions, commit messages, and code comments.
  • Instructions passed to another agent, and prompts.
  • Tool descriptions, error messages, empty states, and log lines.

Do not use it where voice is the point: marketing copy, blog posts, or anything persuasive. STE is deliberately flat. Also leave quoted text alone. If you quote a user, a log, or a document, quote it as it is.

The rules

RuleDoDo not
One meaning per wordPick one verb per action and reuse it every timeRotate "check", "verify", and "confirm" for the same action
One part of speech per word"Apply oil to the valve""Oil the valve"
Active voice"The worker deletes the file.""The file is deleted."
Simple tenses"We received the report.""We have received the report."
One idea per sentence"Open the file. Read line 3.""Open the file and read line 3, then check it matches."
Sentence length20 words or fewer for instructions, 25 or fewer for descriptionsChains of subordinate clauses
Noun clusters3 words or fewer ("fuel pump valve")"high pressure fuel pump inlet valve assembly"
No missing wordsKeep the subject, the verb, and the article, even if it reads longer"Files not backed up will be lost", which hides which files
One hedge, at most"The client version is probably out of date.""An error may have occurred which could be caused by..."
ParagraphsOne topic, 6 sentences or fewerMulti-topic paragraphs
ListsUse a list for 3 or more steps or conditionsA sequence buried in one sentence
JargonKeep the technical term you need, and define it onceUse an internal name the reader has never seen

PostHog house style sits on top of these rules and wins where the two disagree. We use American English, sentence case, and the Oxford comma. We do not use the em-dash.

How to rewrite

  1. Read the text once for meaning. Do not start rewriting before you know what it must still say.
  2. Go sentence by sentence. Name the rule each sentence breaks.
  3. Rewrite the sentence to fix that break. Keep every fact, number, condition, and qualifier.
  4. Check the result against the rules again. A rewrite often introduces a new long sentence.

Precision beats brevity. If a shorter sentence would drop a safety condition, a scope qualifier, or a number, keep the longer sentence and say why.

If the text already follows the rules, say so. Do not change compliant text.

Self-check

Before you send the text, read it once and ask:

  • Does any sentence run past 25 words?
  • Does any sentence carry two instructions?
  • Does the same action appear under two different verbs?
  • Can a passive sentence name its actor?
  • Would a reader who joins here, with no context, know what to do next?

References

  • references/writing-rules.md: the detail behind the table, plus sources.
  • references/before-after.md: worked examples of the rewrite, including agent output.

Source and attribution

Source:PostHog/ai-plugininskills/writing-simplified-technical-englishat commit469d177

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

More from PostHog/ai-plugin

Working With Task Comments

PostHog

Reads and interprets comments on PostHog tasks, artifacts, and canvases through the PostHog MCP exec dispatcher.

Productivity & WorkflowOct 8, 2026

Working With Skills

PostHog

Guides agents in using PostHog's skill-* MCP tools to discover, read, create, update, and refactor skills.

AI & AgentsOct 8, 2026

Working With Scouts

PostHog

Operating manual for delegating watching jobs to PostHog Signals scouts, acting on their reports, and steering the fleet over time.

AI & AgentsOct 8, 2026

Validating And Publishing Canvases

PostHog

Validate and publish a canvas source project safely: the source-project shape, declared capabilities, reading the current version pointer, iterating on validation diagnostics, guarded publishing with expected_current_version_id, staging a draft build and promoting it, waiting out the queued build, and recovering from a 409 version_conflict or a 429 capacity limit without overwriting concurrent work. Use whenever a canvas edit is ready to save, a draft build is wanted, a canvas publish or build returns diagnostics or a conflict, or a task needs to understand canvas version history.

Awaiting classificationOct 8, 2026

Understanding Billing Usage

PostHog

Explains PostHog billing usage and spend from the customer's visible Billing MCP tools. Use when the user asks why usage or spend is high, which product or project is driving usage, what a usage type means, how to reduce usage, what changed over time, why they got a usage change alert, or whether a spike/drop alert was real or noisy. Also use before product-specific analytics skills when the user names a billable PostHog product metric such as events, recordings, feature flag requests, exceptions, survey responses, synced rows, logs, AI events, AI credits, or Inbox credits. Starts from Billing usage/spend tools, then routes to customer-visible product MCP surfaces for deeper investigation.

Awaiting classificationOct 8, 2026

Turning Engineering Analytics Into Insights

PostHog

Turns engineering analytics data into saved PostHog SQL insights, dashboards and subscriptions, with HogQL guidance.

Data & AnalyticsOct 8, 2026