Skills on AI

Ideal Week System

Download raw SKILL.md

Use when asked to design a template week in time blocks that reflects priorities, energy, and commitments, then compare real weeks against it. Distinct from [[weekly-planning-meeting]] (a team meeting to plan one week), [[calendar-control]] (defending and auditing the live calendar), and [[annual-review]] (yearly reflection on goals).

An ideal week is a reusable template: the week you would choose if nothing unexpected happened, laid out in blocks for work, rest, relationships, and upkeep. Real weeks will differ. The value is in having a baseline to compare against, so drift is visible and choices are deliberate. It is for one person; it is not a team plan.

Input required

  • Fixed commitments: work hours, school runs, classes, standing meetings, caring duties, commute.
  • Priorities: three to five things that should get time (a project, health, a relationship, learning, rest).
  • Energy pattern: when the user tends to think best, when they flag, and which days differ.
  • Flexibility: what can move, and who else's schedule is involved.
  • The last real week, roughly, to compare.

Questions to ask first

Ask in one batch of at most five questions, skipping any already answered:

  1. What are the commitments that cannot move?
  2. What are your top three to five priorities this season?
  3. When in the day is your energy highest, and when lowest?
  4. Which area of life gets the least time today but matters most?
  5. How did last week actually go, in broad hours by area?

Method

  1. List the areas. Choose categories such as deep work, shallow work, meetings, exercise, family, friends, admin, learning, chores, and rest. Keep it to eight to ten.
  2. Place the fixed blocks first. Add anything immovable so the rest is designed around reality.
  3. Match demanding work to high-energy hours. Put deep work and hard conversations there; put admin and errands in the low-energy stretches.
  4. Add priorities as named blocks. A priority without a block is a wish. Give each a day and a time, even if brief.
  5. Add buffers and slack. Leave unassigned time, commonly a block or two per day, for overflow and surprises. A week with no slack fails by Tuesday.
  6. Add rest and a weekly review. Protect sleep, a day or half-day off, and a short slot to plan the next week.
  7. Compare a real week. At week's end, log actual hours by area against the template. Note the biggest gaps and ask why: poor estimate, interruption, or changed priority.
  8. Adjust the template or the behavior. If the gap repeats, the template is wrong. If priorities changed, update the template. If neither, fix the habit that caused it.

Comparing plan to actual

| Area | Planned | Actual | Gap | Cause | |---|---|---|---|---| | Deep work | 10 h | 4 h | -6 h | Meetings in morning blocks | | Exercise | 3 sessions | 1 | -2 | Skipped when tired |

Hours here are an example, not a recommended target.

Output format

  • Template week: a day-by-day grid or list in time blocks, with block names and a legend.
  • Priority check: each priority and where it lives in the week.
  • Fixed versus flexible blocks marked.
  • Comparison table for last week, if data is given.
  • Three adjustments to make next week.

Ground rules

  • Fill the user's real constraints before ideals; do not design a week that assumes more hours than exist.
  • Do not prescribe sleep, exercise, or work totals as universal; use the user's own targets or a stated default.
  • Do not push 100 percent scheduling; slack is part of the design.
  • If the user's health, caring, or disability needs are involved, design around them rather than against them.
  • Treat the template as revisable, not a verdict on the user.

Self-check before answering

  • Are fixed blocks placed first, and flexible ones after?
  • Does each stated priority have its own block?
  • Is there slack, rest, and a weekly review slot?
  • Is the hours total possible in a week?

Common pitfalls

  • Fantasy week: no travel time, no meals, no slack.
  • Rigid grid: abandoning it after one disrupted day.
  • Priorities without blocks: good intentions with no home.
  • Ignoring energy: deep work scheduled at the user's low point.
  • Never comparing: a template that is not checked against real weeks is decoration.
  • Copying someone else's week: their commitments are not yours.

Example prompt

Design an ideal week for me. I work 9 to 5:30, have two kids to collect on Tuesdays and Thursdays, and want time for writing, the gym, and my partner. I think best in the morning. Then show me how to compare my real weeks against it.

Learn more

View ideal-week-system/SKILL.md on GitHub