菜单
Resume work from a handoff document with context analysis and validation. Use when the user requests to resume from a handoff, continue previous work, or references a handoff path or ticket number (ENG-XXXX). Supports quick mode (default) and full mode (--full flag).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | resume-handoff |
| description | Resume work from a handoff document with context analysis and validation. Use when the user requests to resume from a handoff, continue previous work, or references a handoff path or ticket number (ENG-XXXX). Supports quick mode (default) and full mode (--full flag). |
| allowed-tools | Read, Write, Bash, Agent, mcp__plugin_claude-mem_mcp-search__smart_search, mcp__plugin_claude-mem_mcp-search__smart_outline, mcp__plugin_claude-mem_mcp-search__smart_unfold |
Resume work from a handoff document through interactive context analysis and validation.
Handoff path provided:
--full): Spawn sub-agents to read all referenced documentsTicket number provided (ENG-XXXX):
humanlayer thoughts sync to update thoughts/No parameters:
Which handoff would you like to resume from?
Tip: /resume_handoff thoughts/shared/handoffs/ENG-XXXX/file.md [--full]
/resume_handoff ENG-XXXX [--full]
smart_outline + smart_unfold over ReadCover: original tasks vs current verification, key learnings, recent changes, recommended next actions.
Get confirmation before proceeding.
| State | Approach |
|---|---|
| Clean Continuation | All changes present → proceed as planned |
| Diverged Codebase | Changes missing → reconcile and adapt |
| Incomplete Work | In-progress tasks → complete unfinished first |
| Stale Handoff | Significant time elapsed → re-evaluate strategy |
Document codebase as-is via parallel sub-agents. Use when researching how code works, mapping architecture, or answering questions about existing systems. Auto-detects thoughts/ directory — if present, integrates historical context and syncs; if absent, skips those steps.
Create the Questions artifact before codebase research, design, planning, or implementation. Use for feature tickets, architecture changes, unclear code work, CRISPY/QRSPI Questions phase, or when the agent needs to define code-answerable unknowns and human questions before researching or planning.
Create a concise Design Concept artifact after questions and codebase research are available. Use for CRISPY/QRSPI Design phase, architecture alignment, feature design discussion, or turning current-state research into a small human-reviewable proposed shape before detailed planning.
Create an interface-first Structure Outline before detailed planning or implementation. Use for CRISPY/QRSPI Structure Outline phase, vertical planning, method signatures, type contracts, API/component boundaries, or converting an accepted design concept into end-to-end slices with verification checkpoints.
Create comprehensive handoff documents for transferring work to another agent session. Use when the user requests to create a handoff, end a session, or document work-in-progress for future continuation.
Create detailed implementation plans through interactive research and iteration. Use when starting a new feature or ticket that needs a comprehensive technical plan. Saves plans to the repo-appropriate plans location and emits Personal Knowledge events when applicable.