Skip to guide
The Use Case Shed

The Use Case Shed Beginner guide

Turn loose notes into a clear checklist.

Give a text-chat tool your notes and ask it to pull out the next actions.

Workflow tested in Codex

What you will make

A short checklist showing each action, its owner, and its due date.

01 / Get ready

Before you start

  • A text-chat tool you already have. Availability and limits depend on your account; sign in if your tool requires it.
  • A few sentences of notes. Start with the invented picnic example below before using your own.
  • The original notes beside you so you can check the result.

Safe sample: planning a community picnic

Community picnic: Maya will bring paper plates. Ask the park office whether we can use the covered tables. I need to send the headcount to Lee by Thursday. Maybe borrow a cooler from Sam? We have not agreed on that. No one has volunteered to bring drinks.

These notes are invented. For your own attempt, remove private details you do not have permission to share.

02 / Give it a go

Try the workflow

  1. Open a new text chat.

    Use a tool you already have access to. No file upload or connection to another app is needed for this example.

  2. Send the complete prompt below.

    It includes the sample notes, the requested format, and a rule for missing information.

  3. Compare the answer with the notes.

    Look for three confirmed actions, a tentative cooler idea, and an unassigned drinks task. The wording can differ; the facts should agree.

  4. Try your own short notes.

    Replace only the text after “Notes:” in the prompt. Keep the other instructions, then compare the checklist with your notes.

The complete prompt

Original prompt by Use Case Shed. Copy the complete text to try the recorded example.

Turn the notes below into a short checklist. Use only information in the notes. For each task show the action, owner and due date. Write “not stated” for an owner or date that is missing. Keep tentative suggestions separate from confirmed tasks. Do not invent facts or turn a question into a commitment.

Notes: Community picnic: Maya will bring paper plates. Ask the park office whether we can use the covered tables. I need to send the headcount to Lee by Thursday. Maybe borrow a cooler from Sam? We have not agreed on that. No one has volunteered to bring drinks.

03 / Make a correction

If the result goes wrong

It invented a date, owner, or commitment.

Ask it to compare the list with the original notes. Check the revision yourself; if a detail is still unsupported, correct it directly or leave it as “not stated.”

A follow-up prompt to try

Suggested correction prompt. This follow-up was not part of the recorded trial.

Review your checklist against the original notes. For every owner, date, and commitment, point to the wording that supports it. Replace unsupported owners or dates with “not stated.” Keep tentative ideas separate and list unassigned tasks without inventing an owner. Show the corrected checklist.

04 / Behind this guide

Sources and evidence

The explanations, sample, and prompts are original work by Use Case Shed. The references below support the method.

  • OpenAI: Prompting

    Supporting reference for giving a desired result, source material, output format, and boundaries, including how to flag missing details.

  • OpenAI: Use ChatGPT

    Supporting reference for checking names, numbers, dates, and assumptions against the original material.

  • OpenAI: Quickstart

    Supporting reference for account sign-in when using ChatGPT.

What we tested

One workflow run in Codex used the exact prompt and invented notes shown above. The result kept the three confirmed actions, tentative cooler idea, and unassigned drinks separate. The exact model identifier was not exposed.

The ChatGPT interface and beginner usability have not been tested. A successful sample does not guarantee the same result for different notes or tools.

Workflow evidence and supporting sources checked .