resume-handoff

Reads and executes HANDOFF.md workflows while updating progress after each action.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/dennywu2966/denny-all-in-one --skill resume-handoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resume-handoff
Source: https://github.com/dennywu2966/denny-all-in-one/tree/main/home/.claude/skills/resume-handoff
Command: npx skills add https://github.com/dennywu2966/denny-all-in-one --skill resume-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates continued work by loading and executing action steps documented in HANDOFF.md.

Core Features & Use Cases

  • Load state from HANDOFF.md and parse goals, non-goals, and constraints.
  • Execute Next actions sequentially, updating HANDOFF.md after each action (marking done, in progress, or blockers) and refreshing the top actionable items.
  • Stop condition handling to end when the remaining work is trivial or a small set of actions remain, preserving a resumable state.

Quick Start

Load docs/HANDOFF.md, confirm the plan, and sequentially execute the Next actions while updating HANDOFF.md.

Frequently Asked Questions about resume-handoff

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

FAQPage Schema
How do I automate workflow execution and track progress from a handoff document?

Automating handoff workflow execution involves loading state from HANDOFF.md, parsing goals and constraints, confirming the plan, and sequentially executing actions while updating progress markers in the document.

What is the best way to resume in-progress tasks documented in a markdown file?

Resuming tasks from a markdown file requires loading the saved state, identifying the next actionable items, executing them sequentially, and marking each action as done or in-progress to preserve a resumable state.

How does state management work when executing sequential actions across multiple workflow steps?

State management during sequential action execution updates HANDOFF.md after each step by marking actions done, in-progress, or blocked, and refreshing the top actionable items to maintain live progress tracking.

Can I use this workflow automation for multi-step plans with strict non-goals and constraints?

Yes, workflow automation parses goals, non-goals, and constraints from HANDOFF.md to validate the plan before executing sequential actions, ensuring task execution aligns with defined boundaries.

When should workflow execution stop to preserve a resumable state for later completion?

Workflow execution stops when remaining work becomes trivial or only a small set of actions remain, preserving a resumable state in HANDOFF.md so you can complete minor tasks later without losing progress.

Why does my HANDOFF.md workflow require goal validation before executing next actions?

Goal validation before executing next actions ensures the loaded plan aligns with documented objectives and constraints, preventing off-track task execution and maintaining workflow integrity across sequential steps.