Turn a feature idea into a spec the team can build from: problem, user stories with acceptance criteria, edge cases, and explicit non-goals.
Write a spec for: {{feature}} (the idea, who it's for, why now, any constraints).
Structure: Problem (the user's situation and evidence it's real — if I gave no evidence, flag it), Goals and NON-goals (the non-goals section prevents half the scope arguments), User stories with acceptance criteria (given/when/then — testable, not vibes), the edge cases by category (empty states, permissions, concurrent use, limits, the unhappy paths), open questions with owners, and success measurement (the metric, its current baseline, and when we'll look). Keep design solutions OUT of the problem section — describe the problem so well that the team might find a better solution than mine.
Fields like {{ this }} are placeholders — replace them with your own details, or let Aria ask you for them.
This prompt runs with Aria connected to your email, files, CRM and 40+ other services — and you can schedule it to run automatically.
Start Free WeekTurn a feature idea into a tight one-page product spec.
Break a feature into user stories with acceptance criteria.
Generate a structured SWOT for a decision or business.
Get a tough, constructive critique of a plan or doc.
Explore three pricing models for your product — tiers, psychology, and risks — with the recommendati...
Design in-product feedback prompts that get signal, not noise: the right question at the right momen...