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. ## Tracker Publish to the project's issue tracker when this session can reach one: an issue-tracker MCP server or a tracker CLI the host has connected (`gh issue` for GitHub Issues counts). Take the identifiers it needs (assignee, team or project, and the label that marks a spec) from the project map in `AGENTS.md`, or ask the user once; never guess or hardcode them. No tracker reachable: write the spec to `docs/plans/<feature-slug>/spec.md` instead, creating the directory if needed. `docs/plans/` is working state, not documentation: the first time you create it in a project, ask whether it should be committed or added to `.gitignore`. ## 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 (the project map in `AGENTS.md` says where both live). 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