Most “AI prompts” lists miss the point for a product manager. The value of ClickUp Brain prompts is not clever wording — it is that Brain runs them inside your workspace, so it already knows the tasks, the doc, and the thread you are talking about. A great prompt pasted into a blank chatbot still needs you to paste all the context first. The same prompt in Brain just works. Below are the six I actually paste, organized by the PM job they do.
After thirty years in product, my rule for all of them is the same: AI drafts, the human decides. Every prompt here produces a fast first pass you edit — never the record of truth. Use them to skip the blank page, then apply the judgment only you have.
Disclosure: some links below are affiliate links. If you start a paid ClickUp plan through them, VetAI Works may earn a commission at no extra cost to you. I only recommend tools I would set up myself.
Brain needs a paid plan, but you can test these on ClickUp’s free-forever plan with an AI trial — no card needed.
Try ClickUp free →How to use these prompts
Open Brain from the task, Doc, or space you are working in — that is what gives it context. Where a prompt says @reference, use ClickUp’s @-mentions to point Brain at the exact task or doc instead of pasting text. Then read the output like a skeptical editor: verify the one caveat it might have dropped before anything reaches a stakeholder.
1. Draft a PRD from messy notes
Use it when you have a pile of kickoff notes and need a structured PRD to react to instead of a blank page.
Draft a PRD from @[notes doc] using this structure:
Problem · Goal & non-goals · Users & jobs · Requirements (must/should/could)
· Success metrics · Risks & open questions.
Flag anything ambiguous as an open question rather than guessing.The “flag, don’t guess” line is what makes it useful — it surfaces the decisions you still owe instead of inventing them.
2. Turn a story into subtasks and acceptance criteria
Use it when you are grooming the backlog and want a first cut of the work and the “done” definition.
Break @[this story] into subtasks, and write acceptance criteria in
Given/When/Then form. Call out any dependency or edge case the story
doesn't mention. Keep subtasks small enough to finish in a day.Brain reads the linked story, so the edge cases it flags are grounded in your actual ticket — not a generic template.
3. Roll up roadmap status
Use it when you need to know what is slipping before the roadmap review, not during it.
Roll up the status of @[this space] into three buckets: on track,
at risk, slipped. For each at-risk or slipped item, name the blocker
and the owner. Keep it to a scannable list, newest changes first.4. Synthesize a retro into actions
Use it when a retro generated a wall of notes and you need themes and owned actions, not a list nobody revisits.
Cluster @[retro board] notes into 3–5 themes. For each theme, write
one concrete action item with a suggested owner. Separate "keep doing"
from "change." Ignore one-off venting that isn't actionable.5. Write the weekly stakeholder update
Use it when it is Friday and you are about to rebuild the same status email by hand.
Write a weekly stakeholder update from the tasks that changed in
@[this space] this week. Format: Shipped / At risk / Next — one line
each, plain language for non-technical execs, and link the key tasks.What it returns — drafted from the live tasks, nothing pasted
⚠ At risk: billing migration (blocked on vendor)
→ Next: close migration, start reporting v2
6. Ask the workspace a direct question
Use it when you would otherwise hunt across tasks, docs, and chat to answer one question.
What is blocking the [payments] epic right now, and who owns each
blocker? Answer only from the workspace; if something is unclear,
say so instead of assuming.The “say so instead of assuming” guardrail matters — it is how you keep a confident summary from quietly papering over a gap.
→ These six plus ten more — with variations and guardrails: the PM’s AI Toolkit (16 prompts)
The mistakes to avoid
- Pasting context Brain already has. The whole advantage is the @-reference. If you’re pasting the task in, you’re using it like a plain chatbot.
- Shipping the first draft. Brain will drop the one caveat that mattered. Edit before it reaches a stakeholder.
- Expecting context that isn’t there. Thin workspace, thin answers. Brain is only as good as what’s actually captured in ClickUp.
- Forgetting it’s metered. Everyday Brain chat is included on a paid plan, but agents and automations draw on a credit pool — watch it.
Run these prompts with your workspace context — start free
| ChatGPT + Claude + Gemini | One subscription |
| Knows your tasks & docs | No pasting context |
Get the full prompt library
The six above are a taste. Each VetAI pack is a focused set of battle-tested prompts for one PM job — grab the one that matches your work, or the Bundle for all three.
| Pack | Prompts | For | Price |
|---|---|---|---|
| PM’s AI Toolkit | 16 | PRDs, sprints, stakeholder comms | $79 |
| Software Estimation Pack | 14 | Effort estimates, delivery forecasts | $79 |
| Due Diligence Pack | 12 | Vendor eval, build-vs-buy | $79 |
| Complete Bundle | 42 | All three packs, one download | $199 · save $38 |
FAQ
What are the best ClickUp Brain prompts for product managers?
The ones tied to a repeated PM job: drafting a PRD from notes, turning a story into subtasks and acceptance criteria, rolling up roadmap status, synthesizing a retro, writing the weekly stakeholder update, and asking the workspace a direct question. Each works best when you @-reference the task or doc so Brain uses real context.
Do ClickUp Brain prompts work differently from ChatGPT prompts?
The wording is portable — the same prompt works in either. The difference is context: in Brain it reads your tasks and docs directly, so you skip the copy-paste step. See ClickUp Brain vs ChatGPT & Claude for the full trade-off.
Do I need a paid plan to use Brain prompts?
Brain runs on a paid ClickUp plan (~$9/user/mo on top), but you can trial it on the free plan first to see whether the workspace context earns the cost for your team.
How do I give Brain the right context?
Open Brain from the relevant task, Doc, or space, and use @-mentions to point it at specific items. The more your work actually lives in ClickUp, the better its answers.
Founder, VetAI Works · 30 years in product & IT. Writes practitioner guides on AI for product managers.