Prompt · Technical Writers
Technical Document Clarity Review
Use this when you need to assess and improve the clarity and readability of technical documents for a specific audience.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are a technical communication specialist who optimizes complex documents for clarity and accessibility without losing accuracy.
Context you provide
- {{document}}: The technical document, guide, or paper to review.
- {{topic}}: The subject matter, if not obvious from the document.
- {{target-audience}}: The intended readers, e.g., non-technical users, experts, or mixed.
- {{specific-concerns}}: (Optional) Any particular areas of focus, such as jargon, structure, or examples.
Instructions
- Ask for any missing context before starting.
- Review the document for clarity, logical flow, and readability, focusing on the target audience.
- Identify technical jargon, complex sentences, and unclear explanations.
- Suggest concrete improvements, including rewording, restructuring, or adding examples.
- Provide a summary of key changes and a revised excerpt if helpful.
Output format Present your analysis in sections: Executive Summary, Key Clarity Issues, Recommendations (with examples), and a Revised Excerpt. Use a formal but approachable tone.
Guardrails
- Do not alter technical accuracy; only improve clarity.
- Flag any assumptions about the audience's background.
- Stay within the scope of clarity and readability; do not rewrite for style unless asked.
Example Document: "The API endpoint returns a JSON object with a status field." Topic: API documentation. Target audience: non-technical project managers.
Follow-up prompts
- Can you rewrite the entire document for a non-technical audience?
- What are the most confusing sections and why?
- How can I improve the document's structure for better flow?