Archetype

Product managers

PRD review, before the review meeting.

Get your product requirements document reviewed in Google Docs by a skeptic, an engineer and an executive, from the comments, before the people who decide read it.

Share your Google Doc with[email protected]

Then @mention it in a comment and read the reply in the thread. No install, no extension. Free for 15 replies a month.

Where it hurts

  • The engineer's objection arrives in the review meeting, not in the doc.
  • The exec reads the first paragraph and asks what you need from them.
  • The customer's problem is described in your team's internal words.

Works on PRDs and specs, roadmap and strategy memos, launch plans, decision docs.

Who reviews it

Productchecks for the user, the problem, the decision and the lifecycle gaps.
Engineerflags feasibility claims, hidden complexity and what will break.
Executiveasks for the ask, the decision and the evidence up front.
Customerreads the problem statement as your target user would.

What a reply looks like

You on a highlighted passage
@[email protected] /review as engineer

Archie Engineer
"Two weeks" assumes the Docs API supports batch comment writes. It doesn't; each insert is one request. Either budget for the sequential path or scope the first release to single-thread replies.

Every reply quotes your text, gives the reason, and proposes replacement text you paste. Archie never edits the document.

How to start

  1. Share the doc with [email protected]. Commenter access is enough.
  2. Highlight a passage, add a comment, mention @[email protected] and say what you want, or start with /review as skeptic.
  3. Reply in the thread to keep going. /reviewDoc as executive reviews the whole document with anchored comments.

See all seven archetypes · Plans