What is a PRD?
A product requirements document (PRD) describes what a product or feature must do and why, without prescribing how to build it. It gets product, design and engineering to agree on the problem, the users and what done looks like.
A good PRD is short. It states the goal, lists user stories with clear acceptance criteria and draws a firm line around scope, so the team can estimate and build without guessing.
How to write good user stories
Each story follows one format: as a [user], I want [action] so that [benefit]. Acceptance criteria use Given, When, Then to describe testable behaviour that developers and testers can turn straight into tests.
Keep each story small enough to build and ship on its own. If a story needs the word 'and' twice, split it.
Use it as a first draft
The generator gets you to a solid first draft. Review it with your team, answer the open questions and cut anything that doesn't serve the goal. Then it is ready for design and estimates.