This skill takes the current conversation context and codebase understanding and produces a specification. Do NOT interview the user; just synthesize what you already know.

The issue tracker and triage role vocabulary should have been provided to you. If not, ask the user whether to run /setup-ai-workspace now; if they decline, stop and tell them this skill needs it before continuing.

Process

Resolve the destination from documentation/agents/issue-tracker.md:
- Draft to .refinement/<issue-key>/specification.md, or .refinement/<feature-slug>/specification.md when no source issue exists. This is the default.
- Publish to the system-of-record tracker only on an explicit request such as "publish", "update Jira", or "create the issue".
When refining an existing issue, fetch its full body and comments through the configured access method before drafting. Put Source: <issue-key> (<url or repository-relative ticket path>) and Status: draft at the top of the draft. Publishing to a local markdown tracker writes the specification under backlog/ and links the draft to that authoritative record, exactly as publishing to a remote does.
Explore the repository to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the specification, 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.

to-specifications

Process