메뉴
Compact the current conversation into a handoff document for another agent to pick up.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Drive and read Ionwake's `__ionwake*` window instrumentation hooks (`__ionwakeScene` on /play, `__ionwakeShipyard` on /shipyard, and the dev-only `__ionwake` debug flags) from outside the page via the Chrome DevTools MCP. Use to read live sim/scene/clock state, screenshot the running app, drive the shipyard, load ship models, inspect a ship schema, log the WebTransport wire, or keep a backgrounded tab stepping.
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo.
Interview the user relentlessly about a game design concept or design until reaching shared understanding, stress-testing the concept and resolving each branch of the decision tree.
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
| argument-hint | What will the next session be used for? |
| description | Compact the current conversation into a handoff document for another agent to pick up. |
| disable-model-invocation | true |
| metadata | {"github-path":"skills/productivity/handoff","github-ref":"refs/tags/v1.0.1","github-repo":"https://github.com/mattpocock/skills","github-tree-sha":"aa82ffd61d7a3bda110060b4e24ec782b983cb8d"} |
| name | handoff |
Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the .claude/handoffs folder in the project's workspace.
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.
