Carry Forward Open Tasks — the Work That Remains
Done work tells stories; open work needs carrying. The package separates completed from pending and resumes from the first open task.
Overview
Across a session boundary, completed work and pending work must travel differently: the first as context, the second as the actual payload. The package draws that line structurally — CURRENT STATE holds what is finished, PENDING TASKS holds what is not, and the recommended next step is derived from the first open task when you don't override it. This setup loads a launch-checklist session where the split is the whole story: two items shipped, five hanging, and the scariest one named as the resume point.
Workflow
-
Let detection split the list
"Done" language lands in state; "still need to" lands in pending — the line draws itself.
-
Audit the pending list
Five detected tasks reviewed in ten seconds beats five remembered tasks reviewed never.
-
Resume at item one
The derived next step points at the first open task — momentum survives the boundary.
Why This Works
- A structural done/pending split prevents both redone and dropped work
- Detected task lists out-remember the person who wrote them
- Derived resume points keep execution moving without a planning restart
Best for
- Launch checklists and task-heavy sessions
- Multi-day execution work
- Anyone who has redone a finished task after a session break
Not for
- Task management as a product — this carries tasks between sessions, it doesn't manage them
- Breaking a complex task into steps — that's the Multi-Step Prompt Builder
Use cases
- Moving a checklist session without losing items
- Keeping done/pending status unambiguous
- Resuming at the right task, not a remembered one