菜单
Compact the current conversation into a handoff document for another agent to pick up.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | handoff |
| description | Compact the current conversation into a handoff document for another agent to pick up. |
| argument-hint | What will the next session be used for? |
Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save it in the workspace tmp/ directory.
Name the file xxx-handoff-slug.md, where xxx is a zero-padded three-digit index and slug is a short kebab-case summary of the handoff focus. Choose the index by scanning existing handoff files in tmp/ and using the smallest available positive integer, reusing gaps. For example, if 001-handoff-*.md is missing and 002-handoff-*.md exists, the next handoff file must use 001.
Include a "suggested skills" section in the document, which suggests skills that the agent should invoke.
Do not duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.
Redact any sensitive information, such as API keys, passwords, or personally identifiable information.
If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.
scripts/delete-handoff.ts — Delete a single handoff by index, slug, filename, or path. Supports --dry-run, --json, --list.scripts/delete-all-handoffs.ts — Delete all handoff files. Supports --dry-run, --json.Delete a single handoff:
npx tsx scripts/delete-handoff.ts <identifier>
npx tsx scripts/delete-handoff.ts --dry-run 001
npx tsx scripts/delete-handoff.ts --list
Delete all handoff files:
npx tsx scripts/delete-all-handoffs.ts
npx tsx scripts/delete-all-handoffs.ts --dry-run --json
Wrap up a work session by validating the repo, grouping the diff into logical change sets, stashing each group, then fanning out parallel subagents that create branches, commits, PRs, and monitor CI — following the repo's GitHub Flow strategy. Use when the user wants to close shop, end a shift, wrap up today's work, or batch a day's coding into PRs.
Assign Complexity ratings (1-5) to issues in a directory and recommend decomposition for Complexity 5 issues. Use when user wants to rate issue complexity, assess backlog difficulty, prioritize issues by effort, or decompose complex issues into smaller slices.
Discover and implement 1-3 ready-for-agent issues using the Features CLI. Use when user says "do an issue", "pick up next issue", "implement issues", "what's next", "work on backlog", "execute issues", or asks to implement ready-for-agent issues from .scratch/.
Add or tighten GitHub Flow restrictions for a GitHub repository using gh CLI in a solo developer setup. Use when asked to enforce pull-request-only main branch protection, required status checks, force-push blocking, or other branch safety rules without requiring a second reviewer.
Verify whether a GitHub repository is correctly configured for GitHub Flow, especially for a solo developer setup. Use when asked to audit branch protection, required checks, pull request rules, rulesets, or whether main is safely protected without blocking a single maintainer workflow.
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.