reset

Document state and guide re-evaluation after execution workflow failures.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ioku24/autorankr --skill reset
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reset
Source: https://github.com/ioku24/autorankr/tree/main/.claude/skills/5-system-framework/5.reset
Command: npx skills add https://github.com/ioku24/autorankr --skill reset

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides automatic recovery after execution failures, helping teams reset their approach, preserve context, and continue workflows without manual rework.

Core Features & Use Cases

  • Failure capture & checkpointing: Record the current state, goals, and attempts to enable precise re-entry.
  • Diagnosis & routing: Classify issues and redirect to the appropriate system (clarity/identity/priority/execution) for rapid remediation.
  • Learning & logging: Persist learnings in a structured log to improve future runs and prevent repeat failures.

Quick Start

To start using the reset framework, trigger a failure in your current task, then follow the Failure Capture and Checkpoint steps to preserve state and re-plan.

Frequently Asked Questions about reset

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate failure recovery and preserve state when an execution workflow is blocked?

Automated failure recovery captures the current execution state and goals to enable precise checkpointing and re-entry. This preserves context and allows you to continue workflows without manual rework after a setback.

What is the best way to diagnose execution errors and route them to the correct system?

Diagnosis and routing classify execution issues and redirect them to the appropriate system—clarity, identity, priority, or execution—for rapid remediation. This structured classification ensures failures are routed accurately for resolution.

How does state capture and checkpointing work for interrupted system-design workflows?

State capture and checkpointing work by recording the current execution state, goals, and attempted approaches when a failure occurs. This documented checkpoint enables precise re-entry into the workflow once the blocker is resolved.

Can I use this failure recovery approach for any step in an execution workflow?

Yes, you can apply this failure recovery approach to any execution workflow step where results are blocked, errors occur, or new information requires a different approach. It guides re-evaluation universally across the workflow.

How do I log learnings from workflow failures to prevent repeat issues?

Log learnings from workflow failures by persisting structured records of the diagnosis and recovery steps. This structured logging improves future runs and prevents repeat failures by preserving historical context.