resume-handoff

Resume work from a handoff document

Prerequisites

# Check project setup (thoughts, CLAUDE.md snippet, config)
if [[ -f "${CLAUDE_PLUGIN_ROOT}/scripts/check-project-setup.sh" ]]; then
  "${CLAUDE_PLUGIN_ROOT}/scripts/check-project-setup.sh" || exit 1
fi

# Auto-discover most recent handoff. Three-source waterfall:
#   1. CATALYST_HANDOFF_PATH env var (CTL-484 continuation-worker contract —
#      set by orchestrate-revive's continuation branch when it spawns
#      `claude --bg --resume` after a turn-cap exhaustion).
#   2. workflow-context.sh recent handoffs (interactive flows).
#   3. (handled later in Step 4) interactive picker.
RECENT_HANDOFF=""
if [[ -n "${CATALYST_HANDOFF_PATH:-}" && -f "$CATALYST_HANDOFF_PATH" ]]; then
  RECENT_HANDOFF="$CATALYST_HANDOFF_PATH"
elif [[ -f "${CLAUDE_PLUGIN_ROOT}/scripts/workflow-context.sh" ]]; then
  RECENT_HANDOFF=$("${CLAUDE_PLUGIN_ROOT}/scripts/workflow-context.sh" recent handoffs)
fi
if [[ -n "$RECENT_HANDOFF" ]]; then
  if [[ "${CATALYST_IS_CONTINUATION:-}" == "true" ]]; then
    echo "📋 Continuation worker — resuming from CATALYST_HANDOFF_PATH: $RECENT_HANDOFF"
  else
    echo "📋 Auto-discovered recent handoff: $RECENT_HANDOFF"
  fi
else
  echo "⚠️ No recent handoff found in workflow context or filesystem"
fi

Configuration Note

This command uses ticket references like PROJ-123. Replace PROJ with your Linear team's ticket prefix:

• Read from .catalyst/config.json if available
• Otherwise use a generic format like TICKET-XXX
• Examples: ENG-123, FEAT-456, BUG-789

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.

Initial Response

Auto-discovery has already run in Prerequisites above. Check its output and follow this priority:

1. If CATALYST_IS_CONTINUATION=true AND CATALYST_HANDOFF_PATH is set (CTL-484

continuation-worker contract from orchestrate-revive): the env-var hook in Prerequisites already selected the handoff. Skip directly to Step 3 without prompting the user — this is a background-dispatched continuation, not an interactive resume. Confirmation gates would hang the worker.

1. If user provided a file path as parameter: Use the provided path (user override). Skip to

Step 3.

1. If user provided a ticket number (like PROJ-123):
2. Run humanlayer thoughts sync to ensure thoughts/ is up to date
3. Look in thoughts/shared/handoffs/PROJ-123/ directory
4. List all handoffs for that ticket
5. If multiple exist, use the most recent (by timestamp in filename YYYY-MM-DD_HH-MM-SS)
6. If none exist, tell user and wait for input
7. Skip to Step 3

1. If no parameters provided AND Prerequisites output shows a discovered handoff (📋):
2. Show user the discovered path
3. Ask: "Proceed with this handoff? [Y/n]"
4. If yes: use it and skip to Step 3
5. If no: proceed to option 4

1. If no parameters AND Prerequisites shows no handoff found (⚠️):
2. List available handoffs from thoughts/shared/handoffs/
3. Show most recent 5 handoffs with dates
4. Ask user which one to use
5. Wait for user input with path or ticket number

STEP 3: Analyze the handoff

Once you have a handoff path:

• Read the handoff document FULLY (no limit/offset)
• Immediately read any research or plan documents it references
• Do NOT use sub-agents to read these critical files
• Ingest all context from the handoff
• Propose course of action to user
• Get confirmation before proceeding

Process Steps

Step 1: Read and Analyze Handoff

1. Read handoff document completely:
2. Use the Read tool WITHOUT limit/offset parameters
3. Extract all sections:
4. Task(s) and their statuses
5. Recent changes
6. Learnings
7. Artifacts
8. Action items and next steps
9. Other notes

1. Spawn focused research tasks: Based on the handoff content, spawn parallel research tasks to

verify current state:

``` Task 1 - Verify recent changes: Check if the recent changes mentioned in the handoff still exist.

1. Verify files mentioned in "Recent changes" section
2. Check if the described changes are still present
3. Look for any subsequent modifications
4. Identify any conflicts or regressions

Use tools: Read, Grep, Glob Return: Current state of recent changes with file:line references ```

``` Task 2 - Validate current codebase state: Verify the current state against what's described in the handoff.

1. Check files mentioned in "Learnings" section
2. Verify patterns and implementations still exist
3. Look for any breaking changes since handoff
4. Identify new related code added since handoff

Use tools: Read, Grep, Glob Return: Validation results and any discrepancies found ```

``` Task 3 - Gather artifact context: Read all artifacts mentioned in the handoff.

1. Read feature documents listed in "Artifacts"
2. Read implementation plans referenced
3. Read any research documents mentioned
4. Extract key requirements and decisions

Use tools: Read Return: Summary of artifact contents and key decisions ```

1. Wait for ALL sub-tasks to complete before proceeding

1. Read critical files identified:
2. Read files from "Learnings" section completely
3. Read files from "Recent changes" to understand modifications
4. Read any new related files discovered during research

Step 2: Synthesize and Present Analysis

1. Present comprehensive analysis:

``` I've analyzed the handoff from [date] by [researcher]. Here's the current situation:

Original Tasks:

• [Task 1]: [Status from handoff] → [Current verification]
• [Task 2]: [Status from handoff] → [Current verification]

Key Learnings Validated:

• [Learning with file:line reference] - [Still valid/Changed]
• [Pattern discovered] - [Still applicable/Modified]

Recent Changes Status:

• [Change 1] - [Verified present/Missing/Modified]
• [Change 2] - [Verified present/Missing/Modified]

Artifacts Reviewed:

• [Document 1]: [Key takeaway]
• [Document 2]: [Key takeaway]

Recommended Next Actions: Based on the handoff's action items and current state:

1. [Most logical next step based on handoff]
2. [Second priority action]
3. [Additional tasks discovered]

Potential Issues Identified:

• [Any conflicts or regressions found]
• [Missing dependencies or broken code]

Shall I proceed with [recommended action 1], or would you like to adjust the approach? ```

1. Get confirmation before proceeding

Step 3: Create Action Plan

1. Use TodoWrite to create task list:
2. Convert action items from handoff into todos
3. Add any new tasks discovered during analysis
4. Prioritize based on dependencies and handoff guidance

1. Present the plan:

``` I've created a task list based on the handoff and current analysis:

[Show todo list]

Ready to begin with the first task: [task description]? ```

Step 4: Begin Implementation

1. Start with the first approved task
2. Reference learnings from handoff throughout implementation
3. Apply patterns and approaches documented in the handoff
4. Update progress as tasks are completed

CLI Tools

When you need to fetch ticket context from Linear (e.g., reading a ticket referenced in the handoff), use the Linearis CLI. For exact syntax, run linearis issues usage or see /catalyst-dev:linearis — do not guess commands.

Guidelines

1. Be Thorough in Analysis:
2. Read the entire handoff document first
3. Verify ALL mentioned changes still exist
4. Check for any regressions or conflicts
5. Read all referenced artifacts

1. Be Interactive:
2. Present findings before starting work
3. Ge