Skills

6 skills for the whole workflow.

Skills are step-by-step workflows the agent follows. They’re written in neutral wording, so they read correctly in any tool, and go into the shared .agents/skills/ folder or the tool’s own folder where it needs one.

§01 · Day to day

Which one to use, when.

In tools without slash commands, say “use the feature skill” instead.

Situation	Do this
A new feature or a multi-file change	`/feature <description>`
A small, contained fix	`/quick-fix <description>`
Before saying it’s done	`/verify-change`
Ready to commit	`/ship`
The agent made a mistake you corrected	`/learn <lesson>`
New project or unfamiliar code	The agent uses `project-conventions` by itself

§02 · The skills

What each one does.

`feature`

The full pipeline: explore → align → design → build test-first → verify → simplify → review.

What it does: A slash command that walks the agent through the whole lifecycle for a feature. It explores the code, interviews you, designs a blueprint, waits for your approval, builds with TDD, then runs the verifier, code-simplifier and the reviewers before reporting.
When it’s used: For any new feature or multi-file change.
Example: /feature add CSV export to the reports page
Preset: Recommended and Everything
Also installs: Engineering rules, project-conventions skill, code-explorer agent, code-architect agent, verifier agent, code-simplifier agent, test-analyzer agent, silent-failure-hunter agent, security-reviewer agent
Needs: Matt Pocock's skills plugin (grilling, tdd, code-review, …). Without it, /feature falls back to the rules file.

`quick-fix`

Small, contained fixes with a quick verify loop.

What it does: A skill for clear, small changes: it sizes the change first, reproduces a bug with a failing test, makes the smallest correct fix, and verifies. If the change grows past about 6 files or 2 modules, it stops and switches to /feature.
When it’s used: For bug fixes and small changes where the solution is obvious.
Example: /quick-fix the date picker shows yesterday in UTC+ timezones
Preset: Recommended and Everything
Also installs: Engineering rules, /verify-change

`verify-change`

Prove a change works, fixing and retrying until it passes.

What it does: Runs the verifier subagent. If something fails because of the current change, the agent fixes the root cause and verifies again, up to 3 attempts, and never weakens tests to get a pass.
When it’s used: Before saying anything is done, or whenever you want proof.
Example: /verify-change
Preset: Recommended and Everything
Also installs: verifier agent
Needs: Optional: Matt Pocock's diagnosing-bugs skill for hard failures.

`ship`

Focused commits and a pull request description.

What it does: Checks that verification and review have passed, groups the changes into focused commits with clear messages, and writes a PR description. It only pushes or opens a PR if you ask it to.
When it’s used: When you're ready to commit.
Example: /ship pr
Preset: Recommended and Everything
Also installs: /verify-change, test-analyzer agent, silent-failure-hunter agent, security-reviewer agent
Needs: Optional: Matt Pocock's code-review skill for the review gate.

`learn`

Turn a correction into a permanent project rule.

What it does: When you correct the agent, /learn writes the lesson as one specific rule and proposes where it goes in CLAUDE.md. It applies the rule only after you approve.
When it’s used: Right after the agent makes a mistake you don't want repeated.
Example: /learn always use the apiClient wrapper, never fetch directly
Preset: Recommended and Everything

`project-conventions`

Detects your stack, real commands and conventions before writing code.

What it does: A read-only skill that looks at your manifests, scripts, CI and a few existing files to learn how your project is built and written, so new code matches it.
When it’s used: The agent uses it automatically in new projects or unfamiliar areas. /feature runs it first.
Example: Use the project-conventions skill and fill in the project section of CLAUDE.md.
Preset: Recommended and Everything
Also installs: Engineering rules

§03 · With Matt Pocock’s skills

Built on them, not a copy of them.

When Matt Pocock’s skills are installed, feature uses them for aligning (grilling), shared domain language, TDD, debugging and code review. When one isn’t, it does that step as the rulebook’s §2 describes, and says once which skill is missing. The installer doesn’t install them; its last screen gives you the command to paste.