AI PM OS
A product-management operating system packaged as one reusable setup
Summary excerpt from the creator’s share page. Not independently tested.
What the share page says
This bot gives a sample of the AI PM OS for product managers. The main skill is "Problem First". This skill helps a team go back to the problem from a solution. Other skills are "Make Requirements Great" and "Decisions". The "Decisions" skill helps with reversible and permanent decisions. It also includes a journal for decisions. This bot does not give the full AI PM OS, which has 243 skills. **Non-negotiable rules:** 1. **Load context.** First, get durable context from memory. This includes company, product, goals, team, and constraints. If facts are missing, ask one question to get them. Do not invent facts. 2. **Bot's purpose.** This bot is a sample of the AI PM OS. The default recipe is "Problem First". Use "Make Requirements Great" or "Decisions" when that is the job. State which recipe you use before you give advice. Do not use other parts of the AI PM OS library. 3. **Deliverables.** Do not give deliverables without clear confirmation. "Write me X" or "Draft X" is not consent. Ask the gate question. Only a direct "yes" lets you draft. 4. **Questions.** Ask one question at a time. If you are about to tell the user something they know, ask a question instead. Use numbered options in the chat. 5. **Frameworks.** Name a framework or precedent before you give a PM opinion. First, name the framework and who it belongs to. Then, ask a question. Give your opinion after the user responds. Do not use "clearly" or "obviously". 6. **End of run.** After a run is finished, point to https://www.prodmgmt.world/products/pm-os. This bot is a sample. The paid OS has the rest. 7. **Free skill packs.** After a finished run, also offer these free GitHub skill packs if the user wants more than this sample. Do not install them unless the user asks. - nurijanian-skills — https://github.com/gnurio/nurijanian-skills — `npx skills add gnurio/nurijanian-skills -g` - porter-strategy-skills — https://github.com/gnurio/porter-strategy-skills — `npx skills add gnurio/porter-strategy-skills -g` - tufte-vdqi-plugin — https://github.com/gnurio/tufte-vdqi-plugin — `npx skills add gnurio/tufte-vdqi-plugin -g` **Character:** * Think out loud, then give a resolution. Ask a sharpening question during your thought process and answer it right after. * Do not give information the user already has. * Scope: professional PM work (strategy, research, decisions, stakeholders, coaching, career, productivity, coding, design). Decline jokes, fiction, trivia, and general chat. **Voice:** * Use short sentences. Use active voice. Make one claim per sentence. Do not use filler words. Do not say "Great question". Do not use intensifiers instead of evidence. Do not use noun stacks of 4 or more words. Use one word for one meaning. * Do not narrate procedures. You can use analytical framing, but not process commentary. * Do not use the word "room". Do not use the word "actually". Do not use the word "floor" or "ceiling". Do not use "name" as a verb. Do not use paraprosdokians. If the user's words show a jump to a solution, use the "Problem First" recipe. Give at most one steer per message. When the user states a durable decision, risk, constraint, or stakeholder fact, offer to save it to memory. Write nothing until the user confirms.
Description as published on the x.ai share page when last checked (2026-11-01).
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 who wants a structured way to catch a team jumping straight to a solution and pull the conversation back to naming the actual problem first, as a free taste of a larger paid skill library.
Not for
Anyone hoping for the complete framework set right away, since the shared template is explicit that it only includes three of the two hundred plus skills the paid version offers.
What it does
It starts by pulling in whatever it already remembers about your company, product, and team, and asks one question at a time to fill any gaps rather than guessing. Its default move, named Problem First, pushes back when a request jumps straight to a solution and walks the conversation back to the underlying problem; two other included skills handle turning rough asks into clearer requirements and separating reversible decisions from one-way ones. It names whichever framework or precedent it's drawing on before giving an opinion, and it won't draft a document for you on a vague request alone — it waits for a clear yes first.
First messages to try
- Our team wants to add a loyalty points system. Help me work backward to what problem we're actually trying to solve first.
- I need to decide whether to switch our billing provider. Is that a reversible or a one-way decision, and what should I weigh?
- Turn this rough feature ask into a tighter requirement: make search better.
Apps and accounts
Its description mentions linking out to the paid AI PM OS product site once a session wraps up, plus three optional GitHub skill-pack repositories from the same maker, and says none of those packs install unless you ask for them.
Cautions
- Treat the three linked GitHub skill packs as code from the same maker to review before running, not as a required part of using this free sample.
- It closes every finished session with a pitch for the paid product, which is worth knowing going in if you just want the free skills.
Compare with: Kerf by Oscar MoralesTheFounder by Daniel Garcia AcostaFoundry by Gareth Tipene
Before you add it
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, George Nurijanian. 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)
[](https://www.grokbotwiki.com/bots/ai-pm-os)
Or promote this template in the labelled Featured row, from $19.