Help us improve
Share bugs, ideas, or general feedback.
From workflows
Creates structured handoff documents for pausing and resuming data science workflow sessions. Reads state files and git history to capture progress, decisions, and next steps, minimizing re-orientation cost.
How this skill is triggered — by the user, by Claude, or both
Slash command
/workflows:ds-handoffThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Announce: "Using ds-handoff to capture session state for clean resumption."
Share bugs, ideas, or general feedback.
Announce: "Using ds-handoff to capture session state for clean resumption."
Capture current DS workflow state into .planning/HANDOFF.md so a fresh session can resume exactly where this one left off.
NO HANDOFF WITHOUT READING STATE FIRST. This is not negotiable.
Before writing .planning/HANDOFF.md, you MUST:
.planning/SPEC.md (if exists) — understand the requirements.planning/PLAN.md (if exists) — understand task breakdown and progress.planning/LEARNINGS.md (if exists) — understand pipeline state and discoveriesIf you catch yourself writing a handoff without reading state files first, STOP.
Read all available state files to understand where we are:
1. Read .planning/SPEC.md → requirements and success criteria
2. Read .planning/PLAN.md → task breakdown and approach
3. Read .planning/LEARNINGS.md → pipeline state, row counts, discoveries
4. Scan recent git log → what's been committed
5. Check for uncommitted changes → what's in-flight
Run:
# Check for uncommitted work
git status --short 2>/dev/null
# Recent commits in this session
git log --oneline -10 2>/dev/null
Description: ds-handoff: read current workflow and git state
From the state files and git history, determine:
Write .planning/HANDOFF.md using the template below. Every field is mandatory.
Write as if briefing a colleague who has never seen this project. Include:
Checkpoint type: human-verify (handoff completeness is machine-verifiable)
After writing, verify the handoff is complete:
1. IDENTIFY: .planning/HANDOFF.md exists
2. READ: Re-read the handoff document
3. VERIFY: Contains all sections (Current State, Completed Work, Remaining Work, Decisions, Next Action)
4. VERIFY: "Next Action" is specific enough to start immediately
5. VERIFY: Frontmatter phase/task numbers are accurate
If any section is empty or vague, fix it before confirming handoff.
---
phase: [current phase number]
phase_name: [brainstorm|plan|implement|validate|review|verify]
task: [current task number, 0 if between tasks]
total_tasks: [N from PLAN.md]
status: paused
context_remaining: [approx % context left when handing off — lets a resuming session triage scope]
decisions_count: [N — number of entries in the Decisions Made section below]
last_updated: [ISO 8601]
---
# Session Handoff
## Current State
[Where exactly we are — the immediate context a new session needs.
Include: current file being edited, current pipeline stage,
current phase gate status. Be specific.]
## Completed Work
- [x] Task 1: [name] — Done ([brief note on what was done])
- [x] Task 2: [name] — Done
- [ ] Task 3: [name] — In progress ([what's done, what's not])
## Remaining Work
- Task 3: [what specifically remains]
- Task 4: [name] — Not started
- Task 5: [name] — Not started
## Decisions Made
- [Decision]: [what was decided and WHY]
- [Decision]: [what was decided and WHY]
## Rejected Approaches
- [Approach]: [why it was rejected — saves the next session from re-exploring dead ends]
## Blockers
- [Blocker]: [status/workaround found]
- (none) — if no blockers
## Uncommitted Changes
- [file]: [what was changed and why]
- (none) — if all work is committed
## Next Action
Start with: [specific first action when resuming — not "continue task 3" but
"load data/processed/merged_panel.parquet and verify the winsorization in
src/clean.py produced expected row counts per LEARNINGS.md, then run DQ3
on the output"]
After writing and verifying .planning/HANDOFF.md:
Announce: "Session handoff saved to .planning/HANDOFF.md. Next session will detect it automatically and offer to resume."
Report to user:
Handoff saved:
- Phase: [phase_name]
- Task: [N] of [total]
- Next action: [one-line summary]
Resume by starting /ds in this project — it will detect the handoff.
npx claudepluginhub edwinhu/workflows --plugin workflowsCaptures session state into HANDOFF.md for clean resumption in a new Claude Code session. Reads spec, plan, and git status before writing.
Creates structured handoff documents with session accomplishments, pause points, and key files for seamless session continuation.
Produces a handoff document so a fresh agent can continue work from the current session. Handles both mid-arc continuation and backlog handoffs.