streak plan / week 2 · free workflow
Plan the Way Back After a Broken Writing Streak — Free
Lay out the rebuild as dated steps with rising targets and the plan spaces them, so the return is a ramp you can actually keep rather than a single heroic session.
What this replaces
Streak recovery usually means trying to hit the old target on day one, failing, and stopping again. This spaces a dated rebuild with rising targets, so the first step is small enough to complete and the ramp is visible.
Tool note. This runs entirely in your browser — no account, no upload, no paid API key. Google NotebookLM is named as the free source-grounded reading path for the material you paste; its published free-tier terms were checked on 2026-09-13 and can change.
The four passes
Collect the smallest useful input
One day per line with a date and a word target for that day.
Let the plan space them
Each day is placed with the gap since the previous one.
Keep the first step embarrassingly small
The first day's job is to happen, not to be good.
Miss a day and continue
The plan shows gaps; it does not reset your progress.
Try it on the streak plan / week 2
The board below runs in your browser. It opens with a worked sample so the result is visible before you paste anything; switch scenarios, edit the text, or reset to the sample.
running the sample…
first-load · sample values are illustrative, not verified facts
Everything you paste stays in this browser tab. Nothing is uploaded, there is no account, and no request leaves the page to generate the result; clearing site data removes anything saved locally.
What breaks, and what to do
Targets set at the old level
That is how the second break happens; start below it.
Days with no date
Marked TBC and raised to the top of the urgency lane.
Editing counted as writing
Say which is which on the line, or the ramp is fiction.
Go deeper — Streak Plan
The free board above is the whole loop. The paid tier keeps the arranged output so you do not rebuild it.
- Printable ticket with a tick box for each rebuild day — estimate: 10 minutes saved per restart, basis: 5 days re-dated at ~2 minutes each
- Saved local history across breaks — estimate: 7 minutes saved per restart, basis: re-entering 5 days at ~84 seconds each
$4 one-time