切换
- 作者仓库星标 34
- 作者仓库 dotfiles
- 领域
- 工程开发
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @steveclarke · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- macOS · Linux
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
# Handoff — Context-to-Context Continuation
Write durable continuation notes to the project, generate a resume prompt, and copy it to the clipboard so a fresh Claude Code session can pick up exactly where this one left off.
## Why This Matters
Claude Code sessions have finite context. Complex multi-session work (migrations, large features, multi-phase plans) needs a way to pass state between sessions without losing momentum. The handoff captures what a fresh session needs to know — not everything that happened, but everything that matters going forward.
## Process
### 1. Gather State
Before writing anything, collect this information from the current session:
**What's done:**
- Tasks/phases completed
- Files created or modified (high-level, not every file)
- Commits made and pushed (branch name, remote status)
**What's not done:**
- Remaining tasks or phases
- Known issues, bugs encountered and fixed (so the next session doesn't repeat them)
- Anything partially started
**Key decisions made:**
- Architectural choices the user approved
- Patterns established that future work should follow
- Things that were tried and didn't work
**Practical details:**
- Repo location, branch, remote
- Dev environment state (running? needs setup?)
- Test credentials if relevant
- Relevant file paths (specs, plans, docs)
If the next task isn't obvious from context, ask: **"What should the next session focus on?"**
### 2. Write Continuation File
Write a continuation notes file to the project. Location preference:
1. `docs/superpowers/plans/` if it exists (superpowers convention)
2. `docs/` if it exists
3. Project root as `CONTINUATION.md`
**Filename:** `YYYY-MM-DD-<topic>-continuation.md`
Structure:
```markdown
# [Topic] — Continuation Notes
## Current State (YYYY-MM-DD)
[1-2 sentence summary of where things stand]
### What's Working
- [bullet list of completed work]
### What's NOT Working Yet
- [bullet list of remaining work, known gaps]
### Key Decisions
- [decisions the user approved that constrain future work]
### Bugs Fixed (Don't Repeat These)
- [gotchas encountered — saves the next session from re-discovering them]
### Practical Details
- Repo: [path] (GitHub: [org/repo], branch: [branch])
- Dev stack: [running? how to start?]
- Credentials: [if needed for testing]
## Next: [What To Do]
[Brief description of what the next session should do first]
### Key Files to Read
- [file path] — [what it contains and why it matters]
### Pattern to Follow
[If a pattern was established, show a brief example so the next session
doesn't have to rediscover it]
```
Keep it concise — this is a briefing, not a history. The next session should be able to read this in under a minute and know exactly what to do.
### 3. Commit and Push
```bash
git add <continuation-file>
git commit -m "docs: add continuation notes for handoff"
git push
```
### 4. Generate Resume Prompt
Craft a resume prompt — the exact text the user will paste into a fresh session. It should:
- Be self-contained (no "see above" references)
- Point to 2-4 files max (the continuation notes + key docs)
- State the next task clearly
- Be under 10 lines
**Template:**
```
I'm [brief context]. [Phase/step] is complete. Read these files to get up to speed, then [next action]:
1. [continuation file path] (where we left off)
2. [spec or plan path] (full context)
3. [CLAUDE.md or other key doc] (conventions)
[One sentence about what to do next.]
```
### 5. Copy to Clipboard
```bash
echo "<resume prompt>" | pbcopy # macOS
# or: echo "<resume prompt>" | xclip -selection clipboard # Linux
```
Tell the user: **"Resume prompt copied to clipboard. Start a fresh session in `[repo path]` and paste it."**
## What NOT to Include
- Full conversation history or play-by-play
- Raw error logs (summarize the fix, not the stack trace)
- File contents that can be read from disk
- Implementation details that are in the code
- Anything the fresh session can derive by reading the codebase
The continuation file supplements `git log` and the code itself — it captures context that isn't in either place.
章节与文件索引
按说明文件中的顺序排列。
为什么这很重要
1. 收集状态
2. 写入延续文件
4. 生成简历提示
5.复制到剪贴板
文件/命令 -> docs/superpowers/plans/ · docs/ · CONTINUATION.md · YYYY-MM-DD-<topic>-continuation.md · [repo path] · git log
内容校验值 -> 30e24e2d24ba
当前原文的自动摘译,尚未人工审校。
为什么这很重要
克劳德代码会话的上下文是有限的。复杂的多会话工作(迁移、大型功能、多阶段计划)需要一种在会话之间传递状态而不失去动力的方法。交接捕获了新的会话需要了解的内容——不是发生的所有事情,而是未来重要的所有事情。
1. 收集状态
在编写任何内容之前,请从当前会话中收集以下信息: 已完成的操作: 已完成的任务/阶段 创建或修改的文件(高级,不是每个文件) 进行和推送的提交(分支名称、远程状态)
2. 写入延续文件
将延续注释文件写入项目。位置首选项:
docs/superpowers/plans/(如果存在)(超能力约定)docs/(如果存在)项目根目录为CONTINUATION.md文件名:YYYY-MM-DD-<topic>-continuation.md4. 生成简历提示
制作恢复提示 - 用户将粘贴到新会话中的确切文本。它应该: 独立(无“参见上文”引用) 最多指向 2-4 个文件(续注 + 关键文档) 清楚地说明下一个任务 少于 10 行
5.复制到剪贴板
告诉用户:“恢复提示已复制到剪贴板。在
[repo path]中启动一个新会话并粘贴它。”