task icon Task

Improve PRD Draft

Requirements
Draft PRD text
2

Analyze the PRD for:

CLARITY

  • Is the problem clearly stated?
  • Can engineering build from this?
  • Are requirements specific or vague?

COMPLETENESS

  • Missing sections?
  • Edge cases covered?
  • Success metrics defined?

SCOPING

  • Clear what's in/out of scope?
  • Appropriately sized for timeline?
  • Dependencies identified?

ALIGNMENT

  • Ties to business goals?
  • User stories make sense?
  • Success metrics connect to goals?
3

Score the PRD on each dimension (1-10):

CLARITY: [X]/10 — Problem statement, requirement specificity, buildability
COMPLETENESS: [X]/10 — All sections present, edge cases, metrics defined
SCOPING: [X]/10 — In/out of scope clear, sized appropriately, dependencies
ALIGNMENT: [X]/10 — Business goals, user stories, metrics connection

OVERALL: [avg]/10 — Grade: [A/B/C/D/F]

Scoring guide:
9-10 = Ready to build | 7-8 = Minor gaps | 5-6 = Needs work | <5 = Major rewrite

4

Provide specific feedback:

  • What's strong and should be kept
  • What's missing or unclear
  • Questions engineering will ask
  • Risks not addressed
5

Offer improvements for each weak area.
Prioritize the most critical gaps that would block progress.

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

> Draft PRD text

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. Analyze the PRD for:

CLARITY
- Is the problem clearly stated?
- Can engineering build from this?
- Are requirements specific or vague?

COMPLETENESS
- Missing sections?
- Edge cases covered?
- Success metrics defined?

SCOPING
- Clear what's in/out of scope?
- Appropriately sized for timeline?
- Dependencies identified?

ALIGNMENT
- Ties to business goals?
- User stories make sense?
- Success metrics connect to goals?


3. Score the PRD on each dimension (1-10):

CLARITY: [X]/10 — Problem statement, requirement specificity, buildability
COMPLETENESS: [X]/10 — All sections present, edge cases, metrics defined
SCOPING: [X]/10 — In/out of scope clear, sized appropriately, dependencies
ALIGNMENT: [X]/10 — Business goals, user stories, metrics connection

OVERALL: [avg]/10 — Grade: [A/B/C/D/F]

Scoring guide:
9-10 = Ready to build | 7-8 = Minor gaps | 5-6 = Needs work | <5 = Major rewrite


4. Provide specific feedback:
- What's strong and should be kept
- What's missing or unclear
- Questions engineering will ask
- Risks not addressed


5. Offer improvements for each weak area.
Prioritize the most critical gaps that would block progress.