Resume Handoff

If $ARGUMENTS matches a ticket ID ([A-Z]+-[0-9]+):

• Set TICKET to that ID
• Run ~/.claude/scripts/ticket-metadata.sh for repo context
• Set THOUGHTS_DIR to ~/Obsidian/second-brain/thoughts/{REPO}/{TICKET}/
• Look for {THOUGHTS_DIR}/handoff.md

If $ARGUMENTS is a file path:

• Use the path directly
• Derive THOUGHTS_DIR from the path's parent directory

If the handoff file does not exist: Respond with: "Could not find the handoff at {path}. Provide the full path, or check if it exists." Then stop.

Step 2: Read and Validate

1. Read the handoff document completely — use the Read tool without limit/offset parameters. Extract all sections: tasks, recent changes, learnings, artifacts, action items, other notes.

2. Read all linked documents in {THOUGHTS_DIR}/:

   • plan.md — implementation plan (if referenced)
   • research.md — background research (if referenced)
   • Any other documents mentioned in the handoff
   • Do NOT use sub-agents for these critical reads — read them directly

3. Read files referenced in the handoff:

   • Files from "Recent Changes" and "Learnings" sections
   • Files from "Artifacts" section
   • Any new related files discovered

4. Verify current state against handoff:

   • Do referenced files still exist? Have they changed?
   • Are documented patterns still valid?
   • Has new related code landed since the handoff?
   • Read references/conventions.md for validation rules and divergence protocol

Step 3: Present Analysis

Present a structured analysis of the handoff state vs current reality:

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

Tasks:
- [Task]: [handoff status] -> [current verification]

Key Learnings Validated:
- [Learning with file:line] — [still valid / changed]

Recent Changes:
- [Change] — [verified present / missing / modified]

Divergences Found:
- [If any, using conventions.md divergence format]

Recommended Next Actions:
1. [Most logical next step]
2. [Second priority]

Shall I proceed with [recommended action], or adjust the approach?

Then wait for the user's response before proceeding.

Step 4: Create Action Plan

1. Use TodoWrite to create a task list from:

   • Action items from the handoff
   • New tasks discovered during validation
   • Prioritized based on dependencies and handoff guidance

2. 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]?

Then wait for the user's response before proceeding.

Step 5: Begin Work

1. Start with the first approved task.
2. Reference handoff learnings throughout implementation — these save re-discovery time.
3. Apply documented patterns and approaches.
4. Update TodoWrite progress as tasks complete.

Step 6: Completion

After all handoff action items are addressed:

1. Summarize what was accomplished with file:line references.
2. Note any open items that remain or emerged during work.
3. Suggest next steps — if the session is long, suggest /create-handoff to preserve new context.

All handoff tasks complete.

Summary:
- [What was done, with file:line references]

Remaining:
- [Any open items or follow-ups]

Suggested next steps:
- [Action item or /create-handoff suggestion]

Important Notes

• Read the entire handoff and all linked documents before acting — incomplete reads produce incomplete context restoration
• Do NOT use sub-agents to read critical context files — read them directly
• Use TodoWrite to maintain task continuity through the session
• Pay special attention to "Learnings" — they capture non-obvious knowledge that would take time to re-discover