plan-executor
Skill0 starsChanged 3 months agoNo licenceView on GitHub
Execute implementation plans from the ./plans/ directory step by step. Use when asked to "work on the next feature", "continue the current plan", "execute plan", "what's next", or any reference to picking up planned work. Reads plan files, implements one step at a time, respects review gates, and tracks progress.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- nguyenvanphituoc/shapeup-sdlc-plugintheir own version, first seen Nov 8, 2026
- pregnantboy/claude-skillstheir own version, first seen Oct 20, 2026
- NatanGer97/nautinktheir own version, first seen Oct 15, 2026
- michaelreynolds111-dev/ai-contexttheir own version, first seen Aug 15, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- nguyenvanphituoc/shapeup-sdlc-plugin★ 3same name
- NatanGer97/nautink★ 2same name
- michaelreynolds111-dev/ai-context★ 0same name
- pregnantboy/claude-skills★ 0same 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 repository4 other files it gives its agents.
- code-mentorSkill
- learning-path-creatorSkill
- plan-architectSkill
- rubber-duckSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
24 rules. 0 are common, 14 are distinctive, and 10 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
14
Distinctive
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.