execute-plan
Skill6 starsChanged 54 days agoNo licenceView on GitHub
Execute a written implementation plan task by task, with a critical review of the plan before starting and a checkpoint after every task. Use this skill whenever the user asks to "execute the plan", "implement the plan", "run the plan", "work through the plan", "start on task 1", "continue the plan", or points at a plan directory or file (e.g. under docs/plans/) and asks to build it. This is the natural next step after the create-plan skill — reach for it as soon as a plan exists and the ask is to start coding. If a skill named "executing-plans" is available in the session, this skill delegates the loop to it rather than duplicating it, while keeping its own review-gate and checkpoint invariants.
25 other projects use a version of this.
Adopted by
Most recently taken up by
- artberri/skillstheir own version, first seen Nov 8, 2026
- Ovich/charrettetheir own version, first seen Nov 7, 2026
- danielvm-git/bigpowerstheir own version, first seen Nov 6, 2026
- melconcoast/code-ideatheir own version, first seen Nov 2, 2026
- mattmireles/gemma-tuner-multimodaltheir own version, first seen Nov 1, 2026
- rakaarwaky/agents-arwakytheir own version, first seen Nov 1, 2026
Used with
Projects with it also use to-spec, grill-with-docs and 5 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.
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 3 projects that use this
MicrosoftSkillgrill-with-docs
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Also in 4 projects that use this
- GoogleSkill
grill-me
A relentless interview to sharpen a plan or design.
Also in 6 projects that use this
NVIDIASkillresearch
Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.
Also in 4 projects that use this
Hugging FaceSkillimplement
Make tests pass. Invoke after /write-tests produces failing tests.
Also in 3 projects that use this
- +2 more from google
Other versions25 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 25
- mattmireles/gemma-tuner-multimodal★ 1.5ksame name
- danielvm-git/bigpowers★ 288same name
- alamops/skills★ 53same name
- Integralist/agent-skills★ 23same name
- Ovich/charrette★ 14same name
- Ovich/swarmstorm★ 14same name
- T-miracle/codex-skills-zh★ 5same name
- melconcoast/code-idea★ 4same name
- preetamnath/agent-skills★ 4same name
- gfrancodev/overdrive★ 3same 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 repository15 other files it gives its agents.
- adcp-reviewSkill
- adcp-scorecardSkill
- adtech-expertSkill
- address-pr-commentsSkill
- create-branchSkill
- create-commitSkill
- create-planSkill
- gather-requirementsSkill
- local-bot-reviewSkill
- local-pr-reviewSkill
- local-reviewSkill
- local-test-reviewSkill
- plannerSkill
- raise-prSkill
- run-testsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 11 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 23 edited versions we read keep these.
11
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 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.
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.