make-plan
Skill1 starsChanged 5 months agoNo licenceView on GitHub
Create a short implementation plan from a task, discussion, issue, bug report, or grill-me summary. Use when user asks to plan, or before risky/non-trivial edits where implementation path is unclear.
14 other projects use a version of this.
Adopted by
Most recently taken up by
- MMACABRE/SKILLStheir own version, first seen Nov 8, 2026
- nnguyenquangg/claude-code-spec-driven-developmenttheir own version, first seen Nov 2, 2026
- susantedit/claude-skillstheir own version, first seen Oct 20, 2026
- ekstremedia/claude-code-plan-and-executiontheir own version, first seen Oct 17, 2026
- oivanfelipe/claude-skillstheir own version, first seen Oct 13, 2026
- Pablomg02/pamaga-agent-toolkittheir own version, first seen Oct 11, 2026
Used with
Projects with it also use oh-my-issues, what-the and 6 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
tuliosalustiano27Skilloh-my-issues
Cluster a GitHub issue backlog by root cause into a small set of plan-master issues, redirect children with a standardized comment, and bundle architectural-fix PRs that close clusters atomically. Use when an issue tracker has accumulated dozens of reports that share underlying defects, when asked to triage / consolidate / cluster / dedupe issues, when asked to build a plan series or roadmap from open issues, or when routing a new incoming bug into an existing plan.
Also in 3 projects that use this
- tuliosalustiano27Skill
what-the
What the? Use when the user wants a plain-English breakdown of something technical — the who, what, where, why, and when.
Also in 3 projects that use this
barrelcSkillmem-search
Search kimi-mneme's persistent cross-session memory database. Use when user asks "did we already solve this?", "how did we do X last time?", "what did we do yesterday?", or needs work from previous sessions.
Also in 5 projects that use this
thedotmackSkillpathfinder
Map a codebase into feature-grouped flowcharts, identify duplicated concerns across features, and propose a unified architecture. Use when asked to "find the ideal path," unify duplicated systems, or audit architecture before a refactor. Emits a proposed unified flowchart plus per-system /make-plan prompts.
Also in 4 projects that use this
dqtx760Skilltimeline-report
Generate a "Journey Into [Project]" narrative report analyzing a project's entire development history from claude-mem's timeline. Use when asked for a timeline report, project history analysis, development journey, or full project report.
Also in 3 projects that use this
tunnckoCoreSkillhow-it-works
Use for 'how does X work', code walkthroughs before changing something, and placement / ownership / layering questions ('where should this live', 'which package owns this', 'is this the right layer'). Explains subsystem architecture, runtime flow, onboarding mental models. Can critique architecture. Use why for motivation.
Also in 3 projects that use this
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- pymc-labs/pymc-marketing★ 1.3ksame name
- GiggleLiu/cryochamber★ 34same name
- nnguyenquangg/claude-code-spec-driven-development★ 22same name
- jorgeasaurus/agent-skills★ 14same name
- dqtx760/skills-manage★ 2same name
- ekstremedia/claude-code-plan-and-execution★ 1same name
- gcapodeferro02/my-agent-skills★ 1same name
- lucidfrontier45/agent-skills★ 1same name
- MMACABRE/SKILLS★ 1same name
- Pablomg02/pamaga-agent-toolkit★ 1same name
4 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 repository6 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- cavemanSkill
- grill-meSkill
- implement-sliceSkill
- setup-repo-guardrailsSkill
- slice-planSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. 0 are common, 18 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
18
Distinctive
This author's own choices. Worth a look.
2
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 14 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.