Skill

handoff

Create a focused handoff prompt file for clean conversation-level handoffs. Deterministically assembles context from git state and prove artifacts, generates a small LLM pickup note, recommends the right agent, and outputs the exact command to start a fresh session. Use when hitting context limits, transitioning between phases, or wanting a clean restart without losing context.

From prove

Install

Run in your terminal

npx claudepluginhub mjmorales/claude-prove --plugin prove

Tool Access

This skill uses the workspace's default tool permissions.

Supporting Assets

View in Repository

scripts/gather-context.sh

Skill Content

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.8k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

bmad-help

Analyzes BMad project state from catalog CSV, configs, artifacts, and query to recommend next skills or answer questions. Useful for help requests, 'what next', or starting BMad.

bmad-pro-skills

43.8k

Stats

Stars0

Forks0

Last CommitMar 29, 2026

Actions

View Source View Plugin View on GitHub View README

Handoff: $ARGUMENTS

Create .prove/handoff.md so a fresh session picks up where this one left off.

Rules

Reference files by path, do not inline content. Target ~100-200 lines total.
Each handoff is a fresh snapshot. Do not append to or reference prior handoffs.
Do not ask the user questions. Use $ARGUMENTS and conversation context.
Cap: max 50 files in "Files Modified", max 7 in "Files to Read First".

Phase 1: Gather Context

bash "$PLUGIN_DIR/skills/handoff/scripts/gather-context.sh" "$PROJECT_ROOT" "$PLUGIN_DIR"

Capture the full output -- this becomes the body of the handoff file. If $ARGUMENTS is provided, note it as additional context for Phase 2.

Phase 2: Pickup Note

Generate a 3-5 sentence pickup note -- the only LLM-generated part. Answer:

Next action -- immediate work for the new agent
Blockers/gotchas -- non-obvious issues that would trip up a fresh agent
Key decisions -- choices from this session not captured in artifacts

Conditional additions:

.prove/TASK_PLAN.md exists: reference the specific step to resume
.prove/decisions/ has entries: mention the most recent decision
No prove artifacts: summarize from git state
$ARGUMENTS provided: incorporate it

Be concrete: "Fix the failing test in auth/middleware.test.ts caused by the new token format" over "Continue working on auth."

Phase 3: Agent Recommendation

If agents/ exists, read .md files and parse frontmatter description. Match against the pickup note's work domain:

Match found: claude --agent agents/<name>.md --prompt-file .prove/handoff.md
No match, specialized work: suggest /prove:create:create-agent first
No agents dir or general work: claude --prompt-file .prove/handoff.md

Phase 4: Write & Output

Write .prove/handoff.md:

# Handoff Context
<!-- Auto-generated by /prove:handoff. Safe to delete after use. -->

## Pickup Note
<from Phase 2>

<gathered context from Phase 1 -- State, Files Modified, Prove Artifacts, Discovery>

## Files to Read First
<3-7 files, priority-ordered with one-line rationale.
 Priority: task plan > modified files > decision records > config>

## Instructions
1. Read the files listed in "Files to Read First" before starting
2. <specific resume point from the pickup note>
3. Run validation before committing: <validator commands from .claude/.prove.json>
4. When done, delete: `rm .prove/handoff.md`

Output to the user: confirm file written, show the recommended command, explain agent match if applicable.