resume-interrupted-work

Manages a project-root RESUME.md handoff file for resuming interrupted repository work.

1|Updated Aug 18, 2026
One-click install
npx skills add https://github.com/davidsneighbour/clerkwork --skill resume-interrupted-work-davidsneighbour
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resume-interrupted-work
Source: https://github.com/davidsneighbour/clerkwork/tree/main/skills/resume-interrupted-work
Command: npx skills add https://github.com/davidsneighbour/clerkwork --skill resume-interrupted-work-davidsneighbour

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Interrupted or paused agent work often loses context between sessions, forcing users to re-explain tasks or leaving repositories in an unknown state. This Skill maintains a project-root RESUME.md handoff file that captures unfinished work so any agent can resume it without prior chat history. ## Core Features & Use Cases - Startup Blocking Check: Before any repository work begins, the agent checks for RESUME.md, treats it as blocking unfinished work, and resolves it before starting unrelated tasks. - Structured Handoff Format: Enforces a fixed RESUME.md template covering status, original task, completed work, remaining steps, files, verification, and notes for the next agent. - Lifecycle Rules: Defines when to create, update, and remove RESUME.md, keeps it out of git commits, and registers the protocol in AGENTS.md and .gitignore during setup. - Use Case: An agent runs out of context mid-refactor. It writes RESUME.md listing changed files, failing tests, and next steps. In a new session, the user says "resume" and the next agent continues exactly where work stopped. ## Quick Start Say "resume" or "continue" at the start of a session to have the agent read RESUME.md and pick up the interrupted repository work.

Frequently Asked Questions about resume-interrupted-work

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

FAQPage Schema
How do I resume interrupted work in a repository with an AI agent?▼

Say "resume", "continue", or "carry on" at the start of a session. The agent checks for a project-root RESUME.md file, reads it, and continues the unfinished work described there before starting anything new.

What should a RESUME.md handoff file contain?▼

RESUME.md must include Status, Original Task, Completed work, Remaining Work, Files and Locations, Verification results, and Notes for Next Agent. It should use exact paths, commands, and error messages so another agent can continue without prior context.

When should RESUME.md be created or updated?▼

Create or update it whenever a task cannot be fully completed in the current step, such as user pauses, context or tool limits, missing credentials, partial multi-step work, or failed verification. Do not create it for speculative or optional future ideas.

Should RESUME.md be committed to git?▼

No. RESUME.md is a temporary scratch file and should not be included in commits unless the user explicitly asks. The skill recommends adding RESUME.md to .gitignore and moving durable items into issues, TODO.md, or PROJECT.md.

What happens if no RESUME.md exists when I say resume?▼

The agent continues from the visible current task context if possible. If neither RESUME.md nor visible context provides enough information to continue, the agent asks the user for the missing context.