Skill Overview

Skills package repeatable work. Claude Code uses /<name>; Codex uses $od-<name> where available. The links below give triggers, arguments and examples.

New to specs and todos? Read Specs and Todos first; Workflows shows how they chain.

Quick pick

I want to…	Skill
remember something small for later	/todo <text>
plan bigger work before building	/spec, then /spec-work
fix a bug properly	/debug
check my change	/test, then /review --quick
commit or publish	/commit, /release
think an idea through	/brainstorm, /challenge, /vision
hand work to another model	/delegate

Plan, build and verify

Skill	Use it for → what you get
/spec	Plan work above the size threshold (>5 steps or >6 files over 2+ subsystems), a larger handoff, or an open decision. A small immediate task is a bounded brief; deferred work → /todo. Starting /spec-work is the approval.
/spec-work	Build one approved spec, checks and all. Rerun it to resume at the first open step. It never commits — /commit is yours. Several independent specs → /wave.
/spec-update	The contract itself is wrong — a missing requirement, criterion or file. Rewrites it and reopens the affected steps; wrong code is fixed in /spec-work.
/debug	A reported bug with a clear expected value: reproduce as a failing test, then fix the cause. A typo needs no test.
/test	Targeted tests after a coherent change, before calling it done. The full suite only on request or for risky shared code.
/review	A read-only second look with a verdict: PASS, PASS_WITH_FOLLOWUPS, BLOCK or NOT REVIEWED, and findings with file:line. --quick for a risky diff, --audit for the repo.
/commit	Only you start it: one commit of this session's files. It never pushes.
/release	Only you start it: on a clean default branch, bump the version, tag, push and publish the GitHub release.
/agent-browser	A real browser pass after Vue, React, Liquid, Twig, Blade or CSS changes, or to check a live URL.
/checkin	You lost track or assumptions are unconfirmed: a status card and one question, applied at once. Not a /review replacement.

Ideas, bigger initiatives and delegation

Skill	Use it for → what you get
/vision	Set the north star for a project or idea; --calibrate when work outgrew it. Other skills check against it.
/brainstorm	Shape a vague idea into problem, options, risks and the next small slice. Resumable by number.
/challenge	Argue against a concrete idea before spending a spec: GO, SIMPLIFY or REJECT, plus traps.
/wave	Several approved specs in parallel worktrees, merged behind the gate. Needs Orca.
/workspace	One requirement across sibling repositories: one spec each and the order to run them.
/delegate	Hand a bounded review, research or implementation to another model.

Knowledge and tasks

Skill	Use it for → what you get
/index	Bring a project to the current devkit: stack, code graph and .agents/context/; commit the result for the team.
/capture	Store one lasting fact — gotcha, convention, decision, term — in .agents/context/.
/todo	Park small work for later or work exactly one from claim to commit. Detail: Specs and Todos.
/research	Judge whether an external repo, tool or article is useful; ranked candidates, then /spec.
/fetch-task	Pull one CrewBuddy ticket or all open ones into local digest files, then route it: direct or spec.
/token-check	Rank the biggest token sinks and apply only the savings you pick.

Feedback, design and setup

Skill	Use it for → what you get
/friction-feedback	Turn a blocked gate or a devkit gap you worked around into a GitHub issue.
/boilerplate-feedback	Send a reusable client-project change to that stack's boilerplate.
/pen-design	Design on a .pen canvas and build it with project tokens; naming frame numbers releases the code.
/skill-create	Write a project-local skill for a procedure that repeats; /reload-skills after.
/improve-codebase-architecture	Find deeper structural candidates; proposes only, then steps for /spec.
/share	Publish a Markdown or HTML file as a public link (30 days) — one approval question first.