To run this task you must have the following required information:

> Feature idea or problem to solve. Optional: user persona, success metrics, constraints.

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/product.prd.guide.md` (Get the PRD template and writing guidance)

2. [Read Human-Style Prose]: Read the documentation in: `./skills/sauna/[skill_id]/references/shared.prose.style.md` (Reference for clear writing)

3. Gather context from the user. A good PRD needs clarity on:

1. **The Problem**
   - What problem are we solving?
   - Who experiences this problem?
   - What evidence do we have? (data, feedback, support tickets)

2. **The User**
   - Who is the primary user?
   - What's their current workaround?
   - What would success look like for them?

3. **The Solution**
   - What's the proposed approach? (high level is fine)
   - What should it definitely do? (must-haves)
   - What's explicitly out of scope?

4. **Success Criteria**
   - How will we measure success?
   - What metrics matter?

5. **Constraints**
   - Timeline or deadline?
   - Technical limitations?
   - Dependencies on other teams?

Check `./documents/product/profile.yaml` for existing product/user context.
Ask for any missing critical inputs before drafting.


4. Draft the PRD using the template from the guide:

1. Start with a clear, specific problem statement
2. Write a concrete user story with real context
3. Describe the solution with specific capabilities
4. Make acceptance criteria testable and verifiable
5. Include realistic success metrics
6. Be explicit about scope (in and out)
7. List known risks with mitigations
8. Note open questions honestly

Output the complete PRD in markdown format.
Don't pad with generic content—if something is unknown, list it as an open question.


5. After presenting the PRD:
- Ask if any sections need expansion or clarification
- Offer to iterate on specific sections
- If new competitive insights, user research, or product positioning
  was developed during this task (e.g., competitive analysis, refined
  personas, new differentiators), offer to update `./documents/product/profile.yaml`:
  "I developed some [competitive analysis / user insights / positioning]
  while writing this PRD—want me to add it to your product profile so
  it's available for future content?"