task icon Task

Write PRD

Requirements
Feature idea, problem context, and target users
1
slice icon Read PRD Writing Guide slice →
2

Gather information needed for the PRD:

PROBLEM CONTEXT

  • What problem are we solving?
  • Who has this problem? How severe is it?
  • What happens if we don't solve it?

PROPOSED SOLUTION

  • High-level description of the feature
  • Why this approach vs alternatives?
  • What's in scope vs out of scope?

USER CONTEXT

  • Primary user persona
  • User journey / workflow
  • Key user stories

SUCCESS CRITERIA

  • How do we know if this works?
  • What metrics will move?
  • What does success look like in 3 months?

CONSTRAINTS

  • Technical constraints
  • Business constraints (timeline, resources)
  • Dependencies on other work
3

Write the PRD with these sections:

OVERVIEW (2-3 paragraphs)

  • Problem statement
  • Proposed solution
  • Why now

GOALS & SUCCESS METRICS

  • Primary goal (what we're trying to achieve)
  • Success metrics (how we measure)
  • Non-goals (explicitly out of scope)

USER STORIES

  • "As a [user], I want to [action] so that [outcome]"
  • Cover primary and secondary use cases

REQUIREMENTS

  • Functional requirements (what it must do)
  • Non-functional requirements (performance, security, scale)
  • Edge cases and error states

DESIGN CONSIDERATIONS

  • UX considerations
  • Technical architecture notes
  • Open questions for design/eng

LAUNCH PLAN

  • Phased rollout if applicable
  • Feature flags / experiments
  • Documentation and support needs
4

Review for PRD quality:

  • Clear enough for engineering to estimate?
  • Success metrics are measurable?
  • Edge cases considered?
  • Dependencies identified?
  • Questions called out vs assumed?
 
                    To run this task you must have the following required information:

> Feature idea, problem context, and target users

If you don't have all of this information, exit here and respond asking for any extra information you require, and instructions to run this task again with ALL required information.

---

You MUST use a todo list to complete these steps in order. Never move on to one step if you haven't completed the previous step. If you have multiple read steps in a row, read them all at once (in parallel).

Add all steps to your todo list now and begin executing.

## Steps

1. [Read PRD Writing Guide]: Read the documentation in: `./skills/sauna/[skill_id]/references/prd.writing.guide.md`

2. Gather information needed for the PRD:

PROBLEM CONTEXT
- What problem are we solving?
- Who has this problem? How severe is it?
- What happens if we don't solve it?

PROPOSED SOLUTION
- High-level description of the feature
- Why this approach vs alternatives?
- What's in scope vs out of scope?

USER CONTEXT
- Primary user persona
- User journey / workflow
- Key user stories

SUCCESS CRITERIA
- How do we know if this works?
- What metrics will move?
- What does success look like in 3 months?

CONSTRAINTS
- Technical constraints
- Business constraints (timeline, resources)
- Dependencies on other work


3. Write the PRD with these sections:

OVERVIEW (2-3 paragraphs)
- Problem statement
- Proposed solution
- Why now

GOALS & SUCCESS METRICS
- Primary goal (what we're trying to achieve)
- Success metrics (how we measure)
- Non-goals (explicitly out of scope)

USER STORIES
- "As a [user], I want to [action] so that [outcome]"
- Cover primary and secondary use cases

REQUIREMENTS
- Functional requirements (what it must do)
- Non-functional requirements (performance, security, scale)
- Edge cases and error states

DESIGN CONSIDERATIONS
- UX considerations
- Technical architecture notes
- Open questions for design/eng

LAUNCH PLAN
- Phased rollout if applicable
- Feature flags / experiments
- Documentation and support needs


4. Review for PRD quality:
- Clear enough for engineering to estimate?
- Success metrics are measurable?
- Edge cases considered?
- Dependencies identified?
- Questions called out vs assumed?