Grok Bot product prompts that keep facts and guesses apart
Official product-performance use case: investigate with dashboards and traces, return a short write-up with screenshots and links, separate facts from hypotheses. You change the product.
In short: This page contains 21 copy-paste ready prompts, organized into 5 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.
Performance and metrics
4 promptsActivation step-change
1/21✨ What it does
The Bot compares new-user activation this week to the previous four weeks, names the funnel step that moved the most, and drafts an investigation plan with chart links. You pick the next chart.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Compare new-user activation this week vs the previous four. Identify the largest step-level change. Draft an investigation plan with chart links. Do not change dashboards. Sources: [ANALYTICS], [FUNNEL DEFINITION], [RELEASE LIST]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not change dashboards or feature flags. Ask me to sign in if needed. Deliverable: Step, delta, chart links, plan, facts vs hypotheses. Review point: I pick the next chart.
Pro tip: Name the funnel steps. "Why is activation down" without steps is a novel.
Release-impact note
2/21✨ What it does
The Bot writes a short report on how [RELEASE] changed [METRICS] between [TIME] and [TIME], with links to the charts it used. You decide whether to keep the release or roll it back.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Impact note for [RELEASE] from [TIME] to [TIME] on [METRICS]. Sources: [ANALYTICS], [ERROR TRACKER], [SUPPORT VOLUME], [CHANGELOG]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not revert or flag-flip. Deliverable: Metric, before/after, related errors, support themes, links. Review point: I decide ship-forward or rollback.
Pro tip: Pin the release time. Otherwise every dip is "probably the release".
North-star and counter-metrics
3/21✨ What it does
The Bot writes a weekly read of [NORTH STAR] plus the counters in [LIST], with one sentence per move and links. You take it to the review.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Weekly read of [NORTH STAR] plus counters [LIST]. Sources: [DASHBOARD], [DEFINITION DOC]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not change the dashboard. If a definition is missing, say so. Deliverable: Number, window, counter-metrics, one sentence per move, links. Review point: I take it to the review.
Pro tip: If you do not name counters, the Bot will celebrate a vanity spike.
Experiment readout draft
4/21✨ What it does
The Bot drafts a readout for [EXPERIMENT] from [TOOL], including sample size, window, and whether anyone peeked early. You decide ship or hold.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft a readout for [EXPERIMENT] from [TOOL]. Include sample, window, and whether we peeked. Sources: [EXPERIMENT TOOL], [PRE-REG DOC IF ANY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not stop or ship the experiment. Deliverable: Result, uncertainty, peeking, recommended decision for me. Review point: I decide.
Pro tip: Ask for sample size and peeking risk. Ban "it is winning" without a window.
Prompts get you started. Tutorials level you up.
A growing library of 300+ hands-on AI tutorials. New tutorials added every week.
Discovery and feedback
4 promptsInterview synthesis with quotes
5/21✨ What it does
The Bot synthesizes [N] interviews on [TOPIC] into themes that each carry real quotes. You share it with the team.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Synthesize [N] interviews on [TOPIC]. Themes must carry quotes. Sources: [NOTES OR TRANSCRIPTS], [RESEARCH Q]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email participants. Do not invent quotes. Deliverable: Theme, quotes, outliers, open questions. Review point: I share with the team.
Pro tip: If a theme has no quote, it is a guess. Label it.
Feedback to opportunity
6/21✨ What it does
The Bot turns this month's feedback into [N] opportunities with the job the user is trying to do and how many times it showed up. You prioritize.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Turn this month's feedback into [N] opportunities with JTBD and evidence count. Sources: [SUPPORT], [CALLS], [NPS], [SALES NOTES]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not promise features in any customer channel. Deliverable: Opportunity, JTBD, evidence, counter-evidence, suggested next research. Review point: I prioritize.
Pro tip: Job-to-be-done first. Button requests last.
Win/loss from call notes
7/21✨ What it does
The Bot pulls win/loss themes for [QUARTER] from [CALL NOTES] and will not use price as the only reason unless someone said it. You take it to leadership.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Win/loss themes for [QUARTER] from [CALL NOTES]. Price cannot be the only reason unless quoted. Sources: [CRM], [CALL NOTES], [COMPETITOR MENTIONS]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email lost deals. Deliverable: Theme, quotes, segment, suggested product or packaging question. Review point: I take it to leadership.
Pro tip: Force a second reason after price. Price is the lazy bucket.
Persona drift check
8/21✨ What it does
The Bot compares [THIS MONTH REQUESTS] to [ICP / PERSONA DOC] and flags where the work is drifting off the customer you said you serve. You update strategy if needed.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Compare [THIS MONTH REQUESTS] to [ICP / PERSONA DOC]. Flag drift. Sources: [ICP], [ROADMAP], [FEEDBACK]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not change the persona doc. Deliverable: Fits ICP / drifts, examples, question for me. Review point: I update strategy if needed.
Pro tip: Compare this month's requests to the ICP doc. Drift is a finding, not a vibe.
Specs and launches
4 promptsSpec diff vs what shipped
9/21✨ What it does
The Bot compares [SPEC] to [STAGING OR PROD] for [FEATURE] and lists drift with screenshots. You file the follow-ups.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Compare [SPEC] to [STAGING OR PROD] for [FEATURE]. List drift with screenshots. Sources: [SPEC DOC], product in the browser. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not edit the spec or the product. Deliverable: Spec claim, actual, screenshot, suggested owner (product / eng / docs). Review point: I file follow-ups.
Pro tip: Computer use. Screenshot the mismatch. Do not "update the spec" on live.
Launch QA as a stranger
10/21✨ What it does
The Bot walks [LAUNCH URL] as a new user on a test account and files friction with screenshots. You file the tickets.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Walk [LAUNCH URL] as a new user on a test account. File friction with screenshots. Sources: Live or staging URL, [EXPECTED COPY], [TEST ACCOUNT VIA SECRETS]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not use customer data. Do not submit a real signup. Deliverable: Step, expected, actual, severity, screenshot. Review point: I file tickets.
Pro tip: Official: fresh test account, no production customer data.
PRD skeleton from a problem
11/21✨ What it does
The Bot drafts a first outline of a product brief for [PROBLEM] with goals, non-goals, unknowns, and success metrics, and writes TBD where a number is undefined. You write the real brief.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft a PRD skeleton for [PROBLEM] with goals, non-goals, unknowns, and success metrics. Sources: [RESEARCH], [CONSTRAINTS], [ANALYTICS DEFINITIONS]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not share the PRD. If a metric is undefined, write TBD. Deliverable: Skeleton plus a TBD list. Review point: I write the real PRD.
Pro tip: Ask for unknowns. A PRD with no unknowns is fiction.
Kill or keep a bet
12/21✨ What it does
The Bot writes a kill-or-keep memo for [BET] against [PRE-REGISTERED BAR], and says so if no bar was written down in advance. You kill it or you keep it.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Kill/keep memo for [BET] against [PRE-REGISTERED BAR]. If no bar exists, say so. Sources: [EXPERIMENT OR METRICS], [ORIGINAL BRIEF]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not turn the flag off. Deliverable: Bar, result, recommendation, what would change it. Review point: I kill or I keep.
Pro tip: If there was no success bar, the memo should say that, not invent one after the fact.
Like these prompts? There are full tutorials behind them.
Learn the workflows, not just the prompts. 300+ easy-to-follow tutorials inside AI Academy — and growing every week.
Roadmap and comms
3 promptsRoadmap change log
13/21✨ What it does
The Bot diffs [ROADMAP A] vs [ROADMAP B] into what slipped, what was added, and why if a source exists. You explain it to the team.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Diff [ROADMAP A] vs [ROADMAP B]. Slipped, added, reasons if sourced. Sources: Two dated roadmap files or views. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not edit the roadmap. Deliverable: Table plus unknown reasons. Review point: I explain it to the team.
Pro tip: Compare two dated roadmap snapshots. Memory is not a source.
Internal launch note
14/21✨ What it does
The Bot writes an internal launch note for [FEATURE] with who it is for and what not to say. You post it.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Internal launch note for [FEATURE] with do-not-say. Sources: [SPEC], [PRICING], [SUPPORT MACROS]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not post to Slack or email the company. Deliverable: Note, audience, do-not-say, links. Review point: I post.
Pro tip: Include the do-not-say. Support will otherwise invent pricing.
Sales ask vs roadmap
15/21✨ What it does
The Bot rolls up this week's sales asks against [ROADMAP] and will not add dates unless they are already public. You reply to sales.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Roll up sales asks this week vs [ROADMAP]. No dates unless already public. Sources: [SALES NOTES], [ROADMAP], [PUBLIC ROADMAP IF ANY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email sales or customers with dates. Deliverable: Ask, fit, public-or-not, draft internal reply. Review point: I reply to sales.
Pro tip: Ban dates unless they are already public. The Bot will be "helpful".
Make the PM Bot durable
6 promptsProduct Bot description
16/21✨ What it does
The Bot writes a product-performance description named [NAME] that investigates, keeps links, and never changes production. You create the Bot.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write a product-performance Bot description named [NAME]. Sources: [OBSERVABILITY], [ANALYTICS], [REVIEW WINDOW]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Never change production settings or feature flags. Deliverable: Description, write-up format, never-do. Review point: I create the Bot.
Pro tip: Official example Bot: product performance, evidence first, never change production settings.
Monday metrics routine
17/21✨ What it does
The Bot writes a Monday job that posts last week's activation and north-star read and changes no dashboards. You turn it on.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Mondays, post the activation and north-star read for last week. Do not change dashboards. Sources: [DASHBOARDS]. If they are down, fail closed. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not change flags or dashboards. Deliverable: Routine card and report format. Review point: I enable.
Pro tip: Official: use a routine for a recurring health report, not unsupervised production changes.
What product Bots never do
18/21✨ What it does
The Bot writes a never-do list for product Bots from your rules, such as [E.G. NO FLAG FLIPS, NO PRICING, NO DATES TO CUSTOMERS], plus what a human does instead. You paste it into the Bot.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write the never-do list for product Bots. Sources: My rules: [E.G. NO FLAG FLIPS, NO PRICING, NO DATES TO CUSTOMERS]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. Deliverable: 12 never-do items and the human substitute. Review point: I paste it into the Bot.
Pro tip: Paste this next to the eng never-do. They share a computer.
Performance pack from real charts
19/21✨ What it does
The Bot pulls [METRICS] for [WINDOW] from [DASHBOARD], compares them to [TARGET], and lists three questions for the next review. You run the review.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Pull [METRICS] for [WINDOW] from [DASHBOARD]. Compare to [TARGET]. Do not change flags. Sources: [DASHBOARD], [NOTES]. If a chart is missing, say missing. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not change feature flags or experiments. Deliverable: What moved, links, 3 questions for the next review. Review point: I run the review.
Pro tip: Name the dashboard. "The product" is not a source.
Feedback cluster from the queue
20/21✨ What it does
The Bot clusters [N] tickets or calls about [FEATURE] into themes with source links and three quotes each. You pick a theme.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Cluster [N] tickets or calls about [FEATURE] into themes with source links. Sources: [QUEUE], [CALL NOTES]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email customers. Do not close tickets. Deliverable: Theme, count, 3 quotes, links. Review point: I pick a theme.
Pro tip: Cap the quotes. Ten real lines beat a synthetic user.
Spec that another Bot implements
21/21✨ What it does
The Bot writes a spec for [JOB] with in-scope, out-of-scope, and acceptance checks, and does not implement it. You hand it to engineering.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write a spec for [JOB] with in-scope, out-of-scope, and acceptance checks. Do not implement. Sources: [BRIEF], [CURRENT UI]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not open a PR. Do not change production. Deliverable: Spec doc path. Review point: I hand it to eng.
Pro tip: Write the out-of-scope list or the implementer will "helpfully" add it.
Free tool
Prompt Optimizer
Turn a rough idea into a structured, professional AI prompt.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.
Related guides