ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Compact the current conversation into a handoff document for another agent to pick up.
Claude Code
$ npx -y skills add mattpocock/skills --skill handoff --agent claude-code
Codex
$ npx skills add mattpocock/skills --skill handoff -a codex -y
Cursor
$ npx skills add mattpocock/skills --skill handoff -a cursor -y
Gemini CLI
$ npx skills add mattpocock/skills --skill handoff -a gemini-cli -y
GitHub Copilot
$ npx skills add mattpocock/skills --skill handoff -a github-copilot -y
OpenCode
$ npx skills add mattpocock/skills --skill handoff -a opencode -y
Windsurf
$ npx skills add mattpocock/skills --skill handoff -a windsurf -y
name: handoff description: Compact the current conversation into a handoff document for another agent to pick up. 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 to the temporary directory of the user's OS (`$TMPDIR`, else `/tmp`; `%TEMP%` on Windows) - not the current workspace.
Include a "suggested skills" section in the document, naming which skills the next agent should call the Skill tool for.
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.
My agent skills that I use every day to do real engineering - not vibe coding. Developing real applications is hard. Approaches like GSD, BMAD, and Spec-Kit try to help by owning the process.
Ask which skill or flow fits your situation. A router over the skills in this repo.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this…
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening…
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something…
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or…
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Act on user feedback attached to the current session. Use when the user submits feedback on the session's changes via the Submit…