resume-plan
Skill0 starsChanged 28 days agoMITView on GitHub
List saved plans in ~/.claude/plans and load one to resume working on it. Use when the user wants to pick up a previous plan, continue past work, or see what plans they have. Filters to the current repo by default.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- DasDigitaleMomentum/opencode-processing-skillstheir own version, first seen Oct 9, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- DasDigitaleMomentum/opencode-processing-skills★ 60same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- arch-reviewSkill
- explain-diffSkill
- explainSkill
- find-sessionSkill
- prep-compactSkill
- prep-prSkill
- prune-commentsSkill
- remove-commentsSkill
- review-pr-comments-loopSkill
- review-pr-commentsSkill
- runbookSkill
- session-review-loopSkill
- session-reviewSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 33
Default: keep only files whose basename starts with <repo>_.
- Very specific: line 35
If zero matches: after filtering: inform the user ("No plans found matching <filter> in repo <repo>."), then offer to show all plans or try …
- Very specific: line 36
"show all" escape hatch: if the user passes all as the arg, skip all filters and list everything.
- Distinctive: line 44
Read the chosen plan file.
- Distinctive: line 48
Ask the user (plain text, not AskUserQuestion):
- Very specific: line 56
Check whether a session plan file path is available (the harness provides it in the plan-mode system reminder, e.g.
- Very specific: line 57
If a session plan file path is present, copy the loaded plan's full contents into that file using the Write tool before entering plan mode.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
resume-plan
Load a previously saved plan from ~/.claude/plans/ and resume or revise it.
Steps
1. Determine repo context
Run:
basename "$(git rev-parse --show-toplevel 2>/dev/null)" 2>/dev/null || echo "no-repo"Store the result as <repo>.
2. List plans
Run:
ls -t ~/.claude/plans/*.md 2>/dev/nullThis returns files sorted newest-first.
3. Filter
- Default: keep only files whose basename starts with
<repo>_. - If an arg was passed (e.g.
/resume-plan consent): instead filter to files whose basename contains the arg substring (case-insensitive). Skip the repo filter in this case. - If zero matches after filtering: inform the user ("No plans found matching
<filter>in repo<repo>."), then offer to show all plans or try a different filter. Stop here. - "show all" escape hatch: if the user passes
allas the arg, skip all filters and list everything.
4. Present options
Take the first 4 matches. Use AskUserQuestion to let the user pick one. Label each option with just the filename (no directory prefix). If there are more than 4 matches, mention the count in the question text and suggest narrowing with a filter arg.
5. Read and summarize
Read the chosen plan file. Provide a 2–4 sentence summary: what repo/task it covers, the main approach, and roughly how far along it seemed.
6. Ask what to do next
Ask the user (plain text, not AskUserQuestion):
- (a) Resume — proceed with executing the plan as written.
- (b) Revise — enter plan mode so the plan can be updated before execution.
Act on their response.
If the user chooses Revise
- Check whether a session plan file path is available (the harness provides it in the plan-mode system reminder, e.g.
~/.claude/plans/can-you-see-the-mutable-deer.md). - If a session plan file path is present, copy the loaded plan's full contents into that file using the Write tool before entering plan mode. This ensures
/planshows the plan content and any inline edits are tracked by the harness. - Enter plan mode.
- Remind the user: when exiting plan mode, rename the session file to the canonical format
<repo>_<YYYY-MM-DD>_<descriptive-slug>.mdinside~/.claude/plans/(overwriting the original if the slug matches). The<repo>is the value from step 1; use today's date.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.