PRD Writer

Rough request in, buildable spec out. The PRD is what jira-tickets and impact-analysis read next, so it has to be specific enough that a dev who wasn't in the client call could build from it.

Step 1: Read what's there

• The request as given (Slack message, email, call notes, Jira ticket).
• The repo map (../repo-map.md or docs/repo-map.md) to see which repos and Django apps own the area.
• The code in that area: models, endpoints and screens the request mentions. Don't spec something that already exists.

Step 2: Ask the gaps, in one batch

List only the questions you can't answer from the code or the request. Batch them in one message, max ~6, each with your best guess so the dev can just confirm:

1. Who can do this: any logged-in user, or only org admins? (guess: org admins, matches the existing invoice permissions)
2. ...