// Create a handoff document for the current conversation, ready for another agent to pick up.
Review recent changes since a fixed point (commit, branch, tag, or merge-base) along three independent axes - Standards, Spec, and Maintainability - run as parallel sub-agents that read beyond the diff, then aggregated into severity-ordered findings with an explicit verdict. Use when the user wants to review a branch, a PR, or recent committed changes.
Extract wisdom, insights, and actionable takeaways from YouTube videos, blog posts, articles, or text files. Use when asked to analyse, summarise, or extract key insights from a given content source. Downloads YouTube transcripts, fetches web articles, reads local files, performs analysis, and saves structured markdown.
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise.
Provides guidance and tools for hardware design. Activate when using KiCAD, looking up electronic parts or designing PCBs.
Find deepening opportunities in a codebase, informed by whatever domain language and architectural decisions are already documented in the repo. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
Guidance for editing Ghostty terminal configuration files. You must use this skill when creating or modifying Ghostty config files.
| name | handoff |
| description | Create a handoff document for the current conversation, ready for another agent to pick up. |
| argument-hint | What will the next session be used for? |
| disable-model-invocation | true |
| metadata | {"source":"Inspired by https://github.com/mattpocock/skills"} |
Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the temporary directory of the user's OS - not the current workspace.
Include a "suggested skills" section in the document, which suggests skills that the agent should invoke.
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.