# Turn Confusing Instructions Into a Numbered Checklist

> A reusable prompt that rewrites a messy instruction or procedure into a numbered checklist, keeping conditions, warnings and source order intact.

## Install

Copy the content below into your project:

# Turn Confusing Instructions Into a Numbered Checklist

A reusable prompt that rewrites a messy instruction or procedure into a numbered checklist, keeping conditions, warnings and source order intact.

## Start here

This is an original reusable prompt for turning a confusing instruction, paragraph, or procedure into a numbered checklist a person can follow top to bottom. Nothing is installed and no technical setup is needed.

**What to paste, and where:** open an ordinary AI chat that accepts text. Paste the complete prompt (appended below) into the chat box, then add your own inputs after it:

- SOURCE TEXT: the confusing instruction or message.
- AUDIENCE: who will use the checklist.
- PURPOSE: the single outcome the reader should reach.
- KNOWN CONSTRAINTS (optional): e.g. "must fit on one page".

**How to check the output:** the reply should contain exactly the sections TITLE, WHO THIS IS FOR, BEFORE YOU START, CHECKLIST, DONE WHEN, GAPS I COULD NOT FILL, QUESTIONS TO CONFIRM BEFORE USE, in that order. Each numbered step should trace back to a sentence in your source, conditions should sit next to the step they affect, and anything missing should appear as [not stated in source] rather than an invented name, number, or deadline.

## What it does well

- Keeps your original wording of obligations: "should" is not upgraded to "must".
- Flags contradictions instead of guessing an order.
- Produces an explicit gaps list plus up to five confirmation questions.

## Limitations and permissions

- If SOURCE TEXT is missing, the prompt asks for it and stops.
- If AUDIENCE or PURPOSE is missing, it still drafts and records the assumption in the gaps list.
- It only prepares a draft for human review; it does not send, publish, file, or schedule anything, and it does not add legal, medical, or safety advice.
- For policies, contracts, or safety-critical procedures, the output carries a review notice and should be verified against the authoritative source.
- The worked example inside the prompt is fictional and exists only to show the output shape; it is not a test result.
- Privacy: paste only text you are allowed to share with the AI service you use.
- source reviewed; runtime not tested.

## FAQ

**Can I use it for a household rule or a classroom direction?** Yes. State the audience plainly; the checklist vocabulary follows whoever you name.

**What if my source has no owner or deadline for a step?** The prompt writes [not stated in source] and lists it under gaps, so you can fill it in yourself.

## Source and thanks

Original TokRepo prompt, CC BY 4.0. Reference context: [ChatGPT release notes](<https://help.openai.com/en/articles/6825453-chatgpt-release-notes>) (reviewed 2026-10-04). External reference material retains its own rights.

## Complete reusable prompt

You are helping me convert a confusing instruction into a numbered checklist that a person can follow top to bottom. Work only from the text I paste. Do not add steps, conditions, deadlines, or contacts that are not present or clearly implied.

INPUT I WILL PROVIDE
1. SOURCE TEXT: the original instruction, paragraph, or message that reads as confusing.
2. AUDIENCE: who will use the checklist (for example, a new employee, a volunteer, a family member, a student).
3. PURPOSE: the single outcome the reader should reach by the end.
4. KNOWN CONSTRAINTS (optional): anything the checklist must respect, such as "must fit on one page" or "reader has no prior training."

WHAT TO DO
- Read the SOURCE TEXT closely and identify: the end goal, the ordered actions, any conditions (if/when/unless), any responsible person for each action, any warnings or things to avoid, and any required inputs (forms, tools, approvals, materials).
- Rewrite it as a numbered checklist in the order the reader should actually perform the steps. If the original order is unclear or contradictory, keep the original sequence and flag the ambiguity instead of guessing.
- Each checklist item must start with a clear verb and name the actor when the source does (for example, "Submit", "Ask the supervisor to", "Check").
- Put conditions and warnings directly with the step they affect, not in a separate pile at the end.
- Keep the reader's vocabulary level appropriate to the stated AUDIENCE. Do not add motivational language.

OUTPUT FORMAT
Return exactly these sections, in this order:

TITLE: one short line stating the outcome.
WHO THIS IS FOR: one sentence using the AUDIENCE I gave.
BEFORE YOU START: bullet list of inputs, access, or prerequisites found in the source. If none are stated, write "None stated in the source."
CHECKLIST: numbered items. Use sub-bullets only for conditions ("If X, then…") or warnings tied to that step.
DONE WHEN: one or two sentences describing the finished state, drawn only from the source.
GAPS I COULD NOT FILL: list every place the source was silent, contradictory, or ambiguous (missing owner, missing deadline, two steps that conflict, an undefined term). If there are none, write "None found."
QUESTIONS TO CONFIRM BEFORE USE: up to five short questions whose answers would remove the gaps above.

HANDLING MISSING OR UNCLEAR INPUT
- If SOURCE TEXT is missing, ask me for it and stop.
- If AUDIENCE or PURPOSE is missing, produce a best-effort checklist and list the assumption in GAPS I COULD NOT FILL.
- Never invent a name, phone number, form title, system, deadline, or approval path. Write "[not stated in source]" in its place and add it to the gaps list.

REVIEW CHECKS BEFORE YOU FINISH
1. Every numbered step traces back to a sentence in the source. Remove or flag anything that does not.
2. No step combines two unrelated actions; split them.
3. Every condition appears next to the step it modifies.
4. The order matches the source unless the source itself is contradictory, in which case the contradiction is flagged.
5. No advice, safety claim, or legal or medical statement has been added beyond what the source says.
6. The gaps list and confirm questions are honest and specific, not generic.

BOUNDARIES
- You are preparing a draft checklist for a human to review. You are not sending, publishing, filing, or scheduling anything.
- Do not soften or strengthen the original obligation ("should" must not become "must", and the reverse).
- If the source is a policy, contract, or safety-critical procedure, say plainly at the top of the output: "Draft for human review; verify against the authoritative source."

WORKED EXAMPLE (fictional, for shape only)
Labeled example input:
SOURCE TEXT: "Staff needing to book the community room should email the office at least three days ahead. If the room is already booked, the office will suggest another date. Setup is the requester's job. Cleanup must be finished before 9pm."
AUDIENCE: volunteer group leaders
PURPOSE: book and use the community room correctly

Illustrative output shape:
TITLE: Community Room Booking Checklist
WHO THIS IS FOR: Volunteer group leaders booking the community room.
BEFORE YOU START: confirmed date; access to email; [not stated in source] for setup supplies.
CHECKLIST:
1. Choose your preferred date.
2. Email the office at least three days before that date to request the room. (If the room is already booked, the office will suggest another date.)
3. [not stated in source] Confirm which date was agreed.
4. Set up the room yourself; setup is the requester's job.
5. Finish cleanup before 9pm.
DONE WHEN: the room has been used and cleanup is finished before 9pm.
GAPS I COULD NOT FILL: office email address not stated; no confirmation deadline; responsibility for confirming the final date unclear.
QUESTIONS TO CONFIRM BEFORE USE: What is the office email? How and when will the booking be confirmed? Who confirms the final date?

Pass/fail checks tied to this example: PASS only if step 2 keeps "at least three days" exactly as written and the booking condition sits with that step; PASS only if the missing office email appears as [not stated in source] rather than an invented address; FAIL if a new step such as "post a sign" is added; FAIL if the 9pm cleanup rule is moved away from the cleanup step.

Now wait for my SOURCE TEXT, AUDIENCE, PURPOSE, and any KNOWN CONSTRAINTS.

## References and reuse

- [ChatGPT release notes](https://help.openai.com/en/articles/6825453-chatgpt-release-notes) · Reviewed 2026-10-04

Original TokRepo prompt · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Reference documents retain their own rights.

---

<!-- ZH -->

# 把混乱的说明改写成编号清单

一段可复用的提示词，把混乱的说明或流程改写成编号清单，保留条件、警告和原始顺序。

## 开始使用

这是一段原创可复用提示词，用于把混乱的说明、段落或流程改写成读者能从第一条顺序执行到最后的编号清单。无需安装，也无需任何技术配置。

**粘贴什么、粘到哪里：** 打开任何能接受文本的普通 AI 对话。把完整提示词（附在文末）粘贴到输入框，然后在后面补上你自己的输入：

- SOURCE TEXT（原文）：那段读起来混乱的说明或消息。
- AUDIENCE（读者）：谁会使用这份清单。
- PURPOSE（目的）：读者读完应达成的单一结果。
- KNOWN CONSTRAINTS（已知限制，可选）：例如“必须控制在一页内”。

**如何检查输出：** 回复应严格按顺序包含这些部分：TITLE、WHO THIS IS FOR、BEFORE YOU START、CHECKLIST、DONE WHEN、GAPS I COULD NOT FILL、QUESTIONS TO CONFIRM BEFORE USE。每个编号步骤都应对应原文中的一句话；条件应写在其影响的步骤旁边；缺失信息应显示为 [not stated in source]，而不是凭空编造姓名、号码或截止日期。

## 它的长处

- 保留原文对义务的措辞：“should”不会被改成“must”。
- 遇到矛盾时标记出来，而不是自己猜顺序。
- 会明确列出缺口，并给出最多五个待确认问题。

## 限制与权限

- 若缺少 SOURCE TEXT，它会向你索要并停止。
- 若缺少 AUDIENCE 或 PURPOSE，它仍会产出草稿，并把该假设写进缺口列表。
- 它只生成供人工审核的草稿，不会发送、发布、提交或安排任何事项，也不会添加法律、医疗或安全建议。
- 对于政策、合同或安全关键流程，输出顶部会带审核提示，应以权威原始文件为准。
- 提示词中的示例为虚构内容，仅用于展示输出结构，并非测试结果。
- 隐私：只粘贴你被允许提交给你所用 AI 服务的文本。
- 已审阅来源；未做运行时测试。

## 常见问题

**可以用在家庭规则或课堂指令上吗？** 可以。把读者写清楚即可，清单用语会跟随你指定的对象。

**如果原文某个步骤没有责任人或截止日期怎么办？** 提示词会写成 [not stated in source]，并列在缺口处，由你自己补充。

## 来源与致谢

TokRepo 原创提示词，CC BY 4.0。参考背景：[ChatGPT release notes](<https://help.openai.com/en/articles/6825453-chatgpt-release-notes>)（审阅于 2026-10-04）。外部参考资料保留其各自权利。

## 完整可复制提示词

你正在帮我把一段令人困惑的说明，转换成一个人可以从头到尾照着做的编号清单。只依据我粘贴的文本工作。不要添加原文中没有出现、也没有明确暗示的步骤、条件、截止日期或联系人。

我会提供的输入
1. SOURCE TEXT（原文）：那段读起来令人困惑的原始说明、段落或消息。
2. AUDIENCE（读者）：谁会使用这份清单（例如，新员工、志愿者、家庭成员、学生）。
3. PURPOSE（目的）：读者到最后应达成的单一结果。
4. KNOWN CONSTRAINTS（已知限制，可选）：这份清单必须遵守的任何事项，例如“必须控制在一页内”或“读者没有受过任何先前培训”。

要做什么
- 仔细阅读 SOURCE TEXT，并找出：最终目标、按顺序执行的动作、任何条件（if/when/unless）、每个动作的任何责任人、任何警告或应避免的事项，以及任何必需的输入（表格、工具、审批、材料）。
- 按读者实际应执行步骤的顺序，把它改写成编号清单。如果原始顺序不清楚或自相矛盾，保留原始顺序并标出歧义，而不是自行猜测。
- 每个清单条目必须以清晰的动词开头，并在原文点明执行者时写出执行者（例如，“Submit”、“Ask the supervisor to”、“Check”）。
- 把条件和警告直接放在其影响的步骤旁边，而不是另起一堆放在最后。
- 保持与所述 AUDIENCE 相适应的读者词汇水平。不要添加激励性语言。

输出格式
严格按此顺序返回以下部分：

TITLE：用一行简短文字说明结果。
WHO THIS IS FOR：用我给出的 AUDIENCE 写一句话。
BEFORE YOU START：用项目符号列出原文中找到的输入、访问权限或前提条件。如果原文没有说明，写“None stated in the source.”
CHECKLIST：编号条目。仅在该步骤相关的条件（“If X, then…”）或警告处使用子项目符号。
DONE WHEN：用一到两句话描述完成状态，只依据原文。
GAPS I COULD NOT FILL：列出原文沉默、矛盾或有歧义的每一处（缺少责任人、缺少截止日期、两个步骤相互冲突、术语未定义）。如果没有，写“None found.”
QUESTIONS TO CONFIRM BEFORE USE：最多五个简短问题，其答案可以消除上述缺口。

处理缺失或不清晰的输入
- 如果缺少 SOURCE TEXT，向我索要并停止。
- 如果缺少 AUDIENCE 或 PURPOSE，产出尽力而为的清单，并把该假设列在 GAPS I COULD NOT FILL 中。
- 绝不编造姓名、电话号码、表格名称、系统、截止日期或审批路径。在其位置写“[not stated in source]”，并将其加入缺口列表。

完成前复查检查
1. 每个编号步骤都应能追溯到原文中的一句话。移除或标出不能追溯的内容。
2. 没有步骤把两个不相关的动作合并在一起；将它们拆分。
3. 每个条件都出现在其修饰的步骤旁边。
4. 顺序与原文一致，除非原文本身自相矛盾；在这种情况下，标出该矛盾。
5. 没有在原文所述之外添加任何建议、安全声明或法律或医疗陈述。
6. 缺口列表和确认问题诚实且具体，而不是泛泛而谈。

边界
- 你是在准备一份供人工审核的清单草稿。你不是在发送、发布、提交或安排任何事项。
- 不要弱化或强化原始义务（“should”不得变成“must”，反之亦然）。
- 如果原文是政策、合同或安全关键流程，请在输出顶部明确写明：“Draft for human review; verify against the authoritative source.”

已做示例（虚构，仅展示结构）
带标签的示例输入：
SOURCE TEXT：“需要预订社区活动室的员工应至少提前三天给办公室发邮件。如果活动室已被预订，办公室会建议另一个日期。布置由申请人负责。清理必须在晚上 9 点前完成。”
AUDIENCE：志愿者小组负责人
PURPOSE：正确预订并使用社区活动室

示意性输出结构：
TITLE：Community Room Booking Checklist
WHO THIS IS FOR：预订社区活动室的志愿者小组负责人。
BEFORE YOU START：已确认的日期；可访问电子邮件；布置用品为 [not stated in source]。
CHECKLIST：
1. 选择你偏好的日期。
2. 至少在该日期前三天给办公室发邮件申请活动室。（如果活动室已被预订，办公室会建议另一个日期。）
3. [not stated in source] 确认最终约定的日期。
4. 自行布置活动室；布置由申请人负责。
5. 在晚上 9 点前完成清理。
DONE WHEN：活动室已使用完毕，且清理在晚上 9 点前完成。
GAPS I COULD NOT FILL：未说明办公室电子邮件地址；没有确认截止时间；确认最终日期的责任不明确。
QUESTIONS TO CONFIRM BEFORE USE：办公室电子邮件是什么？预订将如何以及何时确认？谁确认最终日期？

与本示例相关的通过/不通过检查：仅当第 2 步逐字保留“至少提前三天”，且预订条件与该步骤放在一起时，才 PASS；仅当缺失的办公室电子邮件以 [not stated in source] 出现，而不是编造一个地址时，才 PASS；如果新增了诸如“张贴标志”之类的步骤，则 FAIL；如果将晚上 9 点前清理的规则从清理步骤移走，则 FAIL。

现在等待我的 SOURCE TEXT、AUDIENCE、PURPOSE 以及任何 KNOWN CONSTRAINTS。

## 参考资料与复用

- [ChatGPT release notes](https://help.openai.com/en/articles/6825453-chatgpt-release-notes) · Reviewed 2026-10-04

TokRepo 原创提示词 · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)。参考资料保留各自原有权利。

---
Source: https://tokrepo.com/en/workflows/turn-confusing-instructions-into-numbered-checklist-4f21e631
Author: Prompt Lab