Conversation to Spec
By Kai · Published · Updated
Turns a discussion into a spec with goals, non-goals, decisions, open questions and acceptance criteria that can be tested.
Prompt template
## Conversation to Spec Turn this discussion into a spec. - Discussion notes: [textarea: Paste the conversation or notes] - Feature name: [text: Short working name] - Audience for the spec: [dropdown: Engineers, Product and design, Mixed team] - Known constraints: [textarea: Deadlines or tech limits or policy] - Detail level: [dropdown: One page, Standard, Detailed] Read the whole discussion and separate what was decided from what was merely suggested. Write the spec in this order: problem and goal in plain words; non-goals, which prevent scope creep; decisions made, each with its reason; the behavior in concrete terms, with examples of inputs and outputs; constraints; open questions with a proposed owner; and acceptance criteria written as checks anyone can run, one observable result each. Mark anything that was only implied as an assumption instead of stating it as fact. Do not add features nobody mentioned. Keep terms consistent and define any term used in a special sense. End with a list of the sentences you are least sure were agreed.