Turn a rough idea into a tight PRD, user stories, and a scoped plan you can actually build.
A good PRD turns a fuzzy idea into something a team can build. These prompts take a rough concept and produce a tight product requirements doc, user stories, and a scoped plan — focused on decisions and tradeoffs, not boilerplate. They're built to sharpen scope, not bloat it. Each runs on your own key from a version that shipped.
Feed it a half-formed feature idea and get a one-page PRD: problem, users, scope, non-goals, success metric, and open questions.
Paste a raw interview transcript and get verbatim pains, jobs-to-be-done signals, the strongest quote, and what to build/ask next.
Translates an 'it's broken' message into a triage-ready ticket: steps to reproduce, expected vs actual, severity, and the first place to look in the code.