to-spec
The facts
Its description
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.
The description the agent reads to decide when to use it.
When it starts
The agent never picks this skill from its description: model invocation is disabled, so the user starts it explicitly, normally by typing the /to-spec command, when they want the conversation so far synthesised into a spec and published to the project issue tracker rather than interviewed about.
Things a person might say (the model's guesses)
- “/to-spec”
- “turn this conversation into a spec and put it in the issue tracker”
- “write this up as a spec — don't interview me, just use what we've already discussed”
A model's summary of when it is used.
Who can start it
Only you
Only you can start it. The agent never picks it on its own.
Stops for a person
1 line stops to ask a person
Lines that stop and wait for a person before going on. Found by matching words, so treat them as pointers.
What it leads to
- requires setup-matt-pocock-skills only if the tracker and triage label vocabulary were not already provided line 9
Other skills this one hands off to, calls, requires or offers instead, as a model read them.
What leads to it
- ask-matt hands off to this for a multi-session build ask-matt, line 25
- chief-of-staff calls this for large chunks of work chief-of-staff, line 54
- implement-spec requires this implement-spec, line 3
Other skills that hand off to this one, call it, require it or offer it instead, as a model read them.
Licence
MIT, from LICENSE
The terms its author shares it under, which let it be shown here.
Other files in this skill (1) Close
The text
Most marks come from matching words in the file, so treat them as pointers.
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.
Process
- 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.
- Write the spec using the template below, then publish it to the project issue tracker. Apply the
ready-for-agenttriage label - no need for additional triage.
<spec-template>
Raw lines 11 to 22Problem Statement
The problem that the user is facing, from the user's perspective.
Raw lines 23 to 26User Stories
A LONG, numbered list of user stories. Each user story should be in the format of:
- As an <actor>, I want a <feature>, so that <benefit>
<user-story-example>
- As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending
</user-story-example>
This list of user stories should be extremely extensive and cover all aspects of the feature.
Raw lines 31 to 42Implementation Decisions
A list of implementation decisions that were made. This can include:
- The modules that will be built/modified
- The interfaces of those modules that will be modified
- Technical clarifications from the developer
- Architectural decisions
- Schema changes
- API contracts
- Specific interactions
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.
Raw lines 43 to 58Testing Decisions
A list of testing decisions that were made. Include:
- A description of what makes a good test (only test external behavior, not implementation details)
- Which modules will be tested
- Prior art for the tests (i.e. similar types of tests in the codebase)
From mattpocock/skills at 4ae2317, 2026-10-31. Skills read by DeepSeek V4.1 Flash on 2026-11-04. Summary and techniques by Claude Opus 5.5 on 2026-11-06.