Think & decide

Turn a vague request into a clear brief

Expose missing decisions, constraints, and success criteria before work begins

4 min setupTested with:ChatGPTClaudeGeminiReviewed: 2026-08-27

Add your context

Your text stays in this browser. AILesson Prompts does not send it to a model or server.

The original requestKnown context

Your prompt

Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt

Turn the request below into a clear, executable brief.

Original request:
[request]

Known context:
[context]

Do not invent missing facts. Separate confirmed information from assumptions. Produce:
1. Objective
2. Target audience or user
3. Required deliverable
4. Constraints and non-goals
5. Success criteria
6. Decisions already made
7. The five highest-priority questions that must still be answered

End with a one-sentence definition of done.

Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.

From input to outcome

A worked example

See how concrete context turns this recipe into a usable result

Actual input

The original request: We need a better onboarding experience for the volunteer scheduling portal before the autumn intake.
Known context: The portal is used by new volunteers at a community food bank. The operations team can edit emails and help content but cannot change the account-creation flow this quarter. The autumn intake begins on 15 September. Support logs show that new volunteers often ask where to find their first shift, but no baseline completion data has been collected. One designer and one operations coordinator are available for two weeks.

Example output

1. Objective

Help newly registered food-bank volunteers find and understand their first scheduled shift before the autumn intake begins.

2. Target user

Confirmed: new volunteers using the scheduling portal. Assumption requiring validation: volunteers who contact support represent the broader onboarding audience.

3. Required deliverable

A reviewable onboarding improvement package that the operations team can implement within two weeks, covering editable emails and help content. The exact formats and number of assets are not yet confirmed.

4. Constraints and non-goals

Deadline: ready before 15 September.
Capacity: one designer and one operations coordinator for two weeks.
Changes are limited to emails and help content.
Account-creation changes and a full portal redesign are out of scope.

5. Success criteria

Reduce confusion about finding the first shift. A measurable target and baseline are still missing; the team must choose a proxy such as related support requests or successful first-shift discovery.

6. Decisions already made

Target the autumn intake, use existing editable communication surfaces, and exclude account-creation changes.

7. Highest-priority questions

Which email and help pages can be changed?
What path should volunteers follow to find a first shift?
Which support-log examples reveal the main confusion?
What metric and baseline will define improvement?
Who approves and publishes the final content?

Definition of done: The agreed email and help-content changes are approved, published before 15 September, and paired with a defined measure for first-shift discovery.