issue-handoff
Issue Handoff
Turn agent findings into a self-contained handoff another agent can act on without prior thread context.
Core rule
Default output is one ready-to-send prompt block.
- Prefer prompt text, not files.
- Create files only if the user explicitly asks.
- Preserve evidence.
- Preserve uncertainty.
- Assume the receiving agent has not seen the current conversation.
Workflow
- Extract:
- problem
- current state
- affected scope
- evidence
- expected result
- requested next action
-
Ask for missing critical details only. If something is unknown, mark it
Unknowninstead of guessing. -
Return this exact shape:
You are taking over this task with no prior thread context.
Problem:
- ...
Why this was handed off:
- ...
Current state:
- ...
Affected scope:
- ...
Observed behavior:
- ...
Expected behavior:
- ...
Evidence:
- ...
- ...
Repro steps:
- 1) ...
- 2) ...
Unknowns:
- ...
Acceptance criteria:
- ...
Constraints:
- ...
Requested next action:
- ...
Success looks like:
- ...
Files:
- prompt-only handoff unless user provided files.
- Keep it operational.
- Do not add backstory.
- Do not write ticket prose.
- Do not assume shared memory between agents.
Optional file handoff (only if requested)
Create handoff-YYYY-MM-DD-issue.md with the same content as above.
More from mylesmcook/mcook-skills
adversarial-review
Use this skill when you need a serious code review, diff review, or implementation-plan review from independent reviewers. In Codex hosts, prefer a fresh Codex subagent for the Codex reviewer; otherwise use the Codex, Claude Code, and Gemini reviewer paths when available. Return a PASS, CONTESTED, or REJECT verdict.
13subagent-driven-development
Use after an implementation plan is approved to execute mostly independent tasks through fresh subagents with scoped context, harness-aware model routing, proportional review gates, and mandatory controller verification.
10brainerd
>
10simple-code
Reduce incidental complexity in code and design. Use when shaping APIs, module boundaries, refactors, tests, naming, and architecture tradeoffs with a bias toward concrete, local, reversible solutions.
7git-it-out
Use this skill when the user explicitly wants final end-of-session closeout and no more branch or PR limbo: proper verification, proper commits, main/mainline landing, push, repo-native merge/release/deploy/publish steps, tracker updates, Entire/checkpoint handling when configured, and a concise handoff. Reach for it on prompts like 'git it out', 'get it out', 'ship this', 'I'm done', 'I'm going to bed', 'take this off my plate', 'finish the session', or 'get this into production'. Do not use it for greenfield implementation, open-ended debugging, broad refactors, or inventing a release process from scratch.
7laws-of-taste
>-
6