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 configured local equivalents of both labels:
- ready-for-agent: the canonical triage state; no additional triage is needed.
- spec: a provenance/category label identifying issues published by /to-spec, configured by /setup-nulfrog-skills and recorded under Category labels in the triage-label doc. It is not a triage state and must not replace ready-for-agent. If no such label is configured for this repo, apply ready-for-agent alone and say so; don't invent the label on the tracker.

to-spec

Process

Problem Statement