ProductivityText outputStructured Data outputGuided

Design My Ideal Daily Operating System

Builds a sustainable daily routine around existing commitments, energy patterns, responsibilities, and interruptions.

Published by AIPM · Updated Sep 5, 2026 · 0 copies

Ready to use

Prompt

Design a realistic daily operating system using appropriate context about my schedule, responsibilities, energy patterns, and goals.

Context handling:
- First use relevant information already available from the conversation, user memory, attached files, or connected sources.
- Do not ask the user to repeat information you already have.
- Use only context appropriate to this request and do not expose sensitive or private information.
- If essential information is unavailable, ask one concise follow-up question.
- State important assumptions and never invent facts.

Produce:
1. Start-up routine
2. Deep-work blocks
3. Communication and admin windows
4. Break and recovery structure
5. Shutdown routine
6. Minimum viable version for difficult days
7. A seven-day experiment

Requirements:
Preserve fixed commitments, include buffer time, and do not optimize every minute. If essential schedule context is missing, ask for working hours and fixed commitments.

Create your final prompt

Add your context and generate

Fill in the required variables below. Optional variables can be left blank and will remain as placeholders.

This prompt is ready to generate as written.

What to expect

Example output

A flexible daily template with focus blocks, breaks, admin windows, buffers, and a one-week trial.

Example context

Example input

Ask for a daily operating system; optionally mention working hours or energy patterns.

Discussion

Comments (0)

Loading comments…