session-handoff
Compact this conversation into a handoff file for a fresh agent. Use when launching a clean Claude session or when the user asks for a handoff.
- License 许可
- MIT
- 最近更新
- 2026-09-02
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- session-handoff
- description
- Compact this conversation into a handoff file for a fresh agent. Use when launching a clean Claude session or when the user asks for a handoff.
- argument-hint
- What the next session should focus on
- disable-model-invocation
- true
03 SKILL.md 正文
Session handoff
Write a handoff so a new agent can continue.
Do not use the Write tool (it is sandboxed to the git worktree; /tmp writes are rejected). Do not write into the project.
Pipe markdown to the saver, then launch:
python3 ~/.claude/hooks/prompt-enrich/save_handoff.py <<'EOF'
<!-- PROMPT_CONTRACT_V1 -->
# Prompt contract
...
EOF
The command prints a path under ~/.claude/prompt-enrichment/runs/. Immediately run:
~/.claude/hooks/prompt-enrich/launch-clean-claude.sh --file <that-path>
Then stop. Do not implement in this session.
Must include
- Goal of the next session (use the user’s argument if present)
- Shared understanding (decisions already locked)
- Open questions
- Paths or URLs to specs, plans, ADRs, issues, commits — do not paste those files
- Suggested skills the next agent should load
- Model profile recommendation (
fastcodereasonheavyvision) if known
Start the file with <!-- PROMPT_CONTRACT_V1 -->.
Must not
- Duplicate long specs already on disk
- Include API keys, passwords, tokens, or unnecessary PII
- Instruct the next agent to re-run the grill unless the frontier is still non-empty
- Write under
/tmpor$TMPDIR
04 同仓库更多 Skills
verify-before-done
Use before claiming work is complete, fixed, or passing, and before commit or PR. Run the proof command in this turn.
token-playbook
Token budget for Claude Code. Use when shrinking CLAUDE.md, choosing skills vs rules vs MCP, compressing tool output, or cutting always-on context.
test-writer
Write failing tests from a technical spec and public contracts only. Use in /dev-loop test-writer stage. Do not read implementation sources or write production code.
tdd
Use when implementing a feature or bugfix, before writing production code. Test first, watch it fail, then implement. Vertical slices at public seams.
systematic-debugging
Use when hitting a bug, test failure, or unexpected behavior, before proposing a fix. Find root cause first.
story-spec
Turn a Jira story into a technical spec via grill. Use in the spec stage of /dev-loop. Do not implement.