Grok Bots for product work: a spec an engineer can build from without asking six questions, interview transcripts turned into findings that carry their evidence, documentation written for the moment somebody got stuck, release notes a customer understands, the launch plan worked backwards from the date, and product strings translated properly.
Spec PRD Bot
A spec an engineer can build from
Quote Interview Bot
Synthesis with the quotes that earned it
Notes Changelog Bot
What changed and what it means for the user
Guide Docs Bot
The page they needed, in the product's voice
Locale Strings Bot
Product copy in the other language, not a machine dump
Ship Launch Bot
The launch checklist that actually ships
A template has headings. Spec makes decisions: what we are building, what we are explicitly not building, every state including the empty and the error ones, and how you know it worked. It also marks which parts are assumptions so somebody can correct four lines instead of rewriting a document.
It is written not to. Every finding carries at least two verbatim quotes and a count of how many participants said it out of how many, plus the disconfirming evidence and what would have to be true for the finding to be wrong.
Guide writes task pages rather than feature tours, tests the steps against the real product where it can, and marks which steps it could only infer.
They are included in the BrowserMoon licence, one payment for every design template and every Bot template.