reviewing-plans
Skill8 starsChanged 8 months agoNo licenceView on GitHub
Reviews and refines feature plans for autonomous implementation readiness. Classifies issues as BLOCKING vs NON-BLOCKING, resolves autonomously, and graduates plans when implementable. Outputs READY/NEEDS_WORK status for loop integration. Use after project-planning skill.
- Deletes or force-pushes
7 other projects use a version of this.
Adopted by
Most recently taken up by
- kmorgan-r/claude-skillstheir own version, first seen Oct 22, 2026
- seanmcgary/claude-skillstheir own version, first seen Sep 25, 2026
- augments-labs/sdlc-skillstheir own version, first seen Aug 8, 2026
- kskonovalov/claude-skillstheir own version, first seen Jul 29, 2026
- tunahanaliozturk/ateliertheir own version, first seen Jun 20, 2026
- chrispangg/super-rpitheir own version, first seen Mar 10, 2026
Used with
Projects with it also use writing-plans.
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.
OpenAISkillwriting-plans
Use when you have a spec or requirements for a multi-step task, before touching code
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
- chrispangg/super-rpi★ 5same name
- augments-labs/sdlc-skills★ 1same name
- kmorgan-r/claude-skills★ 1same name
- ogu8/reviewing-plans★ 1same name
- tunahanaliozturk/atelier★ 1same name
- kskonovalov/claude-skills★ 0same name
- seanmcgary/claude-skills★ 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 repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adversarial-reviewSkill
- autonomous-developmentSkill
- create-new-skillSkill
- investigate-blockerSkill
- plan-to-ticketsSkill
- project-planningSkill
- project-visionSkill
- test-driven-developmentSkill
- using-ticketsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
40 rules. 0 are common, 36 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
36
Distinctive
This author's own choices. Worth a look.
4
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 5 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.