write-speclisted

# Create a Feature Specification Produce a feature specification a development team can build from, using GitHub Spec Kit's structure and quality bar. The specification describes **what** users need and **why** it matters — never how to implement it. The person using this is a product manager, business owner, or domain expert — deep knowledge of the business, none of software construction assumed. Write the spec for business stakeholders and keep the conversation in plain language. Never ask them a question only an engineer could answer, and don't use a technical term without defining it in the same sentence. Don't narrate file paths or internal steps as you go — but do say where the spec ended up when you're finished, so they can find it. ## How to ask anything, anywhere in this skill This governs **every** question below, not just the clarifying questions in step 6: - **Always lead with a recommendation.** A neutral menu hands the decision back to someone who came here precisely because they don't know the options. Say what you'd do and why, in a sentence, and make agreeing cheap: "say yes and I'll take it." - **"You pick" / "I don't know" / "which is normal?" is an answer.** Take your recommendation and carry on — never stall waiting for a preference they don't have. Record the result under **Assumptions** as *your* guess, not as their decision. - **Never invent a specific number, threshold, name, or percentage they haven't given you or clearly implied.** Filling in s