implement-plan
Skill1 starsChanged 23 days agoNo licenceView on GitHub
Implement a written plan phase-by-phase using sequential subagents, logging each phase's outcome back into the plan, then verifying and running a final code review.
28 other projects use a version of this.
Adopted by
Most recently taken up by
- korcekj/skillstheir own version, first seen Oct 28, 2026
- TylerAkins/ai-agent-skillstheir own version, first seen Oct 15, 2026
- insapption-projects/claude-agent-team-startertheir own version, first seen Oct 15, 2026
- paultyng/skill-issuetheir own version, first seen Oct 13, 2026
- Pablomg02/pamaga-agent-toolkittheir own version, first seen Oct 11, 2026
- mhylle/claude-skills-collectiontheir own version, first seen Oct 9, 2026
Used with
Projects with it also use iterate-plan, validate-plan and 9 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.
corticalstackSkilliterate-plan
Revise an existing implementation plan in flow/plans/ based on feedback, researching when needed. Explicit-only; run only when invoked via /iterate-plan or explicitly asked.
Also in 5 projects that use this
shawn-dumasSkillvalidate-plan
Validate an orchestration plan after pre-flight certification. Runs adversarial review, deep review (verify prompt data against codebase), and PoC gate for risky approaches. Auto-invoked by orchestrate-* skills at Step 8.
Also in 4 projects that use this
parcadeiSkilldescribe-pr
Generate comprehensive PR descriptions following repository templates
Also in 4 projects that use this
joshuaalpuertoSkillresearch-codebase
Conducts structured research across a codebase to answer questions about architecture, components, and data flow. Use when investigating how code works, where functionality lives, or how systems interact. Decomposes questions, runs parallel investigations, synthesizes findings with file:line references, and produces persistent research documents.
Also in 4 projects that use this
JetBrainsSkillcreate-plan
Research the codebase and create an implementation plan with architecture notes, design document, and track decomposition. Use when starting a new feature or large change.
Also in 8 projects that use this
- JetBrainsSkill
review-plan
Manually re-run the autonomous plan review (Phase 2 — consistency + structural). The same review runs automatically as the first phase of /execute-tracks; this command is for re-runs after inline replanning or whenever the plan needs explicit re-validation. TRIGGER when: user asks to re-validate the plan after inline replanning; user requests explicit plan review outside /execute-tracks. SKIP: /execute-tracks already running State 0 in this session (autonomous Phase 2 path will fire) — do not double-run.
Also in 5 projects that use this
- +1 more from JetBrains
Other versions28 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 28
- penpot/penpot★ 62ksame name
- ChatbotXIO/ChatbotX★ 1.1ksame name
- OpenFn/lightning★ 321same name
- maxedapps/agent-skills★ 59same name
- atomicinnovation/accelerator★ 34same name
- hawkyre/hawk-skills★ 30same name
- mhylle/claude-skills-collection★ 20same name
- L-X-T/ng-agentic-skills★ 13same name
- paultyng/skill-issue★ 8same name
- Akindu23/my-agent-skills★ 4same name
18 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 repository13 other files it gives its agents.
- aztec-mainframeSkill
- blueprintSkill
- create-prSkill
- ethereum-clientsSkill
- html-explainerSkill
- l1-rpc-castSkill
- linear-issuesSkill
- my-contextSkill
- pr-statusSkill
- start-workSkill
- tackle-issueSkill
- update-node-threat-modelSkill
- writing-wellSkill
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 9 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 28 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
3
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 28 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.