grokbotwiki

ChatPRD

by Claire · 6 BotsContent & publishing Share link liveChecked

A product manager that keeps every spec and discovery doc inside ChatPRD

Summary excerpt from the creator’s share page. Not independently tested.

Open on x.ai and add to Grok BotOriginal post ↗Report a problem

What the share page says

A ChatPRD-first product manager. Specs, brainstorms, and discovery live in ChatPRD. Ground every doc in the existing corpus, meeting notes, the issue tracker, and product analytics. On GitHub, comment when a PR matches a spec and update the spec when it merges. Write the doc. Don't just talk about it.

Description as published on the x.ai share page when last checked (2026-11-01).

What its description mentions

Read automatically from the creator's own words and quoted below. Not a test: check the Bot's skills and routines before relying on any of it.

Apps it names
GitHub
Our take

Editorial notes

From the public description, not a test. Written by Grok Bot Wiki from the share-page text; we have not run this Bot. Reviewed .

Best for

A product manager already using ChatPRD for specs who wants GitHub pull requests checked against those specs automatically, and the spec kept current once a matching change ships.

Not for

A team without a ChatPRD workspace already in place, since the whole premise is that specs, brainstorms, and discovery already live there rather than in this chat.

What it does

Every answer is grounded in your existing body of specs, meeting notes, issue tracker, and product analytics rather than invented from scratch. When a GitHub pull request matches an existing spec, it leaves a comment connecting the two, and once that change merges it updates the spec to reflect what actually shipped. Its standing instruction is to produce the written document itself rather than just talking through what the document should say, so a request for a spec gets a drafted spec back, not a verbal outline.

First messages to try

  1. Draft a one-page spec for a saved-search feature, grounded in whatever related specs and meeting notes you already have access to.
  2. This pull request adds pagination to the search results. Does it match any existing spec, and should that spec be updated?
  3. Pull together what our product analytics show about search usage before I write the problem statement for this spec.

Apps and accounts

Its description mentions grounding every document in an existing ChatPRD corpus, meeting notes, an issue tracker, and product analytics, plus a GitHub connection for matching pull requests to specs.

Cautions

  • It depends on a ChatPRD workspace and issue tracker already populated with real specs and notes; without that grounding material it has little to draw on.
  • Check that the pull request it matched to a spec is actually the right one before trusting an automatic spec update, especially on a repo with many small pull requests.

Compare with: Feature Request Tracker by SpaceXRequirement Engineer Bot by Fish

Before you add it

Specific to this Bot, from what its description says:

  • It names GitHub. Connect those as plugins where one exists rather than signing in through the shared browser, and give it the narrowest access the task needs. What to check for GitHub ↗
The standard checks for any shared Bot

Adding a shared Bot copies its profile, settings, enabled skills, routines, and avatar into your account. It does not copy the creator's computer, logins, conversation history, or memory. Everything it then does runs on your shared Agent Computer with your logins.

  • Open the Bot's skills and routines first. Disable any routine before it fires on a schedule you did not choose.
  • Check which apps it will try to sign into. Prefer plugins over browser logins, and keep sensitive accounts off the shared computer.
  • Set an ask-first rule for anything that sends, posts, pays, or deletes. A listing here is not a test result.
  • Give it one small bounded task and read the usage screen afterwards before scaling up.

Related reading: the shared computer permission boundaries the weekly meter

If it misbehaves: Bot not responding routines not running sign-in errors New to Grok Bot? what it is your first task

Attribution

This Bot belongs to its creator, Claire. Facts on this page (name, share link, creator, link status) were read from the public share page. The row was seeded from majiayu000/awesome-grok-bot, ZeroPointRepo/GrokBotDev, elie222/botdirectory.ai and kydlikebtc/awesome-grokbot. Imported catalog prose retains CC BY 4.0 attribution; share-page excerpts are labeled separately. Grok Bot Wiki is independent and not affiliated with SpaceXSI (formerly xAI).

Made this Bot? Add a “Listed on Grok Bot Wiki” badge

Optional and free. It links readers to this page and never affects how the Bot is listed. More badge styles ↗

Markdown (README)

[![Listed on Grok Bot Wiki](https://www.grokbotwiki.com/badge/listed-dark.svg)](https://www.grokbotwiki.com/bots/chatprd)

Or promote this template in the labelled Featured row, from $19.