What problem does it solve?
Long-running or failure-prone Claude Code tasks lose progress when a session is interrupted, forcing agents to reconstruct state from chat history and risking unbounded retries or unverified claims of success. This Skill persists task state in a local checkpoint file so work can resume from explicit state with a finite attempt budget and recorded verification evidence.
Core Features & Use Cases
- Durable State Machine: Enforces a strict planned → running → verifying → succeeded/failed/blocked transition graph with terminal-state immutability and atomic file persistence.
- Bounded Attempt Budget: Each entry into running consumes one attempt, and transitions are rejected once maxAttempts is exhausted, preventing infinite retry loops.
- Verification Evidence Gate: A task cannot transition to succeeded until at least one passing evidence record is appended during the verifying state.
- Use Case: An agent migrating a database table is interrupted mid-task; the next session runs the status command, reads the saved nextAction, performs only that bounded step, records the actual test result, and then marks the task succeeded or schedules a bounded retry.
Quick Start
Ask Claude Code to initialize a checkpointed loop for your task with a finite attempt budget, then let it transition through running and verifying states while recording test evidence before marking the task complete.