to-speclisted

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 is **local markdown**: work items live as files under `.scratch/` in the repo. If `docs/agents/issue-tracker.md` exists, read it first and follow it instead. There is no triage-label vocabulary here, so skip triage labels entirely. Do not tell the user to run `/setup-matt-pocock-skills`; it is not installed. ## 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 save it to `.scratch/<feature-slug>/spec.md` (or publish it to the tracker described in `docs/agents/issue-tracker.md`, if that file exists). Tell the user the path you wrote. <spec-template> ## 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, n