to-spec

Topics in the source

• Process
• Problem Statement
• Solution
• User Stories
• Implementation Decisions
• Testing Decisions
• Out of Scope
• Further Notes

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 and triage label vocabulary should have been provided to you. If not, tell the user to run /setup-matt-pocock-skills. 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 to the project issue tracker. Apply the ready-for-agent triage label - no need for additional triage. The problem that the user is facing, from the user's perspective. The solution to the problem, from the user's perspective. A LONG, numbered list of user stories. Each user stor

This is an excerpt. Refer to the complete source and its current requirements.