How we tested this
Reviewed against ClickUp Brain docs and project workflows in May 2026
We refreshed this guide by checking ClickUp's current public documentation for ClickUp Brain, Brain chat context, AI Fields, Docs, Chat, comments, and task-based AI workflows.
The prompts below are written for working teams. They ask for owners, dates, dependencies, decisions, acceptance criteria, risks, and review steps rather than generic productivity advice.
How to prompt ClickUp Brain
ClickUp Brain is most useful when the prompt tells it where to look and what to create. Instead of asking for project help, ask it to use a specific list, task, Doc, or space and output a status report, task plan, risk register, decision log, SOP, or sprint review.
Prompt map
ClickUp AI workflows and starter prompts
Pick the workflow first, then add the exact ClickUp location. That is what makes the answer specific to your workspace instead of a generic PM template.
| Job | Prompt focus | Starter prompt | Human check |
|---|---|---|---|
| Task creation | source doc, owner, due date, checklist, acceptance criteria | Using this project brief, create implementation tasks with owner suggestions, due-date logic, dependencies, acceptance criteria, and a Definition of Done checklist for each task. | Confirm owners, due dates, dependencies, and anything that affects delivery commitment. |
| Sprint planning | backlog quality, priority, velocity, risk, dependencies | Review this sprint backlog and propose the strongest sprint plan. Group related work, flag vague tasks, identify dependency risks, and recommend what should move out if capacity is tight. | Use team capacity and engineering judgement before locking the sprint. |
| Status reporting | task activity, completed work, blockers, next actions | Create a weekly project status report from tasks updated in the last 7 days. Include progress, completed work, risks, blockers, decisions needed, and next week's focus. | Remove noise, verify risk wording, and make sure leadership sees the decision needed. |
| Meeting notes | decisions, action items, owners, follow-up tasks | Summarize these meeting notes into decisions, action items, open questions, and follow-up tasks. Assign owners where they are mentioned and flag unclear owners. | Check that sensitive comments are not copied into public task descriptions. |
| AI Fields | repeatable summary, classification, risk, priority | Design an AI Field for this list that summarizes each task's current risk in one sentence using status, comments, due date, priority, and blockers. | Test the field on real tasks before relying on it in dashboards. |
Copy this first
The all-purpose ClickUp Brain prompt
ClickUp prompts for tasks and project setup
Use these prompts when a brief, kickoff note, client email, or roadmap item needs to become organized work in ClickUp.
Prompt 1
Turn this project brief into a ClickUp task plan. Include phases, tasks, subtasks, suggested owners, dependencies, due-date logic, and Definition of Done for each major task.
Prompt 2
Read this client email and create the tasks needed to deliver the request. Separate confirmed requirements from assumptions and questions we still need to ask.
Prompt 3
Create a reusable project template for [project type]. Include statuses, required Custom Fields, task sections, checklists, and the recurring review cadence.
Prompt 4
Convert this SOP into ClickUp tasks. Each task should have an owner role, checklist, completion criteria, and one quality-control step.
Prompt 5
Review this task list and identify vague task names. Rewrite them as action-oriented tasks with clear deliverables and completion criteria.
Prompt 6
Create a launch checklist for [campaign/product]. Group tasks by strategy, creative, technical setup, QA, launch day, and post-launch reporting.
Prompt 7
Find missing dependencies in this list. For each dependency, explain what could be blocked and where the dependency should be linked.
Prompt 8
Create a risk register from these tasks. Include risk, likelihood, impact, owner, mitigation plan, and the task or Doc where the risk appears.
ClickUp Brain prompts for Docs and knowledge work
ClickUp Brain is strongest when you point it at the right location: a Doc, task, list, folder, space, or workspace context.
Prompt 1
Summarize this Doc for a busy executive. Include the decision needed, background, options, risks, recommendation, and next step.
Prompt 2
Turn this rough project note into a clean ClickUp Doc with headings, bullets, action items, owner placeholders, and a short summary at the top.
Prompt 3
Compare this project brief with the linked tasks. List anything in the brief that is missing from the execution plan.
Prompt 4
Create a one-page operating procedure from this task history and comments. Keep it practical and include handoff steps.
Prompt 5
Read the linked Docs and tasks for [project]. Create a glossary of project terms, acronyms, stakeholders, and recurring decisions.
Prompt 6
Draft a client-facing project recap from this internal Doc. Remove internal friction, keep factual progress, and state next steps clearly.
Prompt 7
Audit this Doc for unclear ownership, missing dates, unsupported claims, repeated sections, and decisions that need confirmation.
Prompt 8
Create a FAQ from this workspace knowledge base for a new team member joining [team/project].
Sprint planning and backlog prompts
For product and engineering teams, use ClickUp AI prompts to clean the backlog before planning, not to replace the team conversation.
Prompt 1
Review the backlog and group related tasks into epics or themes. Suggest epic names, describe the user value, and list tasks that do not fit.
Prompt 2
Identify duplicate, stale, or vague backlog items. Recommend merge, rewrite, keep, or close for each item with a short reason.
Prompt 3
Turn this feature spec into user stories with acceptance criteria, edge cases, dependencies, and test notes.
Prompt 4
Suggest sprint candidates based on priority, dependency order, and task readiness. Flag anything that is too vague to estimate.
Prompt 5
Create Definition of Ready and Definition of Done checklists for this team's sprint tasks.
Prompt 6
Write release notes from completed sprint tasks. Group by new features, improvements, bug fixes, and known limitations.
Prompt 7
Create standup talking points from tasks updated in the last 24 hours. Format by person: done, doing, blocked, needs help.
Prompt 8
Review this sprint for delivery risk. Look for overloaded owners, late dependencies, missing acceptance criteria, and unresolved blockers.
Status report and stakeholder update prompts
The best status prompts define the audience first. Leadership, clients, and delivery teams need different levels of detail.
Prompt 1
Create a weekly executive status report from this project. Include overall health, completed work, upcoming milestones, risks, decisions needed, and one-line owner summary.
Prompt 2
Write a client-friendly project update email using these tasks and comments. Keep it calm, factual, and focused on progress, risks, and next steps.
Prompt 3
Summarize all blockers in this project. For each blocker, include owner, affected milestone, last update, proposed next action, and escalation need.
Prompt 4
Create a dashboard narrative from these project metrics. Explain what changed, why it matters, and what the team should do next.
Prompt 5
Write a Slack-length update for [channel]. Include what shipped, what is in progress, what is blocked, and one ask from the team.
Prompt 6
Create a red/yellow/green health summary for each active workstream based on due dates, priority, comments, and blocked tasks.
Prompt 7
Turn this project history into a monthly retrospective. Include wins, misses, root causes, process changes, and owners for improvements.
Prompt 8
Create a decision log from this project. Include decision, date, owner, context, options considered, and follow-up task.
Automation and AI Field prompts
ClickUp Brain can help design repeatable summaries, classifications, and workflows. Treat its output as a system design draft before building automations.
Prompt 1
Review this list and propose 5 ClickUp automations. For each, include trigger, condition, action, owner, and risk if the automation fires incorrectly.
Prompt 2
Design AI Fields for this support list: urgency summary, customer sentiment, likely department, escalation risk, and suggested next step.
Prompt 3
Create an AI Field prompt that summarizes each task in one sentence using status, assignee, due date, latest comment, and blocker status.
Prompt 4
Review recurring manual updates in this workspace and suggest which should become automations, templates, or AI Fields.
Prompt 5
Create an intake form and routing workflow for [request type]. Include required fields, routing logic, default assignee, and follow-up tasks.
Prompt 6
Design a project health AI Field for leadership dashboards. Use due dates, priority, blocker comments, overdue subtasks, and latest activity.
Prompt 7
Suggest notification rules for this project so stakeholders are informed without creating alert fatigue.
Prompt 8
Audit these proposed automations for failure modes, duplicate task creation, wrong assignees, privacy risk, and unclear ownership.
What to check before assigning AI-created work
ClickUp AI prompt FAQs
What is the best prompt format for ClickUp Brain?
The best ClickUp Brain prompt names the source context, output type, audience, fields to include, and review criteria. For example: using tasks in this list and linked Docs, create a weekly executive status report with progress, risks, decisions needed, blockers, and next week's focus.
Can ClickUp Brain create tasks from a Doc?
Yes. ClickUp Brain can help turn Docs, notes, and workspace context into tasks or action items. You should still review owners, due dates, dependencies, privacy, and exact task wording before assigning work to a team.
What are ClickUp AI Fields?
AI Fields are Custom Fields that use AI to summarize, classify, or generate task-level information. Useful examples include task summaries, risk summaries, sentiment, next action, customer urgency, and project health. Test them on real tasks before using them in leadership dashboards.
How do I get better status reports from ClickUp AI?
Define the audience and source. A leadership report should highlight health, progress, risk, decisions, and next steps. A team report should include blockers, owner actions, and dependencies. Ask ClickUp Brain to use only the selected list, Doc, or project context so the report does not drift.
Can ClickUp Brain help with sprint planning?
Yes. It can summarize backlog items, group related work, draft acceptance criteria, identify vague tasks, and flag dependencies or blockers. It should not replace sprint planning judgement. Use it to prepare the backlog before the team estimates and commits.
Can I use ClickUp AI prompts for client projects?
Yes, but client projects need careful review. Use prompts to draft updates, plans, tasks, and recaps. Before sending anything externally, remove internal comments, verify dates and commitments, and make sure sensitive client or team information is not exposed.
What is the main mistake people make with ClickUp AI prompts?
The main mistake is asking a broad question without source context. Ask ClickUp Brain to use a specific task, list, Doc, folder, space, or workspace location. Then tell it the exact artifact you want: task plan, status report, sprint review, risk register, SOP, or decision log.
Can ClickUp Brain summarize meetings?
ClickUp supports AI-assisted summaries across workspace content, and ClickUp docs describe AI functionality around comments, Docs, Chat, and Voice Clips. For meeting workflows, ask for decisions, action items, owners, open questions, and follow-up tasks, then verify every owner before assigning work.
Should I let ClickUp AI assign owners automatically?
Use AI owner suggestions as a draft only. It can infer likely owners from context, but actual ownership depends on capacity, priority, authority, and team agreements. Confirm assignments manually before work appears on someone's task list.
Does ClickUp Brain replace project managers?
No. It can reduce administrative work such as summarizing tasks, drafting updates, cleaning backlog items, and creating task plans. Project managers are still needed for judgement, tradeoffs, stakeholder alignment, prioritization, escalation, and delivery accountability.