---
name: simplified-technical-english-codex
description: Write or review executable technical content using a practical subset of ASD-STE100 Simplified Technical English. Use for runbooks, deployment instructions, implementation handoffs, completion briefs, README operations sections, error messages, and UI microcopy. Do not use for stakeholder emails, call packs, persuasive writing, or rationale and trade-off sections that need audience-specific language.
---

# Simplified Technical English

Write technical content that a reader can execute without ambiguity. Apply the rules below as mechanical constraints, not as a claim of full ASD-STE100 certification.

## Preserve the source meaning

- Keep every requirement, condition, warning, command, path, identifier, and expected result.
- Do not invent missing steps or technical facts.
- Flag a missing prerequisite or ambiguous instruction instead of guessing.
- Keep established project terms when changing them would alter meaning.
- Preserve code, commands, URLs, file paths, schema names, and quoted user text exactly unless the task requires changes.

## Control the structure

- Put one topic in each paragraph.
- Use no more than six sentences in a paragraph.
- Keep procedural sentences at 20 words or fewer.
- Keep descriptive sentences at 25 words or fewer.
- Put one instruction in each sentence.
- Put a warning or caution before the step it protects.
- Format a procedure as ordered steps when sequence matters.

## Control the sentences

- Write instructions in the imperative: `Remove the lock file.`
- Use active voice.
- Name the actor when the actor is not the reader.
- Use simple past, present, or future tense.
- Replace a gerund phrase with a finite verb when this improves clarity.
- State conditions explicitly with `if`, `when`, or `unless`.

## Control the words

- Use one word for one meaning throughout the document.
- Use one name for each component, file, state, and action.
- Choose one verb for each repeated action. Do not rotate among `check`, `verify`, `validate`, and `confirm`.
- Use an article before a singular count noun when English requires one.
- Prefer a short common word: `use`, `start`, `stop`, `make`, or `do`.
- Remove fillers and hedges such as `simply`, `just`, `basically`, `as needed`, and `should probably`.
- Replace vague pronouns such as `it`, `this`, or `that` when the reference is unclear.
- Replace vague timing such as `soon` or `periodically` with an exact condition or interval when the source provides one.

## Draft or revise the document

1. Identify the reader, action, prerequisites, and expected result.
2. Separate procedures from explanation.
3. Put prerequisites and warnings before the protected procedure.
4. Rewrite each procedure as imperative, single-action steps.
5. Use consistent nouns and verbs.
6. Split sentences that exceed the applicable word limit.
7. Check that the revision preserves the source meaning.
8. Report unresolved ambiguity separately from the rewritten text.

## Review an existing document

Check each item:

1. Split any procedural sentence longer than 20 words.
2. Split any descriptive sentence longer than 25 words.
3. Rewrite passive instructions in the imperative.
4. Separate sentences that contain more than one instruction.
5. Move each warning before its protected step.
6. Unify different names for the same action or object.
7. Remove filler words and unsupported hedges.
8. Confirm that commands and technical identifiers remain exact.

When the user requests a review, cite each issue by location and propose corrected text. Do not rewrite the entire document unless requested.

## Apply the scope boundary

Do not flatten persuasive or relationship-sensitive writing into procedural language. For stakeholder emails and call packs, preserve the audience's vocabulary, tone, and decision context.

This skill adopts a practical subset of ASD-STE100 principles. Full certification requires the official controlled dictionary and the complete standard.