source-command-resume-handoff

Resumes work from handoff documents by analyzing context and validating current state.

1|1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/redblacktree/fastflow --skill source-command-resume-handoff-redblacktree
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-command-resume-handoff
Source: https://github.com/redblacktree/fastflow/tree/main/.agents/skills/source-command-resume-handoff
Command: npx skills add https://github.com/redblacktree/fastflow --skill source-command-resume-handoff-redblacktree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When returning to a paused development task, engineers lose context about prior decisions, learnings, and next steps. This Skill reads handoff documents, verifies the current codebase state against them, and proposes a validated continuation plan. ## Core Features & Use Cases - Handoff Discovery: Locates handoff documents by direct path or by ticket number (e.g., ENG-1234) under thoughts/shared/handoffs/, selecting the most recent file when multiple exist. - Context Verification: Reads linked research and plan documents, validates that recorded changes and learnings still match the current codebase, and flags regressions or divergences. - Action Planning: Converts handoff action items into a tracked todo list and confirms the approach with the user before implementation. - Use Case: After a weekend break, run the command with ticket ENG-2124 to reload the latest handoff, verify the partial refactor it describes is still intact, and continue implementation from where the previous session stopped. ## Quick Start Ask the assistant to resume work from the most recent handoff for ticket ENG-1234 and propose the next steps.

Frequently Asked Questions about source-command-resume-handoff

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

FAQPage Schema
How do I resume work from a handoff document?▼

Invoke the resume_handoff command with either a direct path to the handoff file or a ticket number like ENG-1234. The skill reads the handoff fully, verifies the current state, and proposes next actions before proceeding.

How do I find the latest handoff for a ticket?▼

Provide the ticket number (e.g., ENG-2124) and the skill lists the contents of thoughts/shared/handoffs/ENG-2124/. When multiple files exist, it selects the most recent one based on the YYYY-MM-DD_HH-MM-SS timestamp in the filename.

What happens if no handoff exists for a ticket?▼

If the ticket's handoff directory is missing or empty, the skill tells the user it cannot find the document and asks for a direct path to the handoff file instead of guessing or fabricating context.

Does the skill verify handoff content against the current codebase?▼

Yes. It reads referenced artifacts, learnings, and recent changes, then checks whether those changes still exist and flags regressions, diverged code, or stale approaches before proposing a course of action.

When should I not rely on an old handoff document?▼

Avoid relying on stale handoffs when significant time has passed or major refactoring occurred, since the original approach may no longer apply. The skill handles this by re-evaluating strategy against the current state before acting.