Menu
Compact the current conversation into a handoff document so a fresh agent can continue the work.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
A relentless interview to sharpen a plan or design, which also creates docs (ADRs and glossary) as we go.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating spec/PRD asked for?). Use when the user wants to review a branch, work-in-progress changes, or asks to "review since X".
Turn the current conversation into a spec, saved to `.plan/` — no interview, just synthesis of what you've already discussed.
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, saved to `.plan/`.
| name | handoff |
| description | Compact the current conversation into a handoff document so a fresh agent can continue the work. |
| argument-hint | What will the next session be used for? |
| disable-model-invocation | true |
Write a handoff document summarising the current conversation so a fresh agent can continue the work.
Save it to .plan/handoffs/<YYYY-MM-DD>-<slug>.md at the repository root, creating the directory if needed (.plan/ is committed to version control — it is the project's shared planning memory). If not working inside a repository, save to the OS temporary directory instead and tell the user the absolute path.
Include a "suggested skills" section, listing skills the next agent should invoke — by name, with a one-line reason each — noting they apply only if available in that agent's environment.
Do not duplicate content already captured in other artifacts (specs, 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.
