Define evidence that a booking is complete
Use fictional booking requirements, mock screens and notifications to draft completion checks. Match dates, time zones, party size, location and provider confirmation.
Execution environment and usage
AI / software
Text chat (ChatGPT, Claude or Gemini)
Where to operate
Optional text entry: start a new conversation at chatgpt.com; the supplied-text exercise can also be adapted to Claude or Gemini.
Getting started
- Start a new conversation at chatgpt.com and paste the original exercise prompt; do not use retired agent-mode onboarding.
- Use fictional booking requirements, mock screens and notifications to draft completion checks.
- For mock screens or package images, choose + → Add photos & files; paste complete text directly when images are unnecessary.
- Review the requested result against its original inputs: Distinguish finding a page, selecting a slot and receiving confirmation. Do not perform actions excluded by the prompt.
Setup and plan requirements
Complete, authorized text/sample inputs specified in the prompt; no external account access required.
Prompt portability limits
Portable as a planning/drafting exercise; the historical product is provenance, not a necessary execution environment. This is an adapted exercise, not equivalent execution of the historical agent workflow.
Usage limitations
Distinct personal agent product; check rollout/account setup, not implied by any ChatGPT account. Historical tool/source attribution is retained. Not hands-on tested; verify plan, region, workspace and site access separately.
Environment sources
適用情境 / When to use
Use fictional booking requirements, mock screens and notifications to draft completion checks. Match dates, time zones, party size, location and provider confirmation. Mark missing confirmation for human follow-up; do not make a booking. Source record: This is an early trial account by a commercial-content author; an independent reservation confirmation was not inspected.
步驟 / Steps
- Use a fictional task, time budget and acceptance requirements.
- Separate started, in-progress, waiting-for-user and completed states.
- Require a checkable artifact for completion and return useful progress after timeout.
提示詞 / Prompt
Using [fictional reservation requirements/time limit/simulated screens and notices], define completion evidence. Distinguish reaching a page, selecting a slot, awaiting the user and obtaining a confirmation record. Check date, timezone, party size, location and provider status for consistency. Without provider confirmation mark the outcome unconfirmed; retain available evidence for human handoff after timeout. Write acceptance criteria only; do not sign in, accept terms, book or send messages.
留意事項 / Cautions
- Reaching a booking page is not a confirmed reservation.
- Do not accept terms, contact third parties or pay automatically.
來源限制 / Evidence limits
No product ranking, regional availability or current capability is inferred; original publication date is unconfirmed.
流程說明 / Workflow note
These steps and prompts are original, untested exercises by this site, not the author’s verbatim workflow. Reported results do not guarantee exercise outcomes.
原始工具組合 / Original tool stack
Dots
Source checked: 2026-10-20