Agent Skills

---

name: brainstorming

description: You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).

---

name: diagnosing-superpowers

description: Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.

---

name: dispatching-parallel-agents

description: Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

---

name: executing-plans

description: Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available

---

name: finishing-a-development-branch

description: Use when implementation is complete, all tests pass, and you need to decide how to integrate the work

---

name: receiving-code-review

description: Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

---

name: requesting-code-review

description: Use when completing tasks, implementing major features, or before merging to verify work meets requirements

---

name: subagent-driven-development

description: Use when executing implementation plans with independent tasks in the current session

---

name: systematic-debugging

description: Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

---

name: test-driven-development

description: Use when implementing any feature or bugfix, before writing implementation code

---

name: using-git-worktrees

description: Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

---

name: using-superpowers

description: Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

---

name: verification-before-completion

description: Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

---

name: writing-plans

description: Use when you have a spec or requirements for a multi-step task, before touching code

---

name: writing-skills

description: Use when creating new skills, editing existing skills, or verifying skills work before deployment

---

name: ask-matt

description: Ask which skill or flow fits your situation. A router over the skills in this repo.

---

name: chief-of-staff

description: Pursue a long-running goal in a single session by co-ordinating subagents.

---

name: claude-handoff

description: Hand the current conversation off to a fresh background agent that picks up the work immediately.

---

name: codebase-design

description: 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.

---

name: code-review

description: 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 issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".

---

name: diagnosing-bugs

description: Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

---

name: domain-modeling

description: Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

---

name: git-guardrails-claude-code

description: Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.

---

name: grill-with-docs

description: A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.