Menu
Close out a work session: write a short HANDOFF.md snapshot so the next session picks up where this one left off. Run at the end of any substantive session.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Send a task or question to Claude Code and/or Gemini as external subagents and report back what they said. Use when the user asks to ask Claude, ask Gemini, ask both, get a second opinion, split reviewer roles, or compare external agents.
Smoke-test skill for the starter kit. Confirms the plugin installed and skills load. Use when the user runs /kit-hello or asks to verify the starter kit installation.
Wrap up the current session by writing a short HANDOFF.md in the project folder, so the next session can resume quickly. Use when the user says done, wrap up, close this out, or capture the session.
Turn a rough, dictated, or ambiguous request into a clear, structured task, then carry it out. Use when a request is conversational, messy, underspecified, or high-stakes enough to deserve careful framing before work begins.
Review a proposed plan with a single-pass structured critique and a clear verdict. Use when the user asks to review a plan, stress-test a plan, critique a workflow, identify risks, or improve an execution sequence.
Dispatch a small panel of critic agents in parallel on a plan, draft, or decision, then synthesize their raw critiques in a separate fresh-context pass. Use when the user asks for a council, a panel of critics, or a multi-angle review.
| name | done |
| description | Close out a work session: write a short HANDOFF.md snapshot so the next session picks up where this one left off. Run at the end of any substantive session. |
Close out this session. Plain Write tool only — no scripts, no state files, no routing logic. Everything stays in the current folder.
Summarize the session from the conversation: what we worked on, where it stands, what was decided, and the next concrete steps.
Overwrite ./HANDOFF.md — it's a snapshot, not a log, so replace the whole file. 30 lines maximum, exactly these sections:
# Handoff — <project>
## Status
## Next steps
- [ ] <one concrete step a fresh session could start on without asking questions>
## Key files
## Decisions
A few short lines per section. Next steps are checkboxes, most important first; leave finished items out. Key files = the handful of files the next session should open first.
If ./SESSION_LOG.md exists, also append a dated entry of 3–6 bullets — what happened this session. Append at the end; never edit earlier entries. (If the file doesn't exist, skip this — don't create it.)
End by telling the user: "Next session, open this folder and I'll read HANDOFF.md to pick up where we left off."