handoff

Writes end-of-turn handoff summaries and updates sprint status, story files, and GitHub issues.

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/watchthelight/shatterfish --skill handoff-watchthelight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/watchthelight/shatterfish/tree/main/.claude/skills/handoff
Command: npx skills add https://github.com/watchthelight/shatterfish --skill handoff-watchthelight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Development sessions on the Shatterfish project lose context between turns because state lives in chat instead of on disk. This Skill standardizes the end-of-turn handoff so every session ends with updated tracking artifacts and a consistent summary message. ## Core Features & Use Cases - Artifact Updates First: Updates sprint-status.yaml, the story spec file, the GitHub issue, docs/roadmap.md, docs/ideas.md, and the memory note before writing the handoff message. - Standard Message Format: Produces a fixed handoff template covering done items with links, artifacts changed, verification results, incidents, the exact next step, and blocking questions. - Use Case: At the end of a coding session on a Shatterfish story, invoke the handoff to close out the GitHub issue comment, refresh sprint status, and leave a readable summary so the next session can resume without re-reading the whole conversation. ## Quick Start Ask the assistant to wrap up the session and write the handoff for the current story.

Frequently Asked Questions about handoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write an end-of-session handoff for a coding project?

Update all tracking artifacts first, then write a summary with sections for completed work with links, artifacts changed, verification results, incidents, one exact next step, and blocking questions. Keep it readable by someone who did not watch the session.

What should a sprint handoff summary include?

A handoff summary should include what was done with PR and commit links, which artifacts changed, build and test verification results, any incidents, exactly one next step, and blocking questions with consequences of each answer.

Does the handoff update GitHub issues automatically?

The workflow directs updates to the GitHub issue for the watchthelight/shatterfish repository, adding a comment with the PR link and status for stories, or ticking session boxes on the E0 epic issue for bootstrap sessions.

When should I trigger the handoff workflow?

Trigger it at the end of every turn, when you say hand off or wrap up, or when invoking /handoff. Never hand off an unbuildable tree; commit and push everything or explain what is not committed and why.

What happens if sprint-status.yaml does not exist?

The sprint-status.yaml update is conditional on the file existing. If present, the story status must match reality and last_updated must be refreshed; otherwise that step is skipped and the remaining artifacts are still updated.