mjmorales/handoff
skills/handoff/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add mjmorales/claude-prove handoffInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 19, 2026, 4:12 AM5.5s2 files scanned
SKILL.md
- name:
- handoff
- description:
- >
- argument-hint:
- [optional: brief note about what to hand off]
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
$ARGUMENTSand 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:
- Active run (state.json + plan.json under
.prove/runs/<branch>/<slug>/): reference the specific step id fromscripts/prove-run show state .prove/decisions/has entries: mention the most recent decision- No prove artifacts: summarize from git state
$ARGUMENTSprovided: 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-agentfirst - 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.
Related Skills
mjmorales/janitor
tools
VerifiedTrustedCommunity
Clean and compact prove's durable memory layers — team Lore, the Codex (scrum decisions), annotations, and contributor artifacts — keeping the tribal knowledge that grows team accuracy and folding away the rot. Triggers on "janitor", "clean the lore", "compact the lore", "compact the codex", "memory cleanup", "clean up team memory", "prune stale decisions", "tidy tribal knowledge", "lore cleanup". You are the driver: the CLI emits inventories and executes writes; the `memory-janitor` agent judges each entry; a per-team batch gate approves; nothing is ever deleted — consolidation, promotion, and supersession only.
2SKILL.mdUpdated Jun 9, 2026
mjmorales/smart-compaction
testing
VerifiedTrustedCommunity
Anchor session context into prove primitives before compaction and rehydrate from them after. Built-in compaction summarizes by recency and drops the claude-prove state an agent needs to reorient; this skill externalizes volatile context into durable anchors (scrum tasks, decisions, run-state, a compact-anchors pointer file) pre-compact, then runs a deterministic reorientation sequence post-compact. Use before a manual /compact, when context is about to auto-compact, or immediately after a compaction. Triggers on "smart compact", "prepare for compaction", "anchor before compact", "context is getting long", "rehydrate", "reorient after compact".
2SKILL.mdUpdated Jun 5, 2026
mjmorales/run-migrate
tools
VerifiedTrustedCommunity
Apply model-driven CONTENT reshaping to stored run artifacts that sit behind the current schema, on explicit operator invocation only. Triggers on "migrate runs", "migrate run artifacts", "run content migration", "reshape run artifacts", "bring runs to current schema". You are the driver: the `run-state migrate-runs` CLI mechanically detects which artifacts are behind and emits a plan naming each one plus its migration-instruction file; you read the instructions and reshape the prose/findings, gated by the operator. The deterministic `schema migrate` handles structural column moves; this skill covers only the content reshaping beyond them. Never run as a background or resident loop — only when the operator asks.
2SKILL.mdUpdated Jun 5, 2026
mjmorales/reasoning-brief
tools
VerifiedTrustedCommunity
Synthesize the 7-section risk-forward Review Brief from a run's reasoning log. Triggers on "reasoning brief", "review brief", "synthesize the brief", "generate the brief", "brief the run", "brief for review", "story brief". You are the driver: the `acb brief` CLI renders a mechanical preservation-safe backbone and proves preservation; you synthesize the narrative prose (summary + changes), single-pass or multipass over episode chunks, then gate it through Stage-1 (mechanical, blocking) and Stage-2 (prose judge, advisory).
2SKILL.mdUpdated Jun 5, 2026