Quickly navigate through the dashboard with your keyboard using the command menu.
Plain instructions, so it works in every AI that reads skills, even pasted into a ChatGPT project. Pick your AI below; we remember it on every skill.
Your AI reads this line to decide when the skill applies. You never have to call it by name.
“Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.”
3 files of instructions.
This skill takes the current conversation context and codebase understanding and produces a spec. Do NOT interview the user; just synthesize what you already know.
The issue tracker and triage label vocabulary should have been provided to you. If not, tell the user to run /setup-matt-pocock-skills.
Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the spec, and respect any ADRs in the area you're touching.
Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one.
Check with the user that these seams match their expectations.
ready-for-agent triage label - no need for additional triage.<spec-template>
The problem that the user is facing, from the user's perspective.
The solution to the problem, from the user's perspective.
A LONG, numbered list of user stories. Each user story should be in the format of:
<user-story-example>
This list of user stories should be extremely extensive and cover all aspects of the feature.
A list of implementation decisions that were made. This can include:
Do NOT include specific file paths or code snippets. They may end up being outdated very quickly.
Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it within the relevant decision and note briefly that it came from a prototype. Trim to the decision-rich parts, not a working demo, just the important bits.
A list of testing decisions that were made. Include:
A description of the things that are out of scope for this spec.
Any further notes about the feature.
</spec-template>
Turns a rough conversation into a clear, buildable spec.
Plain instructions: no scripts, nothing to install.
Builds evidence-based personas with jobs, pains and buying triggers.