Matt Pocock Skills
A personal engineering skill library built around aligning with the agent before code is written: structured interview sessions, a shared project glossary and decision records, specs broken into issue-tracker tickets, test-first development, bug diagnosis, code review and module design, plus smaller utilities such as git safety guardrails. Aimed at software engineers working with a coding agent.
- Task planning
- Architecture
- Testing
- Debugging
Source: mattpocock/skills · pinned commit 3cca18b
View source on GitHubLuluSkill lists this project so you can find it. A listing is not a security review or an endorsement, and nothing on this page is installed or run for you.
EDITORIAL GUIDE
Choose the next engineering decision, not every workflow
The reviewed entry routes between problem discovery, design, planning and implementation. Treat the route as a decision aid rather than evidence that work has been done.
LuluSkill’s own reading of this project, not a summary of its README. About 3 minutes to read
This guide is LuluSkill’s own judgement about when this project fits, written from the pinned version named above. It is not the author’s documentation, not a security review and not a recommendation. LuluSkill did not install, run or test the project to write it, and the guide is shown only while this listing still points at the commit it was written against.
When this project fits
Use the reviewed router when an idea has unclear requirements or a substantial change needs staged decisions. Its opening flow directs an interview toward a specification and tickets, with a prototype detour when uncertainty cannot be resolved by discussion alone.
When to choose something else
A trivial typo fix does not need an entire planning process. Conversely, do not jump from a vague idea straight to implementation because the router mentions a later coding phase. A handoff request is not proof that another worker completed or checked anything.
What to provide and what to expect
Provide the current problem, unresolved decisions, repository context and desired next artifact. Expect the appropriate interview, prototype question, specification or task breakdown. Keep decisions and dependencies explicit so implementation starts from an agreed scope rather than accumulated conversation assumptions.
Tools, permissions and boundaries
Some routes rely on persistent context documents or a work tracker. Those need authorized storage and a clear owner. Source reads, prototypes and implementation have different permission needs; selecting a route should not implicitly grant all of them.
The tradeoff and an alternative
A single prompt with a concrete defect and expected behavior may be faster for a bounded change. The router is more valuable when the costly mistake would be implementing the wrong requirement. Its tradeoff is extra artifacts that must stay consistent as decisions change.
A small acceptance exercise
Proposed exercise: plan a small form change with one unresolved validation rule. Check that the uncertainty becomes an explicit decision, dependent tasks cannot start too early, and each task has observable acceptance criteria. Keep one writer per shared file during any parallel handoff.
Source, version and what was actually read
The opening router, interview stages, prototype decision and specification-to-task handoff guidance were read. Other skills in the collection and their implementation behavior were not evaluated. LuluSkill did not install or run this project; the exercise above is a proposed reader check, not a reported result.
How to use this listing
LuluSkill publishes the description and the source link only. The skill itself stays in its author’s repository, and nothing here is installed, copied or run for you.
- Read what the skill helps with The summary above says which job the project is for. If that is not the job you have, this is probably not the listing you want.
- Open the original source and follow the author’s own instructions The link to the original project opens its author’s page. That page, not this one, is where the setup steps and any copying instructions live.
- Use it in a compatible AI assistant Skills of this kind are normally used inside an AI assistant that can read a folder of files on your computer. Which assistants support them is the author’s decision, so check their page before you start.
Who it is for
Somebody who already wants this one job done and is willing to follow the author’s setup steps. No programming knowledge is assumed, and this listing cannot tell you whether the project suits you.
Before you start
You need an AI assistant that supports skills, and you will be following somebody else’s instructions on your own computer. Read them before you run anything.
What you end up with
Whatever the author’s project produces. LuluSkill never runs it, so this page cannot promise a result, a file, or a level of quality.
Where it is normally used
Projects like this are usually used in an AI assistant that supports skills, such as an AI coding assistant. The author’s repository says which assistants it is written for; LuluSkill has not tested it with any of them.
Version checked
The source was checked at this commit: 3cca18b
Changes made to the repository after this commit have not been checked.
License
MIT, from the licence file in the source repository at the listed commit. Check the repository’s licence before you use or copy the project.
Listing only
LuluSkill lists this project only. It does not host, download or run its code.
What this page does not include
The project’s files and setup steps stay in its own repository. LuluSkill has not security-tested the project or confirmed which AI assistants it works with.
Report a problem or request removal
Rights holders and users can report licence, attribution, security or accuracy problems with this page. We respond within 48 hours and record every request in our review log.
Opens your email app. You can also write to contact@luluskill.com and include this page’s address.