implement
Skill11 starsChanged 2 days agoMITView on GitHub
Execute an active plan task-by-task with state discipline — verified anchors, tests before checkbox ticks, clean stopping points, deviations written back into the plan. Use when the user says "implement <plan>", "continue the plan", "work on the next task", or asks to start building something that already has a plan.
192 other projects use a version of this.
Adopted by
Most recently taken up by
- philoserf/claude-code-configtheir own version, first seen Nov 15, 2026
- muxy-app/muxytheir own version, first seen Nov 15, 2026
- geoffbremner/skillstheir own version, first seen Nov 15, 2026
- SireJeff/k0ntexttheir own version, first seen Nov 15, 2026
- quickchatai/quickreviewtheir own version, first seen Nov 15, 2026
- HiteSit/real-scientist-skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use setup-ts-deep-modules, ask-matt and 10 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.
liufeng1976Skillsetup-ts-deep-modules
Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.
Also in 43 projects that use this
GoogleSkillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Also in 91 projects that use this
RoentekSkillloop-me
Grill me about specs for the workflows I want to build, within this workspace.
Also in 50 projects that use this
AWSSkillto-questionnaire
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
Also in 88 projects that use this
ryotaroh180105Skillclaude-handoff
Hand the current conversation off to a fresh background agent that picks up the work immediately.
Also in 42 projects that use this
GoogleSkillto-spec
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Also in 168 projects that use this
- +3 more from google
Other versions192 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 192
- mattpocock/skills★ 325ksame name
- QuivrHQ/quivr★ 40ksame name
- The-Vibe-Company/quivr★ 40ksame name
- foambubble/foam★ 17ksame name
- formbricks/formbricks★ 13ksame name
- ArcReel/ArcReel★ 6.6ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.8ksame name
- fallow-rs/fallow★ 5.3ksame name
- withcoral/coral★ 4.9ksame name
- bestofjs/bestofjs★ 3.1ksame name
182 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.
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 2 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 174 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Load the context: Read the full plan, the specs in its ## Spec changes, and data/product.md ## Constraints and ## Authoring rules — they …
- Very specific: line 22
Check
## Depends on: Every prerequisite plan must carry stage: done. - Very specific: line 29
Execute the next unchecked task: Follow its Files: list; write the code.
- Very specific: line 33
Write back deviations: If implementation reveals the ## Approach (or a task breakdown) is wrong, update the plan — amend the section, add …
- Distinctive: line 37
Stop at a clean boundary: After each task (or more, if the user asked for a longer run), report progress — "3/5 tasks, next: <task name>" — …
- Very specific: line 41
Finish: When the last box ticks, run the plan's ## Verification commands, report the results, and suggest the verify skill for the full …
- Distinctive: line 47
Never tick a box whose tests fail or weren't run — an unchecked box that's actually done is a nuisance.
“Common” is measured: kept by at least 6 in 10 of the 174 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
Implement a plan
Coding happens as it always does; this skill adds the discipline that keeps the plan document true while it happens. The plan is the source of truth: the code follows it, and where reality wins an argument, the plan is updated — never silently outgrown.
Steps
- Select the plan. Infer from conversation; if ambiguous, list the plans
under
## Activeindata/plans.mdand ask (most recently created first). Announce: "Working on:<plan>— task N of M". No plan exists for what the user wants built? Stop and point at the plan skill. - Load the context. Read the full plan, the specs in its
## Spec changes, anddata/product.md## Constraintsand## Authoring rules— they bind the code you're about to write. - Check
## Depends on. Every prerequisite plan must carrystage: done; if one doesn't, say so and stop — building on an unshipped dependency is how two plans end up half-true. - Re-verify the anchors. The plan's
## Key referencesline numbers were true when written; re-locate each symbol in the current checkout before relying on it. If lines moved, update the anchor list and its "verified as of" date — that edit is part of this session's work. - Execute the next unchecked task. Follow its
**Files:**list; write the code; run the tests that cover this task. When the task's work is done and its tests pass, tick its- [ ]→- [x]in the plan doc andiwe normalize. - Write back deviations. If implementation reveals the
## Approach(or a task breakdown) is wrong, update the plan — amend the section, add or split tasks — before coding past the discrepancy, and tell the user what changed and why. - Stop at a clean boundary. After each task (or more, if the user asked
for a longer run), report progress — "3/5 tasks, next:
<task name>" — and stop. Blocked mid-task? Leave the box unchecked, describe the blocker, and stop there instead. - Finish. When the last box ticks, run the plan's
## Verificationcommands, report the results, and suggest the verify skill for the full pre-ship check, then the ship skill.
Rules
- Never tick a box whose tests fail or weren't run — an unchecked box that's actually done is a nuisance; a checked box that isn't done is a lie the next session builds on.
- Checkbox flips and anchor updates belong to the same change as the code they describe — the same commit, where the plan and the code share a repository.
- One task at a time unless the user asks for more; small honest increments beat a big unreviewable one.
- This skill implements; it doesn't ship. Status flips, spec sync, and release recording stay with the ship skill.
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.

