Stuck recovery
Light as air, firm as law. Spec-driven AI coding with hooks.
npx -y skills add testfree2023/airein --skill stuck-recoveryAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 28 days oldThe repository was created 28 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
同一问题尝试 3 次仍未解决时的恢复协议
SKILL.md
1.2 KB, as published. Nobody here has run it
Stuck Recovery Protocol
Maximum 3 attempts per issue, then STOP and follow this protocol.
Step 1: Document What Failed
Write down:
- What you tried (each attempt)
- Specific error messages (exact text)
- Why you think it failed
Step 2: Research Alternatives
- Find 2-3 similar implementations (search GitHub, Stack Overflow)
- Note different approaches used in each
- Check library docs for alternative APIs
Step 3: Question Fundamentals
- Is this the right abstraction level?
- Can this be split into smaller problems?
- Is there a simpler approach entirely?
- Are you solving the right problem?
Step 4: Try Different Angle
- Different library/framework feature?
- Different architectural pattern?
- Remove abstraction instead of adding?
- Simplify instead of generalizing?
Escalation
If still stuck after this protocol:
- Present the user with: what was tried, what failed, 2-3 possible next directions
- Ask the user for guidance or external resources
- Consider pairing with
tech-lead(mode: design or review) for a fresh perspective