next
Skill0 starsChanged 4 months agoNo licenceView on GitHub
Gathers in-progress work state (queues·status·DEC·deliverables) and ranks the next action deterministically. Not a linear happy path — it presents blocker resolution (fix), upstream reflow (backward), and forward progress together. This is the work-control entry point that reduces the burden of the PM manually chaining repeated /lc calls. The model reports the routing decision from next_emit.py rather than guessing it.
40 other projects use a version of this.
Adopted by
Most recently taken up by
- edwinidrus/dragonhoardtheir own version, first seen Nov 8, 2026
- buildomator/buildomatortheir own version, first seen Nov 4, 2026
- mag123c/toktracktheir own version, first seen Nov 3, 2026
- Hainrixz/claude-dbtheir own version, first seen Nov 1, 2026
- mandarzope/fullstack-swarmtheir own version, first seen Nov 1, 2026
- vercel-labs/emulatetheir own version, first seen Oct 29, 2026
Used with
Projects with it also use quick, project and 7 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
BugRogerSkillproject
Project lifecycle management. Dispatches to Ada.
Also in 3 projects that use this
AnthropicSkillstatus
Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.
Also in 9 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 7 projects that use this
Other versions40 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 40
- vercel-labs/json-render★ 19ksame name
- vercel-labs/emulate★ 2ksame name
- ericboy0224/learn-docker-and-k8s★ 472same name
- mag123c/toktrack★ 196same name
- buildomator/buildomator★ 102same name
- jantichy/claude★ 45same name
- endlessblink/master-plan★ 26same name
- howells/fiction★ 23same name
- kennethleungty/claude-music★ 23same name
- Hainrixz/claude-db★ 22same name
30 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 repository37 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- bddSkill
- confirmSkill
- critiqueSkill
- crSkill
- dec-approveSkill
- discoverSkill
- draft-reqSkill
- exploreSkill
- extract-templateSkill
- fanoutSkill
- flowSkill
- from-urlSkill
- graph-genSkill
- import-sourceSkill
- ingestSkill
- init-hubSkill
- integrateSkill
- intent-routerSkill
- journeySkill
- lcSkill
- plan-auditSkill
- product-auditSkill
- promoteSkill
- renderSkill
- research-autoSkill
- researchSkill
- reviewSkill
- screen-detailSkill
- scSkill
- searchSkill
- seSkill
- stakeholderSkill
- suSkill
- orange-pm:updateSkill
- write-clusterSkill
- writeSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 36 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
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 36 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.