Review Prompt
Use this skill to turn vague instructions into clear, testable LLM instructions.
4-D Framework
- Destination: What result should the model produce?
- Definition: What makes the result successful and usable?
- Doubt: What evidence, citations, uncertainty handling, or source limits are required?
- Done: When should the model stop working and deliver the answer?
Workflow (step-by-step)
- Read the user's current prompt and infer task, audience, constraints, and output shape.
- Identify the highest-risk gap across Destination, Definition, Doubt, and Done.
- Ask exactly one question about that gap.
- Include a recommended default answer the user can accept, edit, or reject.
- After the user answers, repeat steps 2-4 until the instructions are clear enough to draft safely.
- When the remaining gaps are minor, stop interviewing and produce the revised instructions.
Use this question format:
Question: [one focused question]
Recommended answer: [specific default, written as if it could be inserted into the prompt]
Interview Rules (reliability)
- Walk decision branches in dependency order: Destination first, then Definition, then Doubt, then Done, unless another gap is clearly blocking.
- Prefer precise defaults over broad menus. If multiple options are plausible, recommend one default and briefly note tradeoffs.
- Do not ask compound questions. Split multi-part uncertainty into separate turns.
- Do not over-interview. If a reasonable default would not change the final prompt materially, choose it and move on.
- Preserve the user's intent, voice, domain, and constraints. Improve clarity without changing the underlying ask.
- For factual, legal, medical, financial, or research instructions, make Doubt explicit with source, citation, recency, and uncertainty rules.
Revision Template
When ready, provide this output:
## Revised Prompt
[Prompt text with clear Destination, Definition, Doubt, and Done.]
## What Changed
- Destination: [brief note]
- Definition: [brief note]
- Doubt: [brief note]
- Done: [brief note]
If the user asks only for the final prompt:
- the
Revised Prompt should NOT include the text: Destination, Definition, Doubt, and Done.
- omit
What Changed.
Pattern Cues (Weak -> Strong)
- Destination (weak -> strong): "Summarize this meeting transcript." -> "Turn this meeting transcript into a follow-up email I can send to the customer."
- Definition (weak -> strong): "Rewrite this email." -> "Rewrite this email so it is clear, calm, and direct; keep facts unchanged, under 200 words, and place the ask in the first three sentences."
- Doubt (weak -> strong): "Do not make things up." -> "After every factual claim, cite the source inline, e.g.,
[Source: report, p. 4]."
- Done (weak -> strong): "Cover every angle." -> "When the output meets the checklist, provide the final version."
Weak combined instructions:
Act as a world-class business strategist.
- First, read the following transcript.
- Identify all key themes.
- Extract action items.
- Write a client email.
- Make sure the tone is friendly and professional.
- Double-check everything.
- Make a table.
- Finally, give me a recommendation. Be concise and detailed.
Strong combined instructions:
Turn this transcript into a client-ready follow-up email. Success means the email clearly states what was decided, what is still open, and the next action for each person. Use only decisions directly supported by the transcript. Put unclear items under Open Questions. When the checklist is met, provide the final email.
1---2name: review-prompt3description: Reviews and rewrites prompt/"llm instructions" drafts using the 4-D framework (Destination, Definition, Doubt, Done). Use when the user asks to review, improve, debug, sharpen, stress-test, or rewrite the prompt.4---56# Review Prompt78Use this skill to turn vague instructions into clear, testable LLM instructions.910## 4-D Framework1112- Destination: What result should the model produce?13- Definition: What makes the result successful and usable?14- Doubt: What evidence, citations, uncertainty handling, or source limits are required?15- Done: When should the model stop working and deliver the answer?1617## Workflow (step-by-step)18191. Read the user's current prompt and infer task, audience, constraints, and output shape.202. Identify the highest-risk gap across Destination, Definition, Doubt, and Done.213. Ask exactly one question about that gap.224. Include a recommended default answer the user can accept, edit, or reject.235. After the user answers, repeat steps 2-4 until the instructions are clear enough to draft safely.246. When the remaining gaps are minor, stop interviewing and produce the revised instructions.2526Use this question format:2728```markdown29Question: [one focused question]3031Recommended answer: [specific default, written as if it could be inserted into the prompt]32```3334## Interview Rules (reliability)3536- Walk decision branches in dependency order: Destination first, then Definition, then Doubt, then Done, unless another gap is clearly blocking.37- Prefer precise defaults over broad menus. If multiple options are plausible, recommend one default and briefly note tradeoffs.38- Do not ask compound questions. Split multi-part uncertainty into separate turns.39- Do not over-interview. If a reasonable default would not change the final prompt materially, choose it and move on.40- Preserve the user's intent, voice, domain, and constraints. Improve clarity without changing the underlying ask.41- For factual, legal, medical, financial, or research instructions, make Doubt explicit with source, citation, recency, and uncertainty rules.4243## Revision Template4445When ready, provide this output:4647```markdown48## Revised Prompt4950[Prompt text with clear Destination, Definition, Doubt, and Done.]5152## What Changed5354- Destination: [brief note]55- Definition: [brief note]56- Doubt: [brief note]57- Done: [brief note]58```5960If the user asks only for the final prompt:61- the `Revised Prompt` should **NOT** include the text: Destination, Definition, Doubt, and Done.62- omit `What Changed`.6364## Pattern Cues (Weak -> Strong)6566- Destination (weak -> strong): "Summarize this meeting transcript." -> "Turn this meeting transcript into a follow-up email I can send to the customer."67- Definition (weak -> strong): "Rewrite this email." -> "Rewrite this email so it is clear, calm, and direct; keep facts unchanged, under 200 words, and place the ask in the first three sentences."68- Doubt (weak -> strong): "Do not make things up." -> "After every factual claim, cite the source inline, e.g., `[Source: report, p. 4]`."69- Done (weak -> strong): "Cover every angle." -> "When the output meets the checklist, provide the final version."7071**Weak combined instructions:**7273```markdown74Act as a world-class business strategist.75- First, read the following transcript. 76- Identify all key themes.77- Extract action items. 78- Write a client email.79- Make sure the tone is friendly and professional.80- Double-check everything.81- Make a table.82- Finally, give me a recommendation. Be concise and detailed.83```8485**Strong combined instructions:**8687```markdown88Turn this transcript into a client-ready follow-up email. Success means the email clearly states what was decided, what is still open, and the next action for each person. Use only decisions directly supported by the transcript. Put unclear items under Open Questions. When the checklist is met, provide the final email.89```