Your choice also saves this guide’s current worked-example checkmarks. Only this browser; no account or sync. View saved guides
Saving needs JavaScript. Reading and downloading this guide does not save it.
Make a start
One step at a time.
3 steps
Start with the synthetic worked example or other non-sensitive inputs. Run one prompt at a time in your chosen AI tool. Replace any bracketed placeholders with the requested material, check each reply, and supply the source or earlier outputs that step needs. Paste them again if the tool lacks that context.
Start with the synthetic example, then adapt each prompt to your task.
01
Open a chat and use the complete sample
Open https://chatgpt.com. If you have access, choose New chat. Copy all the instructions below (the prompt), including the SAMPLE INPUT, into the message box and send it. You do not need to upload a file. You should see four glossary entries with examples and a warning about each likely misunderstanding. The wording can differ from the worked example, but the facts and constraints must agree. If you cannot access this service, use another text assistant available to you; account requirements and limits may differ.
Your starting prompt
Create a four-term beginner glossary using the team definitions. Use the supplied requests in examples where relevant. Clearly label any invented example scenario as hypothetical. Use only the supplied facts; mark missing information rather than inventing it. Return written text only. Do not send, publish or change anything in another service.
SAMPLE INPUT
Made-up example for practice. All people, organizations, records and product behavior below are fictional.
Source definitions for the fictional Moss team: backlog = requests recorded but not yet selected for work; triage = deciding the right queue and urgency for a request, not solving it; owner = person responsible for coordinating the next step, not necessarily doing all work; blocked = cannot take the next planned step because a named dependency is unresolved. Example facts: R12 is in the backlog. R13 is awaiting a logo file from the design team and its owner is Ivo. Format: term, plain explanation, example, common misunderstanding. Do not treat these as universal industry definitions.
02
Compare, correct and save
Compare the answer with the complete sample input and the checks below. All four supplied terms appear, with their team-specific meaning preserved. If a fact is missing, changed or invented, paste the correction prompt below into the same chat. Read the revised result again; if it still fails, correct the text yourself before using it. Copy the reviewed result into a new note or text document. Keep real publication, decisions and sending for a separate human review.
Your starting prompt
Check your previous answer against the SAMPLE INPUT in my first message. Test each point below. For a failure, show the problem and then return a complete corrected answer; for a missing source fact, keep it explicitly unknown. Do not invent a successful check.
- All four supplied terms appear, with their team-specific meaning preserved.
- R12 is not described as started, and Ivo is not assigned responsibility for creating the logo.
- Any added scenario is clearly hypothetical.
03
Optional: use your own facts
Open a new chat. Copy the prompt below and replace [PASTE YOUR INPUT HERE] with your own non-sensitive source text, facts and limits for this task. Include any desired headings, count or length. Send the whole message. Expect the same kind of written result, using your facts. Check every source fact and limit yourself; the example’s names and totals do not apply. If a detail differs, show the exact mismatch and ask for a complete correction. Save the checked draft before any separate decision to use or send it.
Your starting prompt
Make a beginner glossary for every term below using my team’s supplied definitions. Use supplied requests in examples where useful. Clearly label any invented example scenario hypothetical. Do not replace a local meaning with an assumed general meaning.
Use only my input. Ask for information needed to finish rather than guessing. Return written text only; do not send, publish, book, submit or change another service.
MY INPUT
[PASTE YOUR INPUT HERE]
Optional: improve the result
Test the glossary on examples
Use simple classifications to see whether the definitions actually help. This extension uses the worked example. Return to that example chat, or paste its input and your checked example answer into a new chat first. Do not apply its sample values unchanged to your own input.
Advanced prompt
Create three clearly hypothetical mini-scenarios and ask which glossary term applies. Put an answer key after the questions, explaining each answer in one sentence. Keep the same SAMPLE INPUT from my first message unless I explicitly replace it.
Show, then try
See the shape of the result.
This input is synthetic. The output is a written illustration of the intended result, not a verified AI-tool run.
01 / The starting point
Synthetic input
Made-up example for practice. All people, organizations, records and product behavior below are fictional.
Source definitions for the fictional Moss team: backlog = requests recorded but not yet selected for work; triage = deciding the right queue and urgency for a request, not solving it; owner = person responsible for coordinating the next step, not necessarily doing all work; blocked = cannot take the next planned step because a named dependency is unresolved. Example facts: R12 is in the backlog. R13 is awaiting a logo file from the design team and its owner is Ivo. Format: term, plain explanation, example, common misunderstanding. Do not treat these as universal industry definitions.
Copies text only. For image or file tasks, use the source files named in the steps too.
Worked example written for this guide, not output recorded from a live AI session.
Backlog
Plain explanation: Requests the team has written down but has not chosen to work on yet.
Example: R12 is recorded in the backlog.
Do not assume: Being listed means work has started.
Triage
Plain explanation: Decide where a request should go and how urgent it is.
Example: Hypothetical: the team reviews a new request and chooses its queue.
Do not assume: Triage resolves the request.
Owner
Plain explanation: The person who coordinates the next step.
Example: Ivo is the owner of R13.
Do not assume: Ivo must do every piece of the work.
Blocked
Plain explanation: A stated dependency prevents the next planned step.
Example: R13 is waiting for the design team’s logo file.
Do not assume: Every unfinished request is blocked.
These definitions describe the Moss team’s usage.
These checks use the worked example and its particular facts. With your own material, check your actual names, numbers, sources and rules; do not reuse the sample’s values as the answer.
Unsaved checks stay in this tab and reset when you reload. If you choose Save guide, its current example checkmarks are kept in this browser when storage is available.
!
A few things to watch for.
A familiar business term can mean something different in another team. Keep the team label.
Avoid explaining one unknown term with several new ones.