next
Skill1 starsChanged 30 days agoMITView on GitHub
Read the project state and produce a short ranked recommendation of 1-3 actions. This skill never executes the recommended commands — it only suggests. Produce a short report with two sections:
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 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
BugRogerSkillproject
Project lifecycle management. Dispatches to Ada.
Also in 3 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
genomewalkerSkillexplore
RLM-style recursive memory exploration - dynamically navigate the memory graph
Also in 3 projects that use this
GoogleSkillcritique
Expertise in auditing and fixing repository scripts and GitHub Actions workflows to ensure technical robustness and security.
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 repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- audit-projectSkill
- cleanupSkill
- create-skillSkill
- dailySkill
- dependency-checkSkill
- documentSkill
- execute-prpSkill
- ez-project-workflowSkill
- fix-issueSkill
- generate-prpSkill
- housekeepingSkill
- kickoffSkill
- monitor-setupSkill
- performanceSkill
- pipelineSkill
- refactorSkill
- retrospectiveSkill
- review-codeSkill
- rollbackSkill
- security-scanSkill
- statusSkill
- tddSkill
- upgrade-statusSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 36 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Read the project state and produce a short ranked recommendation of 1-3 actions.
- Distinctive: line 11
Read in this order, skipping silently any source that does not exist:
- Very specific: line 27
No INITIAL.md, fresh repo, on main → run kickoff to start a new feature interview
- Distinctive: line 59
Always print the literal command to run, with exact arguments.
- Very specific: line 61
Always remind that execute-prp and retrospective should run in fresh sessions (ADR-013).
- Distinctive: line 62
If state is genuinely ambiguous (e.g., 5 PRPs active), ASK the user to pick rather than guess.
- Distinctive: line 63
Never fabricate state — if a marker is missing or unreadable, say so and skip that branch.
- Distinctive: line 64
Keep output under 30 lines.
“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.
Files
Next-step advisor
Read the project state and produce a short ranked recommendation of 1-3 actions. This skill never executes the recommended commands — it only suggests.
Phase 1: Detect state
Read in this order, skipping silently any source that does not exist:
.ezproject.jsonfor mode and stackINITIAL.md— exists? when was it last modified? does it still contain placeholders?PRPs/*.md— active (un-archived) PRPsPRPs/done/*.md— recently completed (last 30 days)git status --short— uncommitted filesgit rev-parse --abbrev-ref HEAD— current branchgit log --since="2.weeks.ago" --oneline— recent activitygit log -1 --format="%ar — %s"— last commit summary- CLAUDE.md last modification date — drift signal
grep -l "ai-patchlab\|2026-05-12\|\[REMPLIR\]" *.md— unfinished kickoff?
Phase 2: Decision tree (top-down, first match wins)
- Placeholders remain in INITIAL/CLAUDE/ROADMAP/README → run
kickoffto finish project setup - No INITIAL.md, fresh repo, on main → run
kickoffto start a new feature interview - INITIAL.md exists, no PRP for it → run
generate-prp INITIAL.md - Active PRP, never executed → run
execute-prp PRPs/<name>.mdin a NEW conversation (fresh context per ADR-013) - Active PRP with partial progress → resume
execute-prp PRPs/<name>.md - PRP moved to
PRPs/done/within last 24h, no retrospective committed since → runretrospective lastin a NEW conversation - Uncommitted changes on a feature branch → run
review-codebefore committing - Feature branch ahead of main, tests passing, no active PRP → open a PR or run the release pipeline if available
- 3+ weeks since CLAUDE.md modified AND 10+ commits since → run
audit-project - 30+ days since pyproject.toml change, never ran a dependency check → run a dependency audit
- Many TODO/FIXME comments accumulating → run a cleanup pass
- On main, nothing in progress → list top 3 unchecked ROADMAP items and ask the user to pick, then run
kickoff
Phase 3: Output
Produce a short report with two sections:
## Where you are
- Mode/Stack: ...
- Branch: ...
- Active PRP: ...
- Uncommitted: ...
- Last commit: ...
- Recent activity: ...
## Recommended next steps
1. [PRIMARY] <command with exact args> — <one-sentence reason tied to detected state>
2. [SECONDARY] <command> — <reason>
3. [LATER] <command> — <reason>Rules
- Always print the literal command to run, with exact arguments.
- Tag each recommendation [PRIMARY] / [SECONDARY] / [LATER].
- Always remind that
execute-prpandretrospectiveshould run in fresh sessions (ADR-013). - If state is genuinely ambiguous (e.g., 5 PRPs active), ASK the user to pick rather than guess.
- Never fabricate state — if a marker is missing or unreadable, say so and skip that branch.
- Keep output under 30 lines.
- This skill MUST NOT execute the recommended commands. It only suggests.
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.

