Design a daily shutdown and next-day preparation checklist

작성자: AILesson5 분 소요테스트::ChatGPT검토일: 2026-08-28

빠른 답변

Close open loops, preserve context, and make tomorrow's first action easy to begin. 제공할 내용: Workday and tools, Current shutdown friction, Tomorrow constraints. 예상 결과: A short repeatable shutdown routine with exceptions, timing, and a ready-to-start tomorrow.

맥락 추가

텍스트는 이 브라우저에 유지됩니다. AILesson Prompts는 이를 모델이나 서버로 보내지 않습니다.

Workday and toolsCurrent shutdown frictionTomorrow constraints

프롬프트

채워지지 않은 필드는 플레이스홀더로 표시되므로 프롬프트를 복사하고 편집할 수 있습니다

Design a daily shutdown and next-day preparation checklist using the supplied workflow.

Work pattern, end time, tools, workspace, and handoffs:
[workflow]

Forgotten items, interruptions, privacy/safety needs, and failures:
[friction]

Tomorrow's appointments, priorities, dependencies, energy, and limits:
[tomorrow]

Create a normal routine that fits 10-20 minutes and a two-minute emergency version. Order actions by dependency. Include capture of loose tasks, triage rather than completion, promise/deadline verification, status/handoff updates, saving files with retrievable names, sensitive-information handling, calendar and first-task review, physical/digital reset, and a clear stop signal only where relevant. Do not require checking every inbox or planning the whole next day.

For each step give trigger, action, done condition, and skip/exception rule. Distinguish items that require a reply now from those merely captured. Prepare tomorrow's first physical action and required material, but do not make unauthorized commitments. Include a weekly maintenance item for stale tasks and routine improvement, plus a one-week trial measure for duration and missed-open-loop rate.

Playground에서 사용해 보기

기본적으로 비공개프롬프트 구성은 브라우저에서 로컬로 이루어집니다. 조직에서 허용하지 않는 한 기밀 정보를 AI 서비스에 입력하지 마세요.

입력에서 결과까지

적용 예시

구체적인 맥락이 이 레시피를 바로 사용할 수 있는 결과로 바꾸는 방법을 확인하세요

실제 입력

Workday and tools: Hybrid product designer, normally stops at 18:00. Jira holds tasks, Google Calendar meetings, Slack handoffs, Drive design notes, Figma working files. Laptop must be locked and paper customer notes stored in a drawer. London teammate takes over overnight only when explicitly handed off.
Current shutdown friction: I remember promised replies after dinner, leave unnamed Figma drafts open, and start mornings searching for context. Late meetings sometimes leave only two minutes. Checking Slack can create another 30 minutes of work. Friday tasks often stay stale.
Tomorrow constraints: At 09:30 there is a usability review. Before it, priority is to compare three prototype issues and recommend which to test. Researcher may add notes by 08:45 but has not promised. My best focus is 08:30-10:00. I can spend 15 minutes on shutdown.

예시 출력

15-minute normal shutdown, triggered at 17:45: (1) 3 min—capture loose promises/tasks from today's notes into Jira with source and real due date; done when notes have capture marks, not when tasks are completed. Reply now only if a hard same-day commitment would otherwise be missed. (2) 3 min—update the current Jira item with status, next action, blocker, and file link; skip Slack handoff unless a named London owner has accepted it. (3) 2 min—name/save Figma draft and Drive note with project/date, close duplicates; done when both links reopen. (4) 2 min—check tomorrow's calendar and identify conflicts only. (5) 3 min—prepare the first action: open a comparison note with the three issue IDs and evidence-link slots; write “08:30 compare available evidence; at 08:50 proceed without new researcher notes if absent.” Do not treat 08:45 notes as promised. (6) 2 min—store paper notes, lock laptop, and say “workday closed.”

Two-minute emergency: photograph no sensitive paper; instead place all paper in the locked drawer, add one Jira note containing current task/next action/file link, check the first calendar event, lock laptop. Any uncaptured thought goes on a single permitted paper capture card for next morning.

Friday maintenance: 15 minutes to review stale Jira items, broken links, and whether steps still earn their time. One-week trial: record shutdown duration and next-morning open loops discovered that were known the prior evening; target median ≤15 minutes and fewer misses than baseline, which must be measured during week one rather than invented.

효과가 있는 이유

1
A consistent capture-and-stop sequence reduces reliance on memory without extending the workday indefinitely
2
Preparing the first physical action lowers tomorrow's startup cost

결과 확인

Can the normal routine fit the time limit without doing newly discovered work
Does every step have a visible done condition and a useful exception rule
Are tomorrow's first action and materials prepared without assuming others' agreement

안심하고 사용하세요

자주 묻는 질문

이 레시피를 언제 사용해야 하는지, 무엇을 제공해야 하는지, 그리고 어떤 부분에서 사람의 검토가 여전히 중요한지에 대한 실용적인 답변

What should I prepare before using “Design a daily shutdown and next-day preparation checklist”?

For “Design a daily shutdown and next-day preparation checklist,” prepare Workday and tools, Current shutdown friction, and Tomorrow constraints. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.

When is the “Design a daily shutdown and next-day preparation checklist” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—A short repeatable shutdown routine with exceptions, timing, and a ready-to-start tomorrow—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.

Which AI tools have recorded tests for “Design a daily shutdown and next-day preparation checklist”?

The published test record for “Design a daily shutdown and next-day preparation checklist” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.

더 많은 탐색 방법