forward

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

/forward - Handoff to Next Session

/forward - 交接至下一次会话

Create context for next session, then enter plan mode to define next steps.

为下一次会话创建上下文，然后进入计划模式以定义后续步骤。

Usage

使用方法

/forward              # Create handoff, show plan, wait for approval
/forward asap         # Create handoff + commit immediately (no approval needed)
/forward --only       # Create handoff only, skip plan mode

/forward              # Create handoff, show plan, wait for approval
/forward asap         # Create handoff + commit immediately (no approval needed)
/forward --only       # Create handoff only, skip plan mode

Steps

步骤

Git status: Check uncommitted work
Session summary: What we did (from memory)
Pending items: What's left
Next steps: Specific actions

Git status：检查未提交的工作
会话总结：我们已完成的工作（基于记忆）
待办事项：剩余未完成的内容
后续步骤：具体行动

Output

输出

Resolve vault path first:

bash

PSI=$(readlink -f ψ 2>/dev/null || echo "ψ")

Write to:

$PSI/inbox/handoff/YYYY-MM-DD_HH-MM_slug.md

IMPORTANT: Always use the resolved

$PSI

path, never the

ψ/

symlink directly. This ensures handoffs go to the project's vault (wherever ψ points). Do NOT

git add

vault files — they are shared state, not committed to repos.

markdown

undefined

首先解析Vault路径：

bash

PSI=$(readlink -f ψ 2>/dev/null || echo "ψ")

写入至：

$PSI/inbox/handoff/YYYY-MM-DD_HH-MM_slug.md

重要提示：请始终使用解析后的

$PSI

路径，切勿直接使用

ψ/

符号链接。这能确保交接内容存入项目的Vault（无论ψ指向何处）。请勿对Vault文件执行

git add

操作——它们是共享状态，无需提交至代码仓库。

markdown

undefined

Handoff: [Session Focus]

Date: YYYY-MM-DD HH:MM Context: [%]

What We Did

[Accomplishment 1]
[Accomplishment 2]

[Accomplishment 1]
[Accomplishment 2]

Pending

Item 1
Item 2

Item 1
Item 2

Next Session

Specific action 1
Specific action 2

Specific action 1
Specific action 2

Key Files

[Important file 1]
[Important file 2]

undefined

[Important file 1]
[Important file 2]

undefined

Then: MUST Enter Plan Mode

随后：必须进入计划模式

CRITICAL: You MUST call

EnterPlanMode

after writing the handoff. This is NOT optional. The whole point of /forward is to show the user a plan they can approve for the next session.

Do NOT commit the handoff file — it lives in the vault, not the repo. After writing the handoff, gather cleanup context:

bash

undefined

关键要求：在完成交接内容的写入后，你必须调用

EnterPlanMode

。这是强制要求，不可省略。

/forward

命令的核心目的是向用户展示一份可供其审批的下一次会话计划。

请勿提交交接文件——它存储在Vault中，而非代码仓库内。完成交接内容写入后，收集清理上下文信息：

bash

undefined

Check for things next session might need to clean up

git status --short git branch --list | grep -v '^* main$' | grep -v '^ main$' gh pr list --state open --json number,title,headRefName --jq '.[] | "#(.number) (.title) ((.headRefName))"' 2>/dev/null gh issue list --state open --limit 5 --json number,title --jq '.[] | "#(.number) (.title)"' 2>/dev/null


Then:

1. **Call `EnterPlanMode`** tool
3. In plan mode, write a plan file with:
   - What we accomplished this session
   - Pending items carried forward
   - Cleanup needed (stale branches, open PRs, uncommitted files)
   - Next session goals and scope
   - Reference to handoff file path
   - **Always end plan with a choice table:**

```markdown


随后：

1. **调用`EnterPlanMode`工具**
3. 在计划模式下，编写一份包含以下内容的计划文件：
   - 本次会话已完成的工作
   - 延续至下一次的待办事项
   - 需要清理的内容（过时分支、未合并PR、未提交文件）
   - 下一次会话的目标与范围
   - 交接文件的路径引用
   - **必须在计划末尾添加选择表格：**

```markdown

Next Session: Pick Your Path

Option	Command	What It Does
Continue	`/recap`	Pick up where we left off
Clean up first	See cleanup list below, then `/recap`	Merge PRs, delete branches, close issues, then continue
Fresh start	`/recap --quick`	Minimal context, start something new

Option	Command	What It Does
Continue	`/recap`	Pick up where we left off
Clean up first	See cleanup list below, then `/recap`	Merge PRs, delete branches, close issues, then continue
Fresh start	`/recap --quick`	Minimal context, start something new

Cleanup Checklist (if any)

[Open PR to merge]
[Stale branch to delete]
[Issue to close]
[Uncommitted work to commit or stash]


4. **Call `ExitPlanMode`** — user sees the built-in plan approval UI

The user gets the standard plan approval screen with options to approve, modify, or reject. This is the proper way to show plans.

If user calls `/forward` again — just show the existing plan, do not re-create the handoff file.

[Open PR to merge]
[Stale branch to delete]
[Issue to close]
[Uncommitted work to commit or stash]


4. **调用`ExitPlanMode`**——用户将看到内置的计划审批界面

用户会看到标准的计划审批界面，包含批准、修改或拒绝选项。这是展示计划的正确方式。

如果用户再次调用`/forward`——仅展示已有的计划，无需重新创建交接文件。

ASAP Mode

ASAP模式

If user says

/forward asap

/forward now

Write handoff file
Immediately commit and push — no approval needed
Skip plan mode
User wants to close fast

当用户输入

/forward asap

或

/forward now

时：

写入交接文件
立即提交并推送——无需审批
跳过计划模式
用户希望快速结束会话

Skip Plan Mode

跳过计划模式

If user says

/forward --only

Skip plan mode after commit
Just tell user: "💡 Run /plan to plan next session"

ARGUMENTS: $ARGUMENTS

当用户输入

/forward --only

时：

提交后跳过计划模式
只需告知用户："💡 运行/plan来规划下一次会话"

参数：$ARGUMENTS