Write a product spec (PRD) with user stories

Describe the problem and the idea in a few lines. Get a complete PRD: goals, scope, user stories with acceptance criteria, metrics, risks and open questions.

How to use it

1. Describe the problem Who has it, how often, what they do today.
2. Add constraints Deadline, team size, platforms, things you cannot change.
3. Review the open questions They are the decisions you still owe the team.

The prompt

You are a senior product manager. Write a product requirements document.

Product and feature: [FEATURE_NAME]

The problem and who has it: [PROBLEM]

The idea: [IDEA_DESCRIPTION]

Constraints: [CONSTRAINTS]

Sections: Background, Goals and non-goals, Users, User stories (each with acceptance criteria in Given/When/Then), Scope for the first release versus later, Success metrics with targets, Risks and mitigations, Open questions.

Be specific and testable. Mark any assumption you make as an assumption. Keep it under two pages.

Example result

Saved reports

Background

Owners of small businesses rebuild the same report filters every month (~10 minutes). Support tickets mention this weekly. Assumption: 30% of active users open reports at least monthly.

Goals and non-goals

Goals: make recurring reports a one-click action; reduce time to a repeat report from 10 minutes to under 30 seconds. Non-goals: custom charts, sharing with other people, mobile apps.

Users

Business owners and bookkeepers who open the same two or three reports each month.

User stories

1. Save a report. As an owner, I want to save the filters I used so that I do not rebuild them.
   • Given I have a filtered report open, when I click "Save" and enter a name, then it appears in "My reports".
2. Open a saved report. Given a saved report, when I click it, then the report opens with the current data and my saved filters.
3. Monthly email (later). Given a saved report, when I enable "email me monthly", then I receive a PDF on the 1st.

Scope

Release 1 (6 weeks): save, rename, delete, open. Later: email delivery, shared reports.

Success metrics

• 25% of monthly report users save at least one report within 60 days.
• Median time to repeat a report under 30 seconds.
• Support tickets about "rebuilding reports" down 50%.

Risks

• Saved filters break when a category is deleted → show a notice and fall back to "all".
• Two engineers is tight → email delivery is explicitly out of release 1.

Open questions

1. Do saved reports follow the company or the individual user?
2. Is there a limit on saved reports per account?
3. Which three reports do customers rebuild most? (Check the analytics before design.)