implementation-planner
Skill0 starsChanged 10 months agoNo licenceView on GitHub
Structured implementation planning for software development tasks. Use when the user provides a spec, feature request, bug report, or any development task that needs to be broken into an actionable plan. Handles (1) Bug fixes - root cause analysis and fix planning, (2) New features - ERD, use cases, and implementation tasks, (3) Feature modifications - current vs target logic with migration plan, (4) Feature extensions - adding capabilities to existing features. Outputs dependency-aware task breakdowns where each file = 1 epic.
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
- cellrishi-code/claude-skills-atlastheir own version, first seen Oct 4, 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
Used with
Projects with it also use code-review.
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.
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 3 projects that use this
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
- cellrishi-code/claude-skills-atlas★ 6same name
- Flowerf19/agents-skills★ 3same name
- fworks-tech/agenthood★ 3same name
- gasatrya/skills★ 1same 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 repository7 other files it gives its agents.
- agent-mailSkill
- conventional-commitsSkill
- extract-plan-to-beadSkill
- gitlab-knowledge-graphSkill
- medical-admissionSkill
- orchestratorSkill
- workerSkill
The file
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.