For product managers and engineers
Design doc and PRD review, one reviewer at a time.
Write the doc in Markdown, or have ChatGPT or Claude draft it. Each reviewer edits in place, it comes back to you, and you decide who reads it next.
- Free during the beta
- Reviewers just need a browser
- Markdown supported
## Rollout
Ship behind a flag to all users 5% of uploads first, then ramp up over one week.
Failed jobs retry with backoff, capped at 10 5 attempts.
How it works
How design doc review works
Each reviewer gets the doc to themselves, then it comes back to you.
- Step 1
Share the doc
Paste your Markdown, or tell ChatGPT or Claude “send this RFC to Lena for review.”
- Step 2
One reviewer, full attention
The reviewer edits in place and comments on exact lines. Nobody else edits underneath them.
- Step 3
Resolve and route
Accept or dismiss each comment, then send it to the next reviewer, or mark the doc complete.
Why take turns
Why review a design doc in turns?
Everyone commenting at once feels fast, until you have to resolve it all.
| Everyone at once | One reviewer at a time | |
|---|---|---|
| Conflicting edits | Two people rewrite the same paragraph | Only the person holding the doc can edit |
| Fresh eyes | Reviewers react to each other’s comments | Each reviewer reads the latest version, with earlier feedback worked in |
| Open comments | Dozens left unresolved | You accept or dismiss each one, every round |
| The record | Scattered across threads | Every round: who reviewed it and what changed |
| The next version | Rewrite it by hand | Your AI reads the edits and drafts the next version |
A trail for every decision
Know why the doc says what it says
When someone asks why the rollout starts at 5%, open All versions: who reviewed it, what they changed, and which comments you accepted.
All changes lists every edit from a round in one place, so a reviewer’s pass is easy to check.
- Each round shows who reviewed it
- Comments keep their outcome: accepted or dismissed
- Take the doc back anytime if plans change
- v1You share the RFC with Lena on the platform teamShared
- Lena’s review4 edits, 3 commentsReviewed
- v2You accept 2 comments, dismiss 1, and change the rolloutRevised
- Omar’s reviewSecurity: 1 comment on retriesReviewed
- DoneYou mark the doc completeComplete
Ask better questions
What to ask a design doc reviewer
A focused question gets a focused review. Pick two or three when you send the link.
- Is the problem clear before the solution?
- What did we not consider?
- Which risk worries you most?
- Can we undo the rollout safely?
- What would you cut from version one?
- Who else should read this?
Use it for
Docs you can send for review
- Design docs
- PRDs
- RFCs
- Technical specs
- Architecture decision records
- Postmortems
- Launch plans
- Runbooks
- API docs
- Release notes
Paste Markdown. Headings, lists, tables and code blocks come through as written.