research-after-failure

npx skills add majiayu000/claude-skill-registry --skill research-after-failure-troykelly-claude-skills --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

# Research After Failure ## Overview After 2 failed attempts, stop and research. Don't keep trying the same thing. **Core principle:** Insanity is doing the same thing and expecting different results. **Trigger:** Two consecutive failed attempts at solving a problem. **Announce at start:** "I've failed twice. I'm stopping to research before trying again." ## The Rule ``` Attempt 1: Try solution │ ▼ Failed? │ ┌──────┴──────┐ │ │ Yes No → Done │ ▼ Attempt 2: Try different approach │ ▼ Failed? │ ┌──────┴──────┐ │ │ Yes No → Done │ ▼ STOP │ ▼ RESEARCH ← You are here │ ▼ Attempt 3: Try with new knowledge ``` ## What Counts as a Failure | Failure | Not a Failure | |---------|---------------| | Tests don't pass | Minor syntax error fixed | | Build breaks | Typo corrected | | Feature doesn't work | IDE autocomplete issue | | Same error recurs | Different error (progress) | | No progress made | Partial progress | ## The Research Protocol ### Step 1: Document the Failures Before researching, document what was tried: ```markdown ## Failed Attempts ### Attempt 1 **Approach:** [What was tried] **Result:** [What happened] **Error:** [Error message if any] ### Attempt 2 **Approach:** [What was tr

Check README
cat README.md
Check docs directory
ls -la docs/
cat docs/[relevant-topic].md
Check CONTRIBUTING
cat CONTRIBUTING.md
Search for relevant docs
grep -r "[keyword]" docs/
Find similar patterns