---
title: "Ask for a review. Keep your judgment."
description: "Give AI a bounded task, then verify the suggestions before changing your document."
canonical: https://editmd.app/learn/lessons/review/
markdown: https://editmd.app/learn/lessons/review.md
status: pre-release, waiting list open
generated: editmd-website
---

# Ask for a review. Keep your judgment.

Lesson 06 of 12 in Markdown School. Give AI a bounded task, then verify the suggestions before changing your document.

## Give the request a shape

An AI review is easier to assess when you state the task, supply the relevant material and describe the result you need. Markdown headings are one way to separate these parts. Clear instructions, context and examples are common prompting guidance; headings alone do not guarantee a correct answer. [Anthropic’s prompting guidance](https://platform.claude.com/docs/en/build-with-claude/prompt-engineering/claude-prompting-best-practices).

```markdown
## Goal

Find unclear actions in these meeting notes.

## Context

We agreed to update the guide.

## Constraints

Do not invent an owner or date. Review only.

## Output

Quote each unclear passage and suggest a question.
```

## Review a suggestion against the source

The note above does not name an owner or deadline. A suggestion such as “Mira will update the guide on Friday” adds facts that are absent. A useful response would ask who owns the action and when it is due. Keep the uncertainty visible until someone can resolve it.

This is a teaching example, not a live model response. No text from the practice area is sent to an AI provider.

## Separate three different checks

| Check        | What it can tell you                                     | What it cannot establish                        |
| ------------ | -------------------------------------------------------- | ----------------------------------------------- |
| Structure    | The expected headings or markers are present             | Whether a statement is true                     |
| AI review    | Possible ambiguity, contradictions or improvements       | That every finding is correct or complete       |
| Verification | What the relevant source, calculation or person supports | An automatic guarantee about the whole document |

## Keep scope and control visible

Read the material you plan to send. With a hosted provider, understand which text goes to that provider. A local model has different setup requirements. In editmd, [connect your chosen provider](/docs/ai-setup/), then follow [your first AI request](/docs/ai-use/) to inspect scope and review the result. editmd’s own Review action reads the document you have open and shows exactly what will be sent before you confirm; a written request like the one above suits a tool that takes a typed prompt, such as a chat assistant or editmd’s Custom instruction.

A revision should preserve your intended meaning. Accept useful changes, reject unsupported ones and save deliberately. The practice task below only checks the structure of your review request; your judgment remains part of the work.

## Exercise

Write a review request with ## Goal, ## Context, ## Constraints and ## Output. Include the note, limit the task and say how findings should be returned. This exercise makes no AI request.

## Takeaway

AI can suggest a change. You check its evidence, meaning and scope before accepting it.

Related guide: https://editmd.app/docs/ai-use/. All lessons: https://editmd.app/learn.md