| name | tech-writing |
| description | Use when writing strategic tech posts, engineering narratives, opinion pieces, or industry analysis. |
| allowed-tools | Read,Write,Edit,Bash,Glob,Grep,WebSearch,WebFetch |
Tech Writing
Use for strategic technology writing: blog posts, opinion pieces, engineering narratives, and longer industry analysis. Every sentence needs a job.
Choose the Format
Short form, 800-1,500 words, is the default. Long form, 2,000-4,000 words, is only for arguments that genuinely need scenarios, history, architecture, or several distinct implications.
Drafting Standard
State the thesis early, use specific evidence, develop only the points the thesis requires, cut repeated sections and generic examples, and end with a concrete implication.
Voice
Be opinionated, specific, concise, and technically grounded. Prefer named systems, concrete incidents, numbers, and tradeoffs over generic industry language.
Edit Checks
- Does the opening state the claim within three sentences?
- Does every paragraph add new information or insight?
- Could any section be merged with a prior section?
- Is every example specific enough that not anyone could have written it?
- Did you cut at least 30% from the first draft when polishing?
- If LLM-assisted, did you audit
../copy-editing/references/avoid-ai-writing.md?
References
Load Radar examples, historical parallels, scenario planning, or the copy-editing AI-writing audit only when the task needs that depth.
