메뉴
Compact the current conversation into a handoff document for another agent to pick up.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Create a file-based C# agent workflow using the Agent Workflow Framework. Use when asked to set up an agent workflow, Ralph-style (checklist) workflow, builder&evaluator loop, or other multi-agent orchestration workflows.
Drive a Roslyn compiler/IDE bug from a GitHub issue to an accepted fix using a repro-first, subagent-orchestrated pipeline (repro → baseline commit → root-cause → fix → evaluate → summary). Use when asked to fix a dotnet/roslyn issue, reproduce a Roslyn bug as a unit test, or run the bug-fix loop on an issue number.
Create a git worktree, using copy-on-write reflinks when the volume supports it. Use whenever adding a git worktree.
Create or refresh a private PR review walkthrough as a self-contained HTML file. Use when asked to write a reviewer brief, narrative PR walkthrough, grounded review notes, or a linear walkthrough of a PR. Triggers on: walkthrough this PR, write a PR walkthrough, reviewer brief, review narrative, linear walkthrough.
Teach the user a new skill or concept, within this workspace.
Add a Today I Learned entry to blog.monstuff.com/til. Use when asked to add, write, publish, draft, or create a TIL entry for blog.monstuff.com. Triggers on: add a TIL, write a TIL, new TIL, publish a TIL, create a TIL.
| 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 to a path produced by mktemp -t handoff-XXXXXX.md (read the file before you write to it).
Suggest the skills to be used, if any, by the next session.
Do not duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.
If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.
