Guide

Prompt Quality Checklist for Research Prompts

A review checklist for research plans, interview guides, source synthesis and insight extraction.

Practical method

A review checklist for research plans, interview guides, source synthesis and insight extraction. The goal is not to make prompts longer. The goal is to make the request clearer, easier to verify and more useful in a real workflow.

A good prompt usually includes role, task, context, constraints, examples, output format and a review loop.

Step-by-step process

  1. Write the real task in plain language.
  2. Add context: audience, constraints, examples and unavailable details.
  3. Ask for a first draft and missing-information questions.
  4. Request a critique against your goal.
  5. Revise the prompt and save the version that worked.

Productivity Prompts Context Builder

Best for: teams working on prioritization, checklists, weekly reviews and personal systems in general work

Act as a senior productivity specialist. You are helping a team in general work create a priority plan. First, restate the goal in one sentence. Use this context: [context]. Audience: [audience]. Constraints: [constraints]. Brand or communication tone: [tone]. Your task is to collect missing context before trying to create a priority plan. Return a usable priority plan plus rationale, checklist and next step. Include: 1) a ready-to-use draft, 2) a short rationale, 3) a review checklist, and 4) three missing-information questions if the context is incomplete. Do not invent facts, prices, policies or results that are not provided.
[goal][audience][context][constraints][tone][output format]

Example input: Goal: create a priority plan; scenario: too many tasks, unclear next action and low follow-through; deliverable needed: priority plan; constraint: keep it specific and reviewable.

Expected output: priority plan with a clear structure, one example, and a review checklist

Productivity Prompts First Draft

Best for: teams working on prioritization, checklists, weekly reviews and personal systems in general work

Act as a senior productivity specialist. You are helping a team in general work create a priority plan. First, restate the goal in one sentence. Use this context: [context]. Audience: [audience]. Constraints: [constraints]. Brand or communication tone: [tone]. Your task is to produce a usable priority plan for team. Return a usable priority plan plus rationale, checklist and next step. Include: 1) a ready-to-use draft, 2) a short rationale, 3) a review checklist, and 4) three missing-information questions if the context is incomplete. Do not invent facts, prices, policies or results that are not provided.
[goal][audience][context][constraints][tone][output format]

Example input: Goal: create a priority plan; scenario: too many tasks, unclear next action and low follow-through; deliverable needed: weekly review; constraint: keep it specific and reviewable.

Expected output: weekly review with a clear structure, one example, and a review checklist

Productivity Prompts Critique and Improve

Best for: teams working on prioritization, checklists, weekly reviews and personal systems in general work

Act as a senior productivity specialist. You are helping a team in general work create a priority plan. First, restate the goal in one sentence. Use this context: [context]. Audience: [audience]. Constraints: [constraints]. Brand or communication tone: [tone]. Your task is to audit the weekly review against the real goal and constraints. Return a usable priority plan plus rationale, checklist and next step. Include: 1) a ready-to-use draft, 2) a short rationale, 3) a review checklist, and 4) three missing-information questions if the context is incomplete. Do not invent facts, prices, policies or results that are not provided.
[goal][audience][context][constraints][tone][output format]

Example input: Goal: create a priority plan; scenario: too many tasks, unclear next action and low follow-through; deliverable needed: checklist; constraint: keep it specific and reviewable.

Expected output: checklist with a clear structure, one example, and a review checklist

Common mistakes

  • Using a one-line request like “write something about productivity” with no audience or constraints.
  • Asking for the final answer before collecting the context the AI needs.
  • Publishing output without checking facts, dates, product details or policy-sensitive claims.
  • Requesting many versions without defining what “good” means.
  • Letting the AI decide the structure when the page, email or report already has a known format.

Review checklist

  • The prompt states the user role and business context.
  • The output format is explicit enough to review quickly.
  • The prompt asks for missing-information questions instead of invented details.
  • The answer includes a checklist or next step, not only a paragraph.
  • Claims, numbers, policies and examples are checked before use.

FAQ

What is the fastest way to improve a prompt?

Add specific context, output format and success criteria.

Should prompts be very long?

Not always. A prompt should be complete enough to guide the output, but not padded with irrelevant words.

How do I know the result is good?

Compare it against the original goal, check facts and ask whether a real user can act on it.

Editorial quality

Score: 90/100

Robots: index,follow

Guide page with method, examples, mistakes and review checklist.