Turn a big goal into a working weekly system, not just a plan
A plan tells you what to do. A system survives the week that doesn't go as planned.
- Outcome
- A plan sized to real capacity, a weekly review that catches drift early, and a recovery mechanism for the inevitable bad week.
- Time
- 30-45 minutes to set up, then a 10-15 minute weekly review
The guided runner is a Pro feature
Every step is fully readable and copyable below, free. Pro adds step sequencing, carried inputs, checkpoints, and resumable runs.
Most goal plans are built for an idealized best week and treat a bad week as evidence the plan failed, when really the plan was never designed to absorb one. A real system, not just a plan, is sized to actual capacity from the start, includes a regular check that catches drift while it's small, and has an explicit recovery mechanism for when a week goes wrong — because some weeks always do.
When not to use this
For a short-term, low-stakes goal, this much structure is overkill — just do the thing. This is for a goal with real duration where you have a track record of good intentions not surviving contact with a real week.
Before you start
- A specific goal with real duration (weeks to months)
- Honesty about your actual capacity and past failure patterns
Size the plan to actual capacity and known failure patterns
Build the plan around reality instead of an idealized best week.
Fill in
Goal: {{goal}}
Real constraints: {{constraints}}
What's derailed me before: {{failure_pattern}}
Build a plan sized to my actual capacity, not an idealized version.
Design around my stated failure pattern explicitly — don't build a
plan that ignores it and hope this time is different. Define the
minimum viable version of each step for a bad day. Tell me honestly
if the goal itself is unrealistic in this timeframe.Why it works
Designing around your actual, stated failure pattern rather than ignoring it is what makes the plan different from every other well-intentioned plan that failed the same way before — a plan that schedules mornings despite "I always skip mornings" isn't optimistic, it's just wrong.
Checkpoint
You have a plan sized to real capacity, explicitly designed around your known failure pattern, with a minimum-viable version per step.
Common mistakes
- ×Understating constraints to seem more committed, producing an unsustainable plan.
- ×Ignoring the stated failure pattern and building a plan that repeats it.
Run a weekly review that catches drift early
Notice and address drift while it's small, not after it's compounded.
Fill in
This week: {{week_summary}}
Run my weekly review: what actually worked and why, what didn't and
the real underlying reason (not "I was busy"), and one specific
change for next week based on this, not a vague intention.Why it works
Catching drift weekly, with a specific real-reason diagnosis rather than "I was busy," is what allows a small correction instead of discovering a month later that the plan quietly stopped happening three weeks ago.
Checkpoint
You've identified the real reason behind any drift and committed to one specific change for next week.
Common mistakes
- ×Accepting a vague reason for drift instead of the specific underlying cause.
- ×Skipping the weekly review during a busy week, which is exactly when it matters most.
Use the recovery mechanism when a week genuinely fails
Resume from where you are, not from the beginning or by quitting.
I had a genuinely bad week — [describe what happened]. Help me resume the plan from where I actually am right now, not from the beginning and not by treating this as a reason to quit. Adjust the plan if the bad week reveals something about capacity I got wrong initially.
Why it works
Most goals die not from the missed week itself but from the story that gets told about it — "I've failed, may as well stop." An explicit, planned mechanism to resume from where you are, rather than from the beginning, removes the need to make that decision in a low-motivation moment.
Checkpoint
You have resumed the plan from your actual current point, with any necessary adjustments based on what the bad week revealed.
Common mistakes
- ×Restarting from the very beginning after a bad week instead of resuming from where you are.
- ×Treating a bad week as proof the whole goal is unrealistic instead of checking if it's just this week.
Follow-ups
- It's been a month — run a bigger review: is the plan still realistic given how it's actually gone?
- I want to increase the goal now that the base plan is working well. Help me adjust.
Did this work?
A bad week doesn't derail the goal — you have a specific way to notice drift and resume from where you are, not from the beginning.
Tested on claude-opus-5. Evidence status is draft; it moves to battle-tested only on recorded runs, never by hand.