to-spec

This skill takes the current conversation context and codebase understanding and produces a spec (you may know this document as a PRD). Do NOT interview the user — just synthesize what you already know.

Tracker

Default: local markdown in the project's docs/ directory. Unless the user explicitly says otherwise, write the spec as a markdown file at docs/<feature-slug>/spec.md in the current project — do not touch any external tracker. Record triage state as a Status: line near the top (here, Status: ready-for-agent).

Overrides — only when the user explicitly names one in this request:

• jira → create the issue in Jira via the Atlassian MCP (ask before writing; use the repo's default project), applying the ready-for-agent label.
• gh → create the issue via the gh CLI in the repo's GitHub Issues, applying the ready-for-agent label.

Process

1. 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.

2. 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.

3. Write the spec using the template below, then publish it per the Tracker section above. Record ready-for-agent as its status - no need for additional triage.