product-planner

To turn a product idea into a PRD, provide a brief concept to generate structured product specs, Given/When/Then user stories, acceptance criteria, and a prioritized backlog. This workflow converts ambiguity into a structured plan for development and stakeholder alignment.

Defining MVP scope and success metrics requires outlining the problem definition and applying structured planning templates. This approach ensures you isolate the core feature requirements, establish measurable criteria, and avoid common planning anti-patterns.

Writing user stories in Given/When/Then format involves translating problem definitions into structured acceptance criteria. Inputting an initial idea generates these formatted stories alongside priorities and estimates to guide development.

Yes, you can use this for planning both new products and feature updates. It applies to starting new products, features, or projects by outlining problem definitions, user stories, MVP scope, and success metrics.

Prioritizing a product backlog and avoiding mistakes involves using provided templates for backlog prioritization alongside anti-pattern guidance. This ensures structured priority and estimate allocation for your defined user stories.