PRD template
Generate a product requirements doc with your agent, then share a link engineering and design comment on inline — no more “which version of the PRD?”
What it is
A PRD (product requirements doc) is the shared source of truth for what you're building and why — the problem, the users, the scope, and how you'll know it worked.
A good PRD is read by everyone and owned by one person. The hard part was never the writing — it's keeping one version everyone's reacting to. Draft it with your agent, share the link, and the comments land on the exact requirement.
Generate it with your agent
claude
❯
Draft a PRD for {feature}. Cover: the problem and who has it, the goal and success metric, the user stories, what's in and out of scope, open questions, and a rough timeline. Then publish it to Drafty so I can share a link and collect inline comments — no account needed to reply.▌
See it on a real one
Live canvas — comment on any elementOpen ↗
What goes in a PRD
- Problem — who has it, and how you know it's real.
- Goal + metric — what success looks like, in a number.
- User stories — the jobs, in the user's words.
- Scope — in, out, and the things you're deliberately not doing.
- Open questions — the unknowns, named so they're not forgotten.
When to use one
When more than two people need to agree on what you're building before it's built. For a quick spike, a one-pager is enough — reach for a PRD when the cost of building the wrong thing is high.
Share the link, collect the comments inline, and your agent ships the revision on the same URL — with version history.