What do you want to do?
5 use cases
-
Align an agent on a change before any code is written
Run a grilling session so the agent asks detailed questions before it edits your repo.
- Skills
- Claude Code
- Codex
- Software and DevOps
- Intermediate
View prompt
In the mattpocock/skills repo's grill-with-docs workflow, interview me about the change described here: <feature description>. Expected output: a short list of resolved decisions and updated GLOSSARY.md entries or ADRs. Verify that every new term in the output appears in the glossary file.
-
Split a plan into tracer-bullet tickets with blockers
Turn a conversation into a spec, then into ordered tickets that declare what blocks what.
- Skills
- Codex
- Claude Code
- Software and DevOps
- Intermediate
View prompt
In the mattpocock/skills repo, use to-spec on our current discussion about <feature>, then use to-tickets to split the spec into tracer-bullet tickets. Expected output: a published spec and a ticket list where each ticket names its blocking tickets. Verify that no ticket is blocked by a ticket that depends on it.
-
Fix a bug with a failing test before the fix
Diagnose a bug in phases, then drive a red-green-refactor loop to fix it.
- Skills
- Claude Code
- Codex
- Software and DevOps
- Intermediate
View prompt
In the mattpocock/skills repo, use diagnosing-bugs on this failure: <bug description>, then use tdd to write a failing test before any fix. Expected output: a root-cause note and a red test that turns green after the fix. Verify that the test fails on the unfixed code before you accept the change.
-
Find deepening opportunities in an aging codebase
Scan a repo for modules to deepen, review an HTML report, then grill through one pick.
- Skills
- Claude Code
- Software and DevOps
- Intermediate
View prompt
In the mattpocock/skills repo, run improve-codebase-architecture on <repo path>. Expected output: an HTML report of deepening candidates, then a grilling session on the one I pick. Verify that the report lists concrete modules rather than general advice.
-
Plan a huge project as a map of decision tickets
Use wayfinder to resolve decisions one at a time across several agent sessions.
- Skills
- Codex
- Software and DevOps
- Advanced
View prompt
In the mattpocock/skills repo, use wayfinder to map the work needed to reach <destination>. Expected output: a set of decision tickets on the issue tracker and the first one to resolve. Verify that each decision ticket is stored in the tracker and not only in the chat.
How to use Skills
- Check you have what it needs: A coding agent that supports the plugin or skills install route, such as Claude Code or Codex; A project repository the agent can read and edit; Optional: an issue tracker such as GitHub or GitLab, or a local folder for tickets.
- Open mattpocock/skills on GitHub and read the README and license.
- Install the plugin in Claude Code with
claude plugin install mattpocock-skills@claude-plugins-official. - In your repo, run
/setup-matt-pocock-skillsonce and answer the questions about issue tracker, triage labels, and where docs go. - Run
/grill-with-docsand describe the change you want. - Answer the agent's questions until the plan is clear, and let it update the glossary and ADRs as you go.
These steps come from our top use case, Align an agent on a change before any code is written, which also has a copy-paste agent prompt.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeAbout this repo
- Who it is forWorking software engineers who use Claude Code, Codex, or other coding agents and want more control over planning, testing, and design than full process frameworks give.
- Why it is hot
- LanguageShell
- Sourcegithub.com/mattpocock/skills · Back to Hot repos
Requirements
- A coding agent that supports the plugin or skills install route, such as Claude Code or Codex
- A project repository the agent can read and edit
- Optional: an issue tracker such as GitHub or GitLab, or a local folder for tickets
Maintain Skills? Add the Featured on Deduped badge
Paste this into your README:
[](https://dedupedai.com/use-cases/mattpocock-skills/?ref=badge)
Questions about Skills
What is Skills?
A set of editable agent skills for planning, aligning, building, and debugging software with coding agents, taken from the author's .agents directory. It is an open-source project on GitHub: https://github.com/mattpocock/skills.
Who is Skills for?
Working software engineers who use Claude Code, Codex, or other coding agents and want more control over planning, testing, and design than full process frameworks give.
What can I do with Skills?
5 use cases so far, for example: Align an agent on a change before any code is written; Split a plan into tracer-bullet tickets with blockers; Fix a bug with a failing test before the fix. Each has steps and a copy-paste agent prompt.
What do I need to run Skills?
A coding agent that supports the plugin or skills install route, such as Claude Code or Codex; A project repository the agent can read and edit; Optional: an issue tracker such as GitHub or GitLab, or a local folder for tickets.
What are alternatives to Skills?
Other hot AI repos in Software and DevOps: Harness2, iFixAi, Orca, Diagram Design, AI Memory.
Is Skills safe to run?
Deduped does not own, audit or vouch for it. Read the README and license, run it on your own systems first and review every command before you run it.