Product requirements (PRD)

Who it's for

Software PMs, business analysts, and indie devs writing specs for themselves.

Common challenges

Templates stall halfway; review edits desync copies; edge cases get missed.

How WriteX helps

Markdown PRDs fit Git review. The agent expands one-liners into stories, acceptance criteria, and edge flows; attach prior PRDs for delta-style updates.

Typical workflow

  1. Copy template-prd.md for the feature.
  2. Background + goal paragraphs.
  3. Agent fills stories and AC lists.
  4. Link meeting notes under meetings/.
  5. Snapshot before dev kickoff.

Practical tips

Ask the agent to flag assumptions as TBD; template MoSCoW priority fields.