DanielOnPurpose Resume Work
Counterpart to wrap-session. Crashed threads restarted from scratch, duplicate project folders, and blind handoffs all waste hours. This skill makes every resume start the same safe way: find everything first, touch nothing until confirmed.
The iron rule: if prior artifacts exist, you never start fresh. "Start over" almost always means "I couldn't find it."
Step 1 — Hunt for ALL prior state (read-only)
Search in this order:
- Handoff notes —
wrap-sessionwrites these. Check the project folder and any dashboards forHandoff,RESUME,STATUS,checkpointfiles. - Session history / transcripts — search prior sessions for 2–3 keywords from the project name. They often contain the exact resume prompt.
- Disk — search common work locations for the project folder, INCLUDING near-duplicate names (typos,
-2, nested copies). List every match. - Git — if a repo, check
git log --oneline -10andgit statusfor uncommitted work.
Step 2 — Inventory before touching
Produce a short state-of-the-work summary:
- What exists on disk (files, latest timestamps, which copy is canonical if duplicates)
- What was finished vs. mid-flight
- The recorded next action (from the handoff note or last transcript)
- How to launch/run it — state the exact command
Step 3 — Confirm the resume point
Show the summary and the proposed next action. Wait for a yes before modifying anything. If the handoff came from another tool, flag anything that looks wrong or half-done rather than building on it silently.
Never:
- Rebuild something that exists because finding it was hard
- Create a new project folder without listing near-matches first
- Overwrite handoff files before reading them
Step 4 — Work, then close the loop
Continue the work. When the session winds down, run wrap-session so the next resume starts from a handoff note instead of a hunt.