Ask for a review. Keep your judgment.
Give AI a bounded task, then verify the suggestions before changing your document.
Read the descriptive transcript
Follow the complete narration and the changes shown in the video. Each example can be copied.
1. What does the note actually say?
This note says we will update the guide. It does not say who will do it, or when. Let's write an AI review request that keeps those unknowns visible.
Source shown
## Goal
Find unclear actions.
## Context
We will update the guide.On screen
The document stays visible while the narration explains the idea.
2. 01 / State the task and supply context
The Goal asks for unclear actions. Context contains the note itself. These headings help separate the task from the material being reviewed.
Source shown
## Goal
Find unclear actions.
## Context
We will update the guide.On screen
The document stays visible while the narration explains the idea.
3. 02 / Set a boundary
Add a Constraints heading. Tell the reviewer not to invent names or dates, and to review only. The request should not silently authorize changes.
Source shown
## Goal
Find unclear actions.
## Context
We will update the guide.
## Constraints
Do not invent names or dates.
Review only.On screen
The cursor moves to the edit point. Each character is inserted or removed in the source, and the preview updates from that text.
4. 03 / Ask for an inspectable response
Add an Output heading and ask for a quotation and a question. That gives you something concrete to compare with the original.
Source shown
## Goal
Find unclear actions.
## Context
We will update the guide.
## Constraints
Do not invent names or dates.
Review only.
## Output
Quote and ask a question.On screen
The cursor moves to the edit point. Each character is inserted or removed in the source, and the preview updates from that text.
5. Read the material before sending it
Before using an AI provider, inspect the text you intend to send. This lesson only builds the request; it does not contact a model or transmit the note.
Source shown
## Goal
Find unclear actions.
## Context
We will update the guide.
## Constraints
Do not invent names or dates.
Review only.
## Output
Quote and ask a question.On screen
The document stays visible while the narration explains the idea.
6. Teaching example / An unsupported answer
Imagine a response saying Mira will update the guide on Friday. Neither Mira nor Friday appears in our context. Fluency does not make those details true.
Source shown
## Goal
Find unclear actions.
## Context
We will update the guide.
## Constraints
Do not invent names or dates.
Review only.
## Output
Quote and ask a question.On screen
Unsupported: Mira will update the guide on Friday.
7. Ask for the missing facts
A better review would quote the action and ask who owns it, and when it is due. Ask the relevant person instead of filling the gap with a guess.
Source shown
## Goal
Find unclear actions.
## Context
We will update the guide.
## Constraints
Do not invent names or dates.
Review only.
## Output
Quote and ask a question.On screen
Ask: Who owns this action, and when is it due?
8. Structure is different from verification
Checking for four headings only checks structure. An AI review can suggest concerns. Verification requires the relevant evidence or person.
Source shown
## Goal
Find unclear actions.
## Context
We will update the guide.
## Constraints
Do not invent names or dates.
Review only.
## Output
Quote and ask a question.On screen
Structure → review → verification
9. Your turn / Write a bounded request
Pause and write your own Goal, Context, Constraints, and Output below the video. Keep the task narrow enough that you can judge the response.
Source shown
## Goal
Find unclear actions.
## Context
We will update the guide.
## Constraints
Do not invent names or dates.
Review only.
## Output
Quote and ask a question.On screen
The document stays visible while the narration explains the idea.
10. You decide what belongs in the document
Compare any suggestions with your source. Accept useful changes, reject unsupported claims, and preserve the meaning you intended.
Source shown
## Goal
Find unclear actions.
## Context
We will update the guide.
## Constraints
Do not invent names or dates.
Review only.
## Output
Quote and ask a question.On screen
The document stays visible while the narration explains the idea.
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.
## 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, then follow your first AI request 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.
YOUR TURN
Make the idea your own.
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.
Readable result
Goal
Review these meeting notes.
Compare with one possible answer
## 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; do not change the note.
## Output
Quote each unclear passage and suggest a question to resolve it.This is one approach. Your writing can differ while meeting the same structural goal.
TAKE IT WITH YOU
AI can suggest a change. You check its evidence, meaning and scope before accepting it.
Read the editor guide →Progress is stored in this browser. Your practice text is not saved.