Feature spec

---name: feature-specdescription: "Turn a request, thread or idea into a one-to-two page feature spec: the problem, who it is for, scope, non-goals, acceptance checks and open questions."metadata:  title: "Feature spec"  category: writing  tags: [product, planning]--- ## When to use this Someone has asked for a feature, or a conversation has settled on building one,and it needs writing down before anyone plans or builds it. ## How 1. Find the problem behind the request. "Add a CSV export" often means "I need   these numbers in my spreadsheet every Monday". Ask when it is not clear who   hits the problem and how often.2. Write these sections:   - Problem: two or three sentences, with evidence -- a quote, a ticket, a     number.   - Who it is for, and what they do today instead.   - What it does, from the user's side, step by step.   - Non-goals: what it deliberately does not do. This is the section that     stops the scope growing.   - Acceptance checks: statements that are either true or false.   - Open questions, each with who can answer it.3. Leave out how to build it unless a constraint forces the choice.4. Mark anything you assumed rather than read "(assumed)".5. Two pages at most. Detail that changes no decision goes in a link.6. Post it as a document. Ask before copying it into Notion, Linear or any   other shared tool. If the problem will not fit in two sentences, say so: it is not ready for aspec yet.