snapsynapse/skill-provenance / skills/handoff
handoff
UnverifiedGenerate a handoff note summarizing skill project state for a future session or collaborator. Use when crossing a non-persistent boundary (e.g., Chat upload), ending a session that made significant decisions, or when the user explicitly asks for a handoff note. Triggers on: "generate a handoff", "write a handoff note", "summarize for next session", "prepare handoff", "what should the next session know".
Skill Provenance: Handoff
Generate a structured handoff note that captures project state for the next session or a collaborator picking up the work.
When to use
Run /skill-provenance:handoff when:
- Crossing a non-persistent boundary (e.g., uploading to Claude Chat where filesystem state won't carry over).
- The session made significant decisions not yet reflected in files.
- The user explicitly asks for a handoff note.
- A collaborator or future session needs context beyond what the manifest and changelog provide.
When NOT to use: In filesystem-native environments (Claude Code, IDE) with a current manifest, changelog, and git history, a handoff note is usually unnecessary. The manifest and changelog are the handoff.
Protocol
-
Read current state. Load
MANIFEST.yamlandCHANGELOG.mdto understand the bundle's current version and recent history. -
Generate the handoff note with these sections:
- Current bundle version — name and semver from the manifest.
- What was accomplished this session — summarize the work done, not just files changed.
- What is stale and needs attention — files flagged as behind or not updated this session.
- What the next session should do first — concrete first action, not vague guidance.
- Decisions made but not yet reflected in files — architecture choices, deferred items, scope decisions that someone reading only the code wouldn't know about.
- Per-file change summaries — for each file modified this session, a brief description of what changed (section added, field removed, logic rewritten). More granular than the changelog entry; helps the next session verify work without re-reading every file.
-
Replace, don't accumulate. A new handoff note replaces the previous one. Previous handoffs live in changelog history. Don't maintain a chain of handoff files.
-
Placement. Write the handoff note as a markdown file in the bundle directory (e.g.,
HANDOFF.md). Track it in the manifest withrole: handoffif the user wants it to persist across sessions.
Conventions referenced
- Handoff notes are optional convenience artifacts, not required by the spec.
- The manifest and changelog are always the authoritative record. The handoff note provides context and intent that structured metadata cannot.
- In environments with persistent filesystems and git, prefer the manifest and changelog over handoff notes.
For the full spec: https://skillprovenance.dev
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 467k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |