to-spec

name	to-spec
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.
disable-model-invocation	true

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.

Issue tracker conventions live in docs/agents/issue-tracker.md; the triage label vocabulary lives in docs/agents/triage-labels.md.

A spec is a review artifact — it is staged and reviewed as a PR before it publishes as an issue. See docs/agents/spec-review.md.

Process

1. Ensure a tracking issue exists. wayfinder and triage both arrive here with a tracker issue already (the map and its children; the incoming issue). Reaching to-spec directly from grill-with-docs — a well-understood single feature — does not, so mint one now (docs/agents/issue-tracker.md): a stub issue whose number names the spec-review branch {issue-number}-{slug} and anchors its PR. On merge (step 4), populate that same issue with the spec body and ready-for-agent rather than opening a new one. If a ticket already exists, use it and skip creation.

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

If a wayfinder map fed this spec, read the map's Decisions-so-far as the source and link the spec back to it. A large effort may be several specs — run this skill once per coherent feature.

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

4. Write the spec using the template below to docs/spec/<name>/spec.md, and open it as a PR for review (docs/agents/spec-review.md). Once the PR is approved and merged, publish the spec to the tracking issue from step 1 (creating one only if none exists yet) and apply the ready-for-agent triage label - no need for additional triage. to-tickets then breaks it into implementation tickets parented to this spec.

   The staged docs/spec/<name>/spec.md is temporary — it exists only for review. Once the spec issue exists, remove spec.md in a small follow-up PR against develop. (to-tickets creates its tickets directly on the tracker and no longer stages files, so it won't clean this up.)

Problem Statement

The problem that the user is facing, from the user's perspective.

Solution

The solution to the problem, from the user's perspective.

User Stories

A LONG, numbered list of user stories. Each user story should be in the format of:

1. As an , I want a , so that

1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending

This list of user stories should be extremely extensive and cover all aspects of the feature.

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

Testing 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)

Out of Scope

A description of the things that are out of scope for this spec.

Further Notes

Any further notes about the feature.