Menu
Compact the current conversation into a handoff document for another agent to pick up.
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
Ultra-compressed communication mode. Cuts output tokens 65% (measured) by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes $caveman. Also auto-triggers when token efficiency is requested.
Review a branch, PR, commit range, or working-tree diff along two separate axes: Standards and Spec alignment. Use for review requests and as the quality gate after non-trivial implementation. Load security review only for security-sensitive changes.
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.
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
Implement requested code changes end to end from a prompt, spec, or ticket. Use for feature work, diagnosed bug fixes, refactors, and other tasks that require editing code and verifying the result.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
| name | handoff |
| description | Compact the current conversation into a handoff document for another agent to pick up. |
Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the /memory/handoff directory of the current workspace, if that folder is not there make sure to create it in /docs/handoff and delete it after the task is done.
Include a compact "Suggested skills" section containing only skills whose trigger conditions match the remaining work. Prefer the normal chain: diagnosing-bugs for unresolved bugs, implement for edits, code-review after non-trivial edits, and domain skills only when applicable.
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.
