unstuck
Skill0 starsChanged 3 months agoMITView on GitHub
Break implementation loops by forcing architectural rethinking when stuck on a failing approach.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- ribato22/vibechecktheir own version, first seen Nov 8, 2026
- Enjoyoer/loadouttheir own version, first seen Nov 1, 2026
- momentmaker/kaijutsutheir own version, first seen Nov 1, 2026
- coreyhaines31/makerskillstheir own version, first seen Oct 8, 2026
- molly-diversifiedfun/claude-skillstheir own version, first seen Sep 16, 2026
- Q00/ouroborostheir own version, first seen Jul 31, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- Q00/ouroboros★ 6.3ksame name
- coreyhaines31/makerskills★ 893same name
- momentmaker/kaijutsu★ 3same name
- ribato22/vibecheck★ 3same name
- molly-diversifiedfun/claude-skills★ 1same name
- Enjoyoer/loadout★ 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 repository44 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- a11y-auditSkill
- ai-engineerSkill
- api-clientSkill
- changelog-enforcerSkill
- code-cleanup-guardianSkill
- code-reviewerSkill
- contract-testSkill
- db-migrateSkill
- dep-auditSkill
- devops-automatorSkill
- env-configSkill
- error-observabilitySkill
- frontend-designSkill
- git-commit-helperSkill
- github-issues-managerSkill
- git-issue-syncSkill
- git-protocolSkill
- handoffSkill
- incident-responseSkill
- init-projectSkill
- karpathy-guidelinesSkill
- market-researcherSkill
- parallel-agent-git-isolationSkill
- product-strategistSkill
- pr-workflowSkill
- rapid-builderSkill
- release-managerSkill
- resumeSkill
- scrutinizeSkill
- shadcn-uiSkill
- skill-builderSkill
- sprint-plannerSkill
- state-machine-diagramsSkill
- state-managementSkill
- surveySkill
- system-architectSkill
- tech-docsSkill
- ux-design-systemSkill
- ux-researchSkill
- webapp-testingSkill
- web-dev-fundamentalsSkill
- workflow-optimizerSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
Not variations of the same pattern — fundamentally different architectures.
- Distinctive: line 45
No more iterations on the old approach
- Very specific: line 47
If the new approach also fails after 2 attempts, run /unstuck again with updated context
“Common” is measured: kept by at least 6 in 10 of the 6 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
Unstuck — Break Implementation Loops
Stuck on: $ARGUMENTS
Stop iterating on the current approach. Rethink its architecture.
Step 1: Autopsy the Current Approach
- What's actually failing? (Be specific — error message, behavior, symptom)
- Why can't the current approach work? (Root cause, not symptom)
- What architectural assumption is flawed?
Step 2: Generate 5 Radically Different Strategies
Not variations of the same pattern — fundamentally different architectures.
For each:
- [Strategy Name] — one-line description
- Key change: what makes this fundamentally different
- Complexity: Simple / Medium / Complex
- Success likelihood: Low / Medium / High
Step 3: Pick One
Select the simplest approach with highest success likelihood.
- Why this one
- What new problems it might introduce
- What to watch for
Step 4: Execute
- [Action 1]
- [Action 2]
- [Action 3]
- [Validation — how to prove it works]
Rules:
- No more iterations on the old approach
- New architecture only
- If the new approach also fails after 2 attempts, run
/unstuckagain with updated context
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.

