save-plan
Skill2 starsChanged 42 days agoMITView on GitHub
Save or update the agent's current plan to .opencode/plans/ in the working project
2 other projects use a version of this.
Adopted by
Most recently taken up by
- CSPulse/customer-success-skillstheir own version, first seen Nov 8, 2026
- AGMO-Inc/agmo-everywheretheir own version, first seen Mar 18, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- AGMO-Inc/agmo-everywhere★ 4same name
- CSPulse/customer-success-skills★ 2same 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 repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- changelog-bump-verSkill
- gh-copilot-review-readSkill
- gh-copilot-review-resolveSkill
- gh-copilot-reviewSkill
- gh-cr-submitSkill
- gh-issue-fixSkill
- gh-issueSkill
- gh-pr-mergeSkill
- gh-protect-default-branchSkill
- gh-pr-reviewSkill
- gh-prSkill
- gh-releaseSkill
- git-branchSkill
- git-commitSkill
- git-pushSkill
- make-changelogSkill
- mir-skills-installSkill
- mir-skills-updateSkill
- python-venvSkill
- session-noteSkill
- work-reportSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 8 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Create .opencode/plans/ directory in the project if it doesn't exist
- Distinctive: line 15
Write the final plan the agent has devised as freeform markdown — agent decides structure and content
- Distinctive: line 16
If a plan file for the same topic already exists, overwrite it with the latest version
- Distinctive: line 21
Use this skill when:
- Distinctive: line 37
Keep it concise (3-5 words max)
- Very specific: line 41
If .opencode/plans/<filename>.md already exists → overwrite with the latest plan
- Distinctive: line 42
No need to prompt the user.
- Distinctive: line 46
Write exactly the plan that was discussed/devised in the conversation
- Distinctive: line 47
Do not add boilerplate or enforce a fixed template.
- Distinctive: line 55
No plan devised yet: Do not save. Tell the user there is no plan to save yet and offer to devise one first.
- Very specific: line 56
Unclear topic: Use plan.md as the filename, or ask the user for a one-word topic if context is truly ambiguous.
≈ “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
What I do
- Create
.opencode/plans/directory in the project if it doesn't exist - Derive a topic-based filename in kebab-case from the plan subject (e.g.
add-csv-export.md) - Write the final plan the agent has devised as freeform markdown — agent decides structure and content
- If a plan file for the same topic already exists, overwrite it with the latest version
- Confirm the saved file path to the user
When to use me
Use this skill when:
- User asks to save, record, or write down the current plan
- User asks to update an existing plan with latest changes
- Agent has finished devising a plan and the user wants it persisted
Workflow
- Create directory:
mkdir -p .opencode/plans - Derive filename:
- Extract the main topic or subject of the plan from conversation context
- Format as kebab-case:
<topic>.md - Examples:
add-csv-export.md,refactor-auth-module.md,migrate-to-postgres.md - Keep it concise (3-5 words max)
- Fallback:
plan.mdif topic is unclear
- Check for existing file:
- If
.opencode/plans/<filename>.mdalready exists → overwrite with the latest plan - No need to prompt the user; silent overwrite is the expected behavior
- If
- Write plan:
- Content is freeform markdown — the agent decides the structure based on the plan it devised
- Write exactly the plan that was discussed/devised in the conversation
- Do not add boilerplate or enforce a fixed template; let the plan speak for itself
- Confirm to user:
- Report the file path:
.opencode/plans/<filename>.md - State whether it was created or updated
- Report the file path:
Edge Cases
- No plan devised yet: Do not save. Tell the user there is no plan to save yet and offer to devise one first.
- Unclear topic: Use
plan.mdas the filename, or ask the user for a one-word topic if context is truly ambiguous. - Not a git repo / no project root: Save relative to the current working directory;
.opencode/plans/still works. - Multiple unrelated plans in one session: Each gets its own topic-based filename and can coexist in
.opencode/plans/.
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.