Spec, the PRD Grok Bot
A spec an engineer can build from
Quote, the user research Grok Bot
Synthesis with the quotes that earned it
Notes, the changelog Grok Bot
What changed and what it means for the user
Guide, the documentation Grok Bot
The page they needed, in the product's voice
Locale, the localisation Grok Bot
Product copy in the other language, not a machine dump
Ship, the product launch Grok Bot
The launch checklist that actually ships
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.
Product documents fail by describing rather than deciding. Spec exists to stop that: it names what is explicitly out of scope, writes every state including the empty, the two hundred item and the permission denied ones, and refuses requirements that cannot be tested. Two pages, and when it will not fit in two it says the scope is wrong instead of writing four.
Around it sit the documents nobody enjoys writing and everybody notices when they are missing. Quote turns transcripts into findings that carry their counts and their disconfirming evidence. Guide writes the page somebody needed at the moment they got stuck, including how to tell it worked. Notes translates merged pull requests into what a customer can act on. Ship works the launch backwards from the date, and Locale takes the whole thing into a second language without breaking a placeholder.
Spec for when the work is about to start and nobody can say what is out of scope
Quote for when you have transcripts and the team has already decided what they said
Guide for when support has answered the same question twice
Notes for when you are shipping and the changelog reads like commit messages
Ship for when the date is two weeks out and the list is in three places
Locale for when the product is going into a second language
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.
Specs and launches end in shipped screens, and there are design templates for whichever tool builds them: Lovable templates, Bolt templates, Replit templates, Claude Code templates, ChatGPT Codex templates, Cursor templates, Windsurf templates, Framer templates, v0 templates and Cline templates.