next
Skill2 starsChanged 22 days agoLicence not identifiedView on GitHub
Detect where the project is in the leanwheel lifecycle and recommend the single next command — the answer to "what do I run now?" at any point from empty folder to post-MVP. Use when the user says "next", "what's next", "what now", "what should I run", "where am I", or opens a session unsure how to continue.
42 other projects use a version of this.
Adopted by
Most recently taken up by
- librosdeia/builder-method-claude-plugintheir own version, first seen Nov 15, 2026
- RyanDanielWalker/snipprtheir own version, first seen Nov 15, 2026
- warrendeanlangeveldt/code-kittheir own version, first seen Nov 15, 2026
- zecod/claude-queuetheir own version, first seen Nov 15, 2026
- elfrost/ai-patchlabtheir own version, first seen Nov 9, 2026
- edwinidrus/dragonhoardtheir own version, first seen Nov 8, 2026
Used with
Projects with it also use quick, idea and 8 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.
codebycoreySkillquick
Quick start a change with minimal interaction. Use when fast-tracking a straightforward change that needs proposal, design, and tasks in one step.
Also in 3 projects that use this
szweibelSkillidea
Generate a wide field of options when the user is brainstorming, exploring, expanding, or pressure-testing — not recommending or implementing
Also in 3 projects that use this
MicrosoftSkillcleanup
Also in 4 projects that use this
ArvorCoSkillclarify
Identify and resolve ambiguities in feature specifications. Use when spec has unclear requirements. Triggers on: clarify spec, resolve ambiguities, clarify requirements.
Also in 3 projects that use this
OpenAISkillaudit
Audit or critique a product flow, journey, workflow, funnel, onboarding path, checkout path, settings path, screen, or multi-step product experience by capturing screenshots first, then reporting UX, design, and accessibility findings inline from that evidence. Use Figma only when the user explicitly asks for a board. Use when the user asks to audit, review, critique, inspect, assess, analyze, evaluate, or give feedback on a product experience.
Also in 8 projects that use this
genomewalkerSkillexplore
RLM-style recursive memory exploration - dynamically navigate the memory graph
Also in 3 projects that use this
Other versions42 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 42
- vercel-labs/json-render★ 20ksame name
- vercel-labs/emulate★ 2ksame name
- ericboy0224/learn-docker-and-k8s★ 472same name
- mag123c/toktrack★ 196same name
- buildomator/buildomator★ 102same name
- jantichy/claude★ 52same name
- endlessblink/master-plan★ 26same name
- howells/fiction★ 23same name
- kennethleungty/claude-music★ 23same name
- Hainrixz/claude-db★ 22same name
32 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 repository45 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .claude-plugin/CLAUDE.mdCLAUDE.md
- .claude/skills/CLAUDE.mdCLAUDE.md
- appstore-connectSkill
- appstore-preflightSkill
- architectureSkill
- check-readinessSkill
- code-reviewSkill
- correct-courseSkill
- create-storySkill
- decision-logSkill
- deferredSkill
- design-verifySkill
- dev-single-goalSkill
- dev-storySkill
- discoverSkill
- doc-reviewSkill
- docs-syncSkill
- e2e-testsSkill
- elicitSkill
- epic-archiveSkill
- epic-flywheelSkill
- epicsSkill
- evalsSkill
- forge-ideaSkill
- github-trackingSkill
- harvest-findingsSkill
- ideateSkill
- investigateSkill
- prdSkill
- product-briefSkill
- quick-devSkill
- refresh-swiftSkill
- refresh-webSkill
- researchSkill
- retrospectiveSkill
- security-reviewSkill
- setupSkill
- specSkill
- statusSkill
- story-flywheelSkill
- swift-auditSkill
- upgrade-projectSkill
- uxSkill
- web-auditSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 37 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — 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 37 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.

