菜单
Write a structured session handoff file for clean context transfer. Use when ending a session, before /clear, when context is heavy, when handing off work to another pane, or when asked to "handoff", "checkpoint", "session-transfer", "save state", "prepare for clear".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Walk the B1-B15 AI-to-AI blind-spot catalog systematically. Use during the audit pipeline AFTER hard-stops and Tambon hunt and BEFORE the 13 domain audits. Output: PRESENT / NOT PRESENT for each B-class with evidence. Findings flow into the appropriate domains.
Standardize remediation decisions, baseline-policy entries, and legal-review banners for accepted, deferred, or policy-blocked audit findings.
Audit the security domain - auth, authz, secrets, transport, sensitive data exposure, dependency CVEs. Run as part of /audit Phase E.
Audit the architecture and code quality domain - module boundaries, abstraction layers, code organization, naming, documentation. Run as part of /audit Phase E.
Audit the database and data layer - schema design, query patterns, migrations, indexing, RLS, soft-delete, transactions. Run as part of /audit Phase E.
Audit the infra and DevOps domain - CI/CD, deployment, IaC, secrets management, environments, logging, observability. Run as part of /audit Phase E.
| name | handoff |
| description | Write a structured session handoff file for clean context transfer. Use when ending a session, before /clear, when context is heavy, when handing off work to another pane, or when asked to "handoff", "checkpoint", "session-transfer", "save state", "prepare for clear". |
| metadata | {"argument-hint":"[focus-instruction]","disable-model-invocation":false} |
Write a comprehensive, structured handoff document so the NEXT session (or a clean restart of THIS session after /clear) can pick up with ZERO context loss on what matters.
Output file: handoffs/handoff-<ISO-timestamp>-<short-id>.md relative to your current working directory. Create the handoffs/ directory if it doesn't exist. NEVER overwrite an existing handoff file - always generate a unique filename.
If $ARGUMENTS is provided, treat it as a focus instruction (e.g., "focus on the auth refactor, skip the test debugging"). Prioritize that area in your handoff.
Fill ALL of these. If a section is genuinely empty, write "None" - do NOT skip the heading.
## ContextWhat was this session about- One paragraph, high-level. Include:
## Current StateConcrete, verifiable state of the codebase RIGHT NOW:
git status --short if unsure)## Open ThreadsWork that is IN PROGRESS but NOT yet reflected in committed files:
This is the most critical section. The next session won't know about these unless you write them down. Be specific - "I was refactoring X" is useless; "I extracted function Y from file Z into module W, the import in Z is updated but 3 callers in A, B, C still reference the old location" is useful.
## Next StepsExactly what to do FIRST in the new session, ordered by priority:
## Constraints & GotchasAnything learned during this session that shouldn't be re-discovered:
## Relevant FilesAbsolute paths to the files the next session should read FIRST:
/full/path/to/critical-file-1.ts
/full/path/to/critical-file-2.cjs
Don't make the next session grep - give it the exact paths.
## Corr IDIf a correlation ID was provided (e.g., corr=handoff-abc123), include it here for tracking. If none was provided, generate one: handoff- + 6 random alphanumeric characters.
C:\Users\username\...) in the handoff file. Use relative paths or $HOME-based references.parseStatusBar() to src/status-parser.cjs, imported in pane-discovery.cjs:12, exposed ctx field in collectPanes() at dashboard-server.cjs:85" is USEFUL.git status, check the build, check if your dev server is alive. Don't guess - report facts.