.claude/skills/resume-handoff/SKILL.md
Continue work from a previous session's handoff document
npx skillsauth add charly-vibes/wai resume-handoffInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Resume work from a handoff document through analysis and verification.
If given a handoff path:
# Read the handoff file
cat handoffs/2026-01-12_14-30-00_oauth-integration.md
If given an issue ID:
# Find handoffs for this issue
ls handoffs/*issue-123* | sort -r | head -1
# Or search in handoff content
grep -l "issue: issue-123" handoffs/*.md | sort -r | head -1
If no parameter provided:
# List recent handoffs
ls -lt handoffs/ | head -10
# Ask user which to resume
From the handoff, identify:
Task Status:
Critical Files:
Key Learnings:
Open Questions:
Next Steps:
# Check if anything changed since handoff
git log --oneline [handoff_commit]..HEAD
# Check current branch
git branch --show-current
# Check working directory status
git status
# Compare current state to handoff state
git diff [handoff_commit]
Read the "Critical Files" section files:
# Read each critical file mentioned
cat src/auth/oauth.ts
cat src/auth/providers.ts
# ... etc
Focus on:
I've analyzed the handoff from [date]. Here's the current situation:
## Original Context
[Summary of what was being worked on]
## Task Status Review
**Completed (from handoff):**
- [x] Task 1 - VERIFIED: Still complete
- [x] Task 2 - VERIFIED: Still complete
**In Progress (from handoff):**
- [ ] Task 3 - STATUS: [describe current state]
**Planned:**
- [ ] Next task 1 [Priority from handoff]
- [ ] Next task 2
## Changes Since Handoff
**Commits since handoff:**
[List any commits between handoff and now]
**Impact:**
[How these changes affect our work]
## Key Learnings Still Applicable
1. [Learning 1] - Still valid because [reason]
2. [Learning 2] - Still valid, see [file:line]
## Questions Needing Resolution
From handoff:
- [ ] [Question 1] - [Current thinking or need decision]
- [ ] [Question 2] - [Can we resolve this now?]
## Recommended Next Action
Based on the handoff priorities and current state:
**Priority 1:** [Action from handoff]
- Reason: [Why this is still the priority]
- Files: [What needs to change]
- Approach: [How to do it]
Shall I proceed with [action]?
Wait for user confirmation, then:
All changes present, no conflicts, proceed normally.
Changes detected since handoff:
Commit a1b2c3d: "refactor: restructure auth module"
- Affects our OAuth implementation
- Provider files moved to src/auth/providers/ directory
- Need to update our understanding
I'll read the new structure before proceeding. Let me check:
- src/auth/providers/ directory contents
- How existing patterns changed
- If our learnings still apply
[After reading]
Updated understanding:
- Providers now in separate directory (not one file)
- Pattern still the same, just reorganized
- Our work can continue with file path updates
Shall I proceed with the original plan, adapting to new structure?
The handoff shows Task 3 was "in progress". Let me verify current state:
[Reads relevant files]
Current state: Task 3 is partially done:
- OAuth flow implemented
- Provider selection NOT YET implemented
- Error states missing
Recommended approach:
1. Complete Task 3 first (finish what was started)
2. Then proceed to planned work
Shall I complete Task 3 before moving to new work?
The handoff is from [3 weeks ago]. Significant changes detected:
Changes:
- 47 commits since handoff
- Auth system refactored
- New OAuth library integrated
This handoff may be too stale to resume directly.
Options:
1. Review changes and adapt the plan
2. Start fresh with current codebase state
3. Cherry-pick specific unfinished work
What would you like to do?
testing
Compare original and distilled prompts to verify the distillation is faithful and lossless. Checks completeness, accuracy, and appropriate conciseness.
development
Implement features following Test-Driven Development methodology. Red-Green-Refactor cycle with phased approach and verification at each step.
development
Orchestrate multi-agent code review with three waves - parallel analysis, cross-validation, and convergence check. Simulates specialist reviewers and synthesizes findings.
development
Apply Steve Yegge's Rule of 5 iterative review to any artifact - code, plans, research, issues, specs, or documents. Five stages from draft through excellence.