source-command-ff-resume-handoff

Resumes development work from handoff documents with context analysis and validation.

1|1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/redblacktree/fastflow --skill source-command-ff-resume-handoff-redblacktree
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-command-ff-resume-handoff
Source: https://github.com/redblacktree/fastflow/tree/main/.agents/skills/source-command-ff-resume-handoff
Command: npx skills add https://github.com/redblacktree/fastflow --skill source-command-ff-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 rebuilds an actionable plan so work can continue without re-discovery. ## Core Features & Use Cases - Handoff Ingestion: Reads a handoff document fully, plus any linked research or plan documents under thoughts/shared/plans and thoughts/shared/research. - Ticket-Based Lookup: Given a ticket number like ENG-1234, locates the most recent handoff in thoughts/shared/handoffs/ENG-XXXX/ using timestamped filenames. - State Validation: Verifies that changes, learnings, and file references from the handoff still match the current codebase before acting. - Use Case: After a weekend break, run the command with your ticket number to get a synthesized analysis of task statuses, validated learnings, and a recommended next-action plan. ## Quick Start Ask the assistant to resume work from the handoff for ticket ENG-1234 and propose the next steps.

Frequently Asked Questions about source-command-ff-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 command with the handoff file path or a ticket number like ENG-1234. The skill reads the handoff fully, loads linked research and plan documents, verifies current state, and proposes next actions for your confirmation.

How does the skill find the latest handoff for a ticket?

It lists the directory thoughts/shared/handoffs/ENG-XXXX for the given ticket and selects the most recent file based on the YYYY-MM-DD_HH-MM-SS timestamp in the filename. If multiple files exist, the newest one is used.

What happens if no handoff exists for my ticket?

If the ticket's handoff directory is missing or empty, the skill tells you it cannot find the document and asks you to provide a direct path to the handoff file instead.

Does the skill verify handoff information before acting?

Yes. It reads all referenced artifacts, checks that documented changes still exist in the codebase, and flags diverged, incomplete, or stale handoff states before proposing a plan. Confirmation is required before implementation begins.

When should I not rely on a handoff document?

Avoid relying on handoffs when significant time has passed or major refactoring occurred, since the original approach may no longer apply. In those stale-handoff scenarios the strategy should be re-evaluated against the current codebase.