resume-handoff

Resume Handoff

You are tasked with resuming work from a handoff document through an interactive process. These handoffs contain critical context, learnings, and next steps from previous work sessions that need to be understood and continued.

Input

$ARGUMENTS — path to a handoff document under .rpiv/artifacts/handoffs/. If omitted, the skill lists available handoffs and asks which to resume from.

Metadata

echo "### recent (read only in case of empty user input)"
echo "recent handoffs:"
node "${SKILL_DIR}/../_shared/list-recent.mjs" .rpiv/artifacts/handoffs 10

Flow

1. Input → 2. Read & analyze handoff → 3. Synthesize & present → 4. Create action plan → 5. Begin implementation

Steps

Step 1: Input Handling

When this command is invoked:

1. If the path to a handoff document was provided:

   • If a handoff document path was provided as a parameter, skip the default message
   • Immediately read the handoff document FULLY using the Read tool
   • Immediately read any research or plan documents that it links to under .rpiv/artifacts/plans or .rpiv/artifacts/research or .rpiv/artifacts/solutions. Read these critical files DIRECTLY using the Read tool - do NOT invoke skills for this initial reading phase.
   • Begin the analysis process by ingesting relevant context from the handoff document, reading additional files it mentions
   • Then propose a course of action to the user and confirm, or ask for clarification on direction.

2. If no parameters provided, branch on the recent handoffs: listing in the Metadata block:

   • Empty — no handoffs exist; tell the user and ask for a path in prose.
   • Exactly one entry — confirm with ask_user_question: "Resume this handoff?" with options "Resume <filename> (Recommended)" and "Pick a different path". Do NOT call ask_user_question with a single option (the tool requires ≥2).
   • Two or more entries — present the top 4 filenames as ask_user_question options. The tool automatically appends a Type something. free-text row; do not list it manually.