to-spec takes what you and the agent have already discussed, plus its understanding of the codebase, and writes a spec from a fixed template. It does not interview you. It sketches the test seams for the feature, checks them with you, publishes the spec to the project issue tracker and applies the ready-for-agent label.
It expects the tracker setup from setup-matt-pocock-skills.
What You Get
- A spec issue on your tracker with seven fixed sections
- A long list of user stories in the as-an-actor format
- Implementation decisions written without file paths or code snippets that go stale
- A proposed set of test seams, ideally one
Common Use Cases
- Capture the result of a long design chat as a ticket an agent can pick up
- Record the modules and interfaces a feature will touch before work starts
- Hand a feature to a background agent with testing decisions attached
What Makes It Unique
It synthesizes and never interviews, which makes it a fast closing step after a grilling session. It prefers the highest existing test seam and aims for as few seams as possible, and it applies the ready-for-agent label on publish so no further triage is needed.
Under The Hood
A single SKILL.md with an embedded spec template and no scripts. It explores the repo, uses the domain glossary vocabulary, respects ADRs, then publishes to whichever tracker setup-matt-pocock-skills configured, which can mean running gh or writing local markdown files.