Skip to content
reset logo

Reset System (Failure Recovery)

reset

Reset after failures, blockers, or when stuck. Use when execution hits a wall, something breaks, or we need to step back and reassess. This is the fifth system in the 5-system framework.

SKILL.md

Full skill instructions

Reset System (Failure Recovery)

Purpose: Gracefully recover from setbacks, learn, and continue. When to trigger: When stuck, something breaks, approach isn't working, or need to step back.

Failure Response Protocol

Step 1: STOP

Immediately cease current approach.

Do NOT:

  • Try "one more thing"
  • Keep pushing the same failing approach
  • Make changes hoping they'll work
  • Ignore the signals

Do:

  • Acknowledge something isn't working
  • Take a breath
  • Prepare to capture state

Step 2: CAPTURE STATE

Document what happened:

## Failure Capture

**What we were trying to do:**
[Description of goal]

**What actually happened:**
[Description of failure/​block]

**Error/​symptom observed:**
[Specific error messages, unexpected behavior]

**What we tried:**
1. Attempt 1: [what] → [result]
2. Attempt 2: [what] → [result]
3. Attempt 3: [what] → [result]

**Current git state:**
[Branch, commit, uncommitted changes]

Log this to .claude/​failure-log.md.

Step 3: CHECKPOINT

Ensure state is preserved:

  1. Git status - Are there uncommitted changes to save?
  2. Working state - Note the last known working commit
  3. Context - Save any important context that might be lost
git status
git stash  # if needed to preserve work-in-progress

Step 4: DIAGNOSE

Determine the root cause category:

Clarity Problem (misunderstanding)

  • Requirements were ambiguous
  • Success criteria unclear
  • Scope was wrong → Return to Clarity System

Identity Problem (hidden issue)

  • Discovered unknown constraint
  • Missed a dependency
  • Technical limitation found → Run Identity System

Priority Problem (wrong focus)

  • Solving the wrong problem
  • This should have waited
  • Dependencies not addressed → Return to Priority System

Execution Problem (bad approach)

  • Approach was flawed
  • Implementation strategy wrong
  • Need different technique → Try different approach, same task

External Block (outside control)

  • API down
  • Missing credentials
  • Need user input → Document and wait/​ask

Step 5: RESET TO APPROPRIATE SYSTEM

Based on diagnosis:

Root CauseAction
ClarityUpdate active-context.md, restart with clarity
IdentityRun identification, log new issues
PriorityRe-evaluate, might deprioritize
ExecutionNew approach, same goal
ExternalDocument, notify user, wait

Step 6: LEARN

Update .claude/​learnings.md with:

## Learning Entry - [Date]

**Failure:** [Brief description]

**Root Cause:** [What actually went wrong]

**Pattern:** [Is this a recurring issue?]

**Prevention:** [How to avoid this in future]

**New Rule/​Check:** [Any process improvement to add]

Failure Log Format

Maintain .claude/​failure-log.md:

# Failure Log

## Entry Template

| Date | Task | What Failed | Root Cause | Resolution | Learning |
|------|------|-------------|------------|------------|----------|
| 2026-01-01 | Add auth | Type errors cascaded | Didn't validate early | Reset, fix types first | Run tsc after every change |

## Detailed Entries

### [Date] - [Brief Title]

**Context:**
What we were doing

**Failure:**
What went wrong

**Attempts:**
What we tried

**Resolution:**
How it was fixed

**Takeaway:**
What we learned

Recovery Strategies

For Code Failures

  1. git stash or commit current state
  2. git checkout . to return to last working state
  3. Re-approach with new strategy

For Conceptual Failures

  1. Step back to clarity
  2. Re-read requirements
  3. Ask user for clarification

For Integration Failures

  1. Isolate the failing component
  2. Test in isolation
  3. Gradually reintegrate

For Persistent Failures

  1. Document thoroughly
  2. Ask user for help
  3. Consider if this is the right approach at all

Rules

  1. No shame in reset - It's better to restart cleanly than compound mistakes
  2. Document first - Don't reset without capturing what happened
  3. Learn always - Every failure is information
  4. Stay calm - Frustration compounds errors
  5. Ask for help - The user is a partner, not a judge

Transition

After reset:

  • Clarity problem → Clarity System
  • Hidden issue found → Identity System
  • Wrong priority → Priority System
  • Bad approach → Execution System with new approach
  • Resolved → Continue with task

This is System 5 of 5: Clarity → Identity → Priority → Execution → Reset

The Complete Cycle

          ┌─────────────────────────────────────────────┐
          │                                             │
          ▼                                             │
    ┌─────────┐     ┌──────────┐     ┌──────────┐      │
    │ CLARITY │ ──▶ │ IDENTITY │ ──▶ │ PRIORITY │      │
    └─────────┘     └──────────┘     └──────────┘      │
                                           │            │
                                           ▼            │
                                    ┌───────────┐       │
                                    │ EXECUTION │       │
                                    └───────────┘       │
                                           │            │
                              ┌────────────┴────────┐   │
                              ▼                     ▼   │
                        ┌─────────┐           ┌───────┐ │
                        │ FAILURE │           │SUCCESS│ │
                        │ (Reset) │           └───────┘ │
                        └─────────┘                     │
                              │                         │
                              └─────────────────────────┘

More skills from diegosouzapw

accessibility logo
diegosouzapw/awesome-omni-skill

accessibility

Accessibility guidelines for VS Code features — covers accessibility help dialogs, accessible views, verbosity settings, accessibility signals, ARIA alerts/status announcements, keyboard navigation, and ARIA labels/roles. Applies to both new interactive UI surfaces and updates to existing feature...

62 1
View
mermaid-diagrams logo
diegosouzapw/awesome-omni-skill

mermaid-diagrams

Mermaid diagram creation for flowcharts, sequences, ERDs, and more. Generate diagrams from text in markdown files. Use for documentation, architecture diagrams, and visual representations. Triggers on mermaid, flowchart, sequence diagram, ERD, entity relationship, gantt chart, pie chart, class di...

62 1
View
tauri2-react-rust logo
diegosouzapw/awesome-omni-skill

tauri2-react-rust

Guides development of cross-platform desktop apps with Tauri 2, TypeScript, React, and Rust. Use when building Tauri apps, implementing IPC, designing Rust backend or TypeScript/React frontend, when researching or cloning a website (open site, snapshot elements), when verifying local dev or built...

62 1
View
fp-ts-errors logo
diegosouzapw/awesome-omni-skill

fp-ts-errors

Handle errors as values using fp-ts Either and TaskEither for cleaner, more predictable TypeScript code. Use when implementing error handling patterns with fp-ts.

62 0
View
ring:pre-dev-research logo
diegosouzapw/awesome-omni-skill

ring:pre-dev-research

Gate 0 research phase for pre-dev workflow. Dispatches 3 parallel research agents to gather codebase patterns, external best practices, and framework documentation BEFORE creating PRD/TRD. Outputs research.md with file:line references.

62 0
View
create-assistant logo
diegosouzapw/awesome-omni-skill

create-assistant

Create and configure Vapi voice AI assistants with models, voices, transcribers, tools, hooks, and advanced settings. Use when building voice agents, phone bots, customer support assistants, or any conversational AI that handles phone or web calls.

62 0
View
codex-headless logo
diegosouzapw/awesome-omni-skill

codex-headless

Delegiere Aufgaben an OpenAI Codex CLI im Headless-Mode. Nutzt ChatGPT Subscription (KEIN API Key). Nur Workspace-Zugriff, KEIN System-Zugriff. Auto-Accept mit --full-auto. Web-Recherche mit --search.

62 0
View
social-media-scheduler logo
diegosouzapw/awesome-omni-skill

social-media-scheduler

Generate a full week of social media content for any topic. Outputs platform-optimized posts for Twitter/X, LinkedIn, and Instagram with hashtags and posting times.

62 0
View
Data Privacy Compliance logo
diegosouzapw/awesome-omni-skill

Data Privacy Compliance

Data privacy and regulatory compliance specialist for GDPR, CCPA, HIPAA, and international data protection laws. Use when implementing privacy controls, conducting data protection impact assessments, ensuring regulatory compliance, or managing data subject rights. Expert in consent management, da...

62 0
View
triple-review logo
diegosouzapw/awesome-omni-skill

triple-review

Reviews a task using the TRIPLE protocol, as the review agent.

62 0
View
Tech Stack & Architecture Decision logo
diegosouzapw/awesome-omni-skill

Tech Stack & Architecture Decision

Define and document the technology stack and architecture decisions for a project. Use when the user needs to choose a tech stack, make architecture decisions, define infrastructure choices, or document technology selections. Triggers on requests like "define the tech stack", "choose technologies...

62 0
View

Popular AI tools

Kaiber logo
Video

Kaiber

Generate, edit, and beat-sync AI video with leading models in one workspace.

Paid
View
Vimcal logo
Productivity

Vimcal

The world's fastest calendar for remote work

Free
View

Transform Your Design with AI Designer by ImgCreator.ai

Freemium
View
Akool AI logo
Content & writing

Akool AI

Revolutionizing Video Production with AI-Powered Creativity

Paid
View

Extend an image past the frame and let AI fill the new aspect ratio.

Freemium
View
StarByFace logo
Security

StarByFace

Discover your celebrity doppelgänger with StarByFace!

Free
View
C

ChainClarity explains 700+ crypto whitepapers in plain English, with layered summaries, comparisons, research tools, alerts, and a $4.99 Pro plan.

Freemium
View
Opus Clip logo
Coding & apps

Opus Clip

Opus.ai: Revolutionize Your Web Experience

Free
View