implementation-plan
Skill1 starsChanged 3 months agoMITView on GitHub
Convert a plan, PRD, backlog item, or vague feature into ordered implementation work with acceptance criteria and verification. Use when the user asks to break down work, make an implementation plan, create tasks, plan execution, or use slice-plan.
25 other projects use a version of this.
Adopted by
Most recently taken up by
- dvy1987/agent-loomtheir own version, first seen Nov 15, 2026
- anuragsarkar97/skillstheir own version, first seen Nov 8, 2026
- AndersonAndrad/skillstheir own version, first seen Nov 8, 2026
- Mehul72/skillstheir own version, first seen Nov 8, 2026
- aniketshukla1/sdlc-kittheir own version, first seen Nov 8, 2026
- jboczek/skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use code-quality and security-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.
MicrosoftSkillcode-quality
Statically check changed C# against the same deterministic rules github-code-quality[bot] runs on pull requests, so a contributor can fix likely findings before opening the PR and keep the bot's inline comments to a minimum. Activate when a contributor asks to "check code quality", "run code quality on my changes", "will the code quality bot complain", "pre-check before I open the PR", "code quality check", or similar. Scoped to C#. Reads the diff and compares it against the enumerated csharp-code-quality rule set below — no CodeQL download or build required. This is a fast approximation of a dataflow engine, not a reproduction; report accordingly. Does NOT apply fixes unless explicitly asked.
Also in 3 projects that use this
SentrySkillsecurity-review
Finds exploitable application security vulnerabilities in code changes. Use for Warden security scans, appsec review, OWASP-style checks, authentication or authorization bugs, injection, XSS, SSRF, path traversal, secrets, unsafe crypto, webhook verification, open redirects, or sensitive data exposure.
Also in 3 projects that use this
Other versions25 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 25
- Neeeophytee/finding-unknowns-skills★ 339same name
- POW-Software/ByteSync★ 172same name
- petrowsky/agentic-fm★ 98same name
- gregwebs/skills-sdlc★ 21same name
- marc-ing/marc-skills★ 14same name
- Mozurok/fhorja.dev★ 10same name
- Nirusan/claude-config★ 7same name
- fattain-naime/engineering-docs★ 6same name
- affectionatec/agentic-engineering★ 5same name
- dvy1987/agent-loom★ 4same name
15 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 repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- architecture-reviewSkill
- debugSkill
- domain-modelingSkill
- handoffSkill
- requirements-reviewSkill
- test-and-verifySkill
- webgl-scroll-siteSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 23 edited versions we read keep these.
8
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 12
Do one job: convert intent into ordered, independently provable work.
- Distinctive: line 15
Avoid ceremony: no full process framework when a two-step plan is enough.
- Distinctive: line 16
Keep tool and tracker assumptions explicit.
- Distinctive: line 20
Use for plan breakdowns, implementation sequencing, issue creation, PRD-to-work conversion, or when a task is too large to complete safely …
- Distinctive: line 26
Prefer vertical tasks through the real interface over layer-by-layer tasks.
- Distinctive: line 28
Keep dependencies explicit and minimal.
- Distinctive: line 32
Read the source plan and the current implementation surface.
- Distinctive: line 36
If the user asked to create issues or files, publish/write them after confirming any tracker or path requirements.
“Common” is measured: kept by at least 6 in 10 of the 23 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-plan
Break work into tasks that can be built, reviewed, and verified independently.
Unix/Pi Contract
- Do one job: convert intent into ordered, independently provable work.
- Consume a plan, PRD, issue, or conversation; emit tasks with acceptance criteria and verification.
- Make every task pipeable into
PLAN.md, a tracker issue, or an implementation prompt. - Avoid ceremony: no full process framework when a two-step plan is enough.
- Keep tool and tracker assumptions explicit.
Use
Use for plan breakdowns, implementation sequencing, issue creation, PRD-to-work conversion, or when a task is too large to complete safely in one edit.
Slice Rules
- Each task should produce observable behavior or a meaningful invariant.
- Each task should include tests or a concrete verification command.
- Prefer vertical tasks through the real interface over layer-by-layer tasks.
- Mark human-decision tasks separately from agent-executable tasks.
- Keep dependencies explicit and minimal.
Workflow
- Read the source plan and the current implementation surface.
- Identify the narrowest first task that reduces uncertainty.
- Split remaining work by user-visible behavior, contract, or migration step.
- Attach acceptance criteria, files likely touched, and verification commands.
- If the user asked to create issues or files, publish/write them after confirming any tracker or path requirements.
Output
For each task:
- Title.
- Type: executable, decision, review, or cleanup.
- Acceptance criteria.
- Likely files.
- Verification.
- Dependencies.
End with the recommended first task.
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.

