handoff-out
Use when preparing to move active Miller-backed work to another harness, model, or session and the receiving agent needs a self-contained resume packet.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when preparing to move active Miller-backed work to another harness, model, or session and the receiving agent needs a self-contained resume packet.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
Use before changing existing indexed files with Miller edit, especially symbol rewrites, text replacements, renames, or refactors.
Use when an agent needs extractor-recognized code-shape facts such as routes, htmx attributes, Alpine directives, SQL DDL/DML, or data-document structure.
Use when starting a Miller task, choosing a Miller tool, or choosing a Miller search mode.
Use when tracing Miller bridge paths in supported providers: dotnet-web URL literals and fetch/axios client requests to ASP.NET signals, client requests to Next.js route handlers or Nuxt server routes, Next.js/Nuxt route references to file routes, Vue/React references to route definitions, or backend-http client requests to Express/FastAPI/Flask/Django/Spring/Go/gin/echo/Rails/NestJS/Laravel/Phoenix/axum/actix/Symfony/Ktor route facts.
Use when orienting on an unfamiliar code area with Miller, explaining a module, finding entry points, or gathering context before a change.
Use when assessing blast radius with Miller, choosing tests for a change, answering who uses a symbol, or planning a refactor.
| name | handoff-out |
| description | Use when preparing to move active Miller-backed work to another harness, model, or session and the receiving agent needs a self-contained resume packet. |
| user-invocable | true |
| arguments | <target harness/model> [goal, next action, session notes, token budget] |
| allowed-tools | mcp__miller__workspace, mcp__miller__impact, mcp__miller__context, mcp__miller__search, mcp__miller__inspect, mcp__miller__trace, Bash |
Create a local markdown handoff packet from current workspace facts, Miller context, impact analysis, and explicit session notes. This is a skill workflow, not a Miller MCP tool or CLI command.
.miller/handoffs/; write both a timestamped packet and .miller/handoffs/latest.md..miller/handoffs/ packets.workspace(operation="status", format="json")
workspace(operation="health")
If health reports stale, missing, or corrupt sidecars, run workspace(operation="refresh") before collecting packet evidence. From JSON status, record index.built_revision and index.latest_revision as index_built_revision and index_latest_revision; do not invent a generic revision field.
git rev-parse --show-toplevel
git branch --show-current
git rev-parse --short HEAD
git status --short
git diff --stat
git diff --name-only
impact(git=true)
context(query="<goal, changed area, or next action>", token_budget=<budget>)
If the worktree is clean, write no local diff in the Impact section and use the goal/session notes to drive context(...).
.miller/handoffs/.Filename shape:
.miller/handoffs/YYYY-MM-DDTHH-MM-SSZ-<source>-to-<target>-<branch>-<short-head>.md
.miller/handoffs/latest.md
Use UTC time. Sanitize harness and branch names for filenames.
---
packet_format: miller-handoff-v1
workspace_root: /absolute/path
workspace_id: <miller workspace id or display id>
created_at_utc: 2026-06-28T00:00:00Z
source_harness: <source harness/model>
target_harness: <target harness/model>
branch: <branch>
head: <short head>
dirty_state: dirty|clean
index_built_revision: <workspace status index.built_revision>
index_latest_revision: <workspace status index.latest_revision>
---
## Resume Prompt
<Prompt the receiving agent can start with.>
## Current State
<Workspace status, branch, HEAD, dirty files, and concise state summary.>
## Changed Files
### git status --short
```text
<exact git status --short output, or "clean">
<exact git diff --name-only output, or "none">
<exact git diff --stat output, or "none">
<Miller impact output for the working-tree diff, or explicit "no local diff".>
<Agent-authored notes: what was tried, what failed, decisions made, constraints, and current intent. Do not include secrets.>
<Files, plans, tests, commands, or Miller calls worth opening first.>
## Final Check
Before reporting success:
```bash
test -s .miller/handoffs/latest.md
git check-ignore -q .miller
Report the timestamped packet path, whether the packet is safe for the target harness to read, and the next action. Do not paste the full packet unless the user asks.