resume-handoff

Resumes work from handoff documents by validating current codebase state against recorded context.

1|1|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/corticalstack/flow --skill resume-handoff-corticalstack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resume-handoff
Source: https://github.com/corticalstack/flow/tree/main/.claude/skills/resume-handoff
Command: npx skills add https://github.com/corticalstack/flow --skill resume-handoff-corticalstack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When returning to a paused task, developers lose context about prior decisions, learnings, and next steps. This Skill reads a handoff document, verifies that the recorded state still matches the actual codebase, and rebuilds an actionable plan before continuing work. ## Core Features & Use Cases - Handoff Ingestion: Reads a handoff document fully, plus any linked research or plan documents under flow/plans or flow/research. - State Validation: Spawns research tasks to verify that recorded changes, learnings, and artifacts still exist and remain valid in the current codebase. - Interactive Continuation: Presents an analysis of original tasks, validated learnings, and recommended next actions, then builds a todo list after user confirmation. - Use Case: After a week away, run /resume-handoff gh-42 to pick up the most recent handoff for issue 42, confirm nothing has diverged, and continue implementation from where the previous session stopped. ## Quick Start Invoke the skill with a handoff path or work-item id, for example by asking to resume work from flow/handoffs/gh-123 using the latest handoff document.

Frequently Asked Questions about resume-handoff

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

FAQPage Schema
How do I resume work from a previous coding session?▼

Invoke the skill with a handoff document path or a tracker work-item id such as /resume-handoff gh-123. It reads the handoff fully, verifies the current codebase state against it, and proposes next actions before continuing.

What is a handoff document in an agentic coding workflow?▼

A handoff document captures tasks, statuses, recent changes, learnings, artifacts, and next steps from a prior work session. It is stored under flow/handoffs/<work-item>/ with timestamped filenames so work can resume with full context.

What happens if multiple handoff files exist for one work item?▼

The skill lists the work item's handoff directory and selects the most recent file based on the YYYY-MM-DD_HH-MM-SS timestamp in the filename. If no handoff exists, it asks you to provide a path.

Does resume-handoff verify the codebase before continuing?▼

Yes. It spawns research tasks to read referenced artifacts and confirms that recorded changes and learnings still match the current code. It presents discrepancies and recommended actions, then waits for your confirmation before implementing.

When should I not use a handoff document to resume work?▼

Avoid relying on a stale handoff when major refactoring has occurred since it was written. In that scenario the skill flags the divergence and helps re-evaluate strategy rather than blindly following outdated next steps.