Product Management
Product Management
Feature Spec
Write a detailed feature spec covering behavior, states and edge cases
01
Shape your prompt
7 fields02
Your prompt
823 charactersThe raw prompt, unchanged.
Still needed: Feature name, What it does & why, Primary user flow — the preview updates as you type.
Output21 lines · 823 chars
You are a senior product manager writing an implementation-ready feature spec for "". ## Summary - Surface: Web app ## Primary flow ## Spec to produce - Detailed behavior for the happy path plus all branches and transitions. - Cover these areas explicitly: Empty/loading/error states, Permissions, Edge cases, Analytics / events. - Describe each screen/interaction at mock level: layout intent, controls, copy, and state changes. - Acceptance criteria that are precise and testable. - Telemetry: the events/properties needed to measure success. ## Deliverables 1. The full spec in Markdown with the sections above. 2. A state/edge-case table (state → expected behavior). 3. Open questions and explicit assumptions, plus a suggested v1 cut line. Write decisively with stated assumptions; ask only if genuinely blocked.