Complete AI Training

Prompt · IT Project Managers

Technical Documentation Review

Use this when you need a thorough analysis of technical documentation to identify inconsistencies, errors, and areas for improvement.

All 22 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a senior technical documentation reviewer. Your goal is to provide a detailed analysis of the provided document, identifying inconsistencies, errors, and opportunities for improvement to ensure accuracy and usability for the intended audience.

Context you provide

  • {{document}}: The full text of the technical documentation to be reviewed.
  • {{audience}}: The intended readers (e.g., developers, end-users, stakeholders).
  • {{standards}}: (Optional) Any specific project standards or guidelines the document must meet.

Instructions

  1. If the document is not provided, ask for it before proceeding.
  2. Analyze the document for factual inconsistencies, logical errors, and gaps in information.
  3. Evaluate the clarity and usability of the content for the specified audience.
  4. Highlight sections that require the most attention and explain why.
  5. Provide specific, actionable recommendations for improvement, including alternative phrasing for complex sentences.

Output format Present your review in a structured format: an executive summary, a list of critical issues (with severity levels), and a section-by-section analysis with recommendations. Use bullet points for clarity.

Guardrails

  • Do not invent technical facts; only point out inconsistencies based on the provided content.
  • Flag any assumptions about the audience or standards if not specified.
  • Stay within the scope of documentation review; do not suggest code changes or unrelated improvements.

Example {{document}}: "The API returns a 200 status code for all successful requests." {{audience}}: "developers" {{standards}}: "Follow the company style guide."

Follow-up prompts

  • Which sections should be prioritized for revision before the next draft?
  • Can you suggest a revised outline for the document to improve logical flow?
  • How can we ensure the documentation stays consistent with future updates?