plan-first
Skill5 starsChanged 2 months agoMITView on GitHub
write a short spec and plan before editing code; no edits until the plan is agreed
11 other projects use a version of this.
Adopted by
Most recently taken up by
- cathyzhang0905/agent-cockpittheir own version, first seen Nov 8, 2026
- fvkmizel/soulkeepertheir own version, first seen Nov 8, 2026
- Hvftpie13/Flashmind_Gemini-3.8-Flash_Smart-agenttheir own version, first seen Nov 1, 2026
- AndrewBrown-USDA/aigb-skills-usdatheir own version, first seen Oct 31, 2026
- randommonicle/claude-skillstheir own version, first seen Oct 25, 2026
- nadavnaveh/skillstheir own version, first seen Oct 25, 2026
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- duncan-buildroom/freeskills★ 65same name
- hongshuxifan321/plan-first★ 43same name
- Hvftpie13/Flashmind_Gemini-3.8-Flash_Smart-agent★ 39same name
- randommonicle/claude-skills★ 27same name
- AndrewBrown-USDA/aigb-skills-usda★ 7same name
- nadavnaveh/skills★ 2same name
- cathyzhang0905/agent-cockpit★ 0same name
- fvkmizel/soulkeeper★ 0same name
- justomsharma/github-resume-assistant★ 0same name
- kartykk/agent-ready★ 0same name
1 more not listed
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 repository8 other files it gives its agents.
- agent-budgetSkill
- code-reviewSkill
- commit-disciplineSkill
- dependency-checkSkill
- eval-before-mergeSkill
- incident-reviewSkill
- safe-refactorSkill
- test-firstSkill
The file
Files
plan-first
before touching code:
- state the goal in one sentence.
- list the files you expect to change.
- name how you'll know it worked (the check).
only then edit. if the change needs more than a few files you didn't expect, stop and re-plan.
when to abort
stop and hand back if:
- the plan can't name a check for "done".
- the file list keeps growing - the goal isn't understood yet.
- the change wants to touch something the spec never mentioned.
a plan you can't exit cleanly is worse than no plan.
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.