implementation-planner
Skill6 starsChanged 39 days agoMITView on GitHub
Use when a coding task is large enough to require repository inspection, a plan, affected files, risks, and verification before implementation.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- Flowerf19/agents-skillstheir own version, first seen Nov 8, 2026
- galz10/pickle-rick-extensiontheir own version, first seen Oct 8, 2026
- fworks-tech/agenthoodtheir own version, first seen Sep 28, 2026
- yh594774855/skill-collectiontheir own version, first seen Aug 3, 2026
- gasatrya/skillstheir own version, first seen Jun 9, 2026
- xuanjgcarryyou/claude-skilltheir own version, first seen May 29, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- galz10/pickle-rick-extension★ 454same name
- Flowerf19/agents-skills★ 3same name
- fworks-tech/agenthood★ 3same name
- gasatrya/skills★ 1same name
- ngothanhthien/claude-skills★ 0same name
- xuanjgcarryyou/claude-skill★ 0same name
- yh594774855/skill-collection★ 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 repository36 other files it gives its agents.
- bioinformatics-planningSkill
- biology-literature-analysisSkill
- biology-paper-analysisSkill
- chemistry-research-analysisSkill
- skill-authorSkill
- codebase-explorerSkill
- codebase-understandingSkill
- code-reviewSkill
- debug-systematicallySkill
- implementation-reviewSkill
- ledger-tasks-yyloSkill
- test-and-verifySkill
- algorithm-learningSkill
- system-design-basicsSkill
- defensive-security-reviewSkill
- threat-modelingSkill
- data-analysisSkill
- tutorSkill
- experiment-analysisSkill
- model-evaluationSkill
- numerical-methodsSkill
- mathematics-problem-solverSkill
- proof-solvingSkill
- physics-research-analysisSkill
- data-cleaningSkill
- data-visualizationSkill
- evidence-checkerSkill
- evidence-comparisonSkill
- experimental-planningSkill
- literature-synthesizerSkill
- reproducibility-auditSkill
- research-questionSkill
- source-verificationSkill
- api-designSkill
- frontend-planningSkill
- technical-editorSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
If important information is missing, ask focused questions before implementation.
- Distinctive: line 26
Do not modify files unless the user explicitly asks for implementation.
- Distinctive: line 30
Keep the plan concrete enough that another developer can execute it without rediscovering the repository.
“Common” is measured: kept by at least 6 in 10 of the 5 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.
Files
Implementation Planner
Goal
Turn a coding request into an implementation plan before changing code.
Instructions
- Inspect the repository structure and relevant configuration.
- Identify the smallest set of files likely to change.
- Trace existing patterns before proposing a new abstraction.
- State assumptions instead of silently inventing requirements.
- Produce:
- objective
- current architecture relevant to the task
- files to inspect/change
- implementation steps
- risks and edge cases
- verification plan
- If important information is missing, ask focused questions before implementation.
- Do not modify files unless the user explicitly asks for implementation.
Output
Keep the plan concrete enough that another developer can execute it without rediscovering the repository.
Source note
Inspired by recurring community recommendations to separate planning from implementation and keep work focused. See docs/community-sources.md.
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.