The best prompts for project managers give the model a role, the real project facts, and a fixed output format. That is the difference between a vague "help me plan this project" and a prompt that returns a usable status report, risk register or sprint plan in one pass. Below are 30 prompts for ChatGPT and Claude, grouped by the six jobs a PM actually does: planning and scoping, scheduling and estimation, risk and issues, stakeholder communication, team ceremonies, and reporting and closure. Every prompt uses [brackets] for the fields you fill in. None of them repeat the 10 prompts on our project manager landing page, so treat the two sets as one library of 40.
AI skill for program managers
Cressida - Program Manager AI Skill
A persistent program manager persona that runs status reports, RAID logs, dependency maps and steering updates without you re-typing the prompt every time.
$29
Get the skill →
How to use these prompts
Three habits make every prompt below work better. First, paste real material: the actual ticket list, the actual meeting transcript, the actual budget line. The model cannot invent your project and should not try. Second, keep the output format instruction. Tables, numbered lists and word limits are what make the result paste-ready. Third, if you run the same prompt weekly, stop pasting it and save it as a skill or custom GPT. That is what the AI project manager collection is for, and our guide on how to use AI agents for project management explains the difference between a prompt and an agent in more depth.
Planning and scoping (prompts 1 to 5)
Prompt 1: Project brief from a messy kickoff
Act as a senior project manager. Here are my raw notes from the kickoff meeting: [paste notes]. Turn them into a one-page project brief with these sections: objective (one sentence), business reason, in scope, out of scope, key stakeholders with roles, constraints (budget, dates, people), assumptions, and open questions I must answer before planning. Flag anything in the notes that contradicts itself.
Prompt 2: Requirements gap check
Here is the requirements list for [project name]: [paste requirements]. Review it as a project manager, not an engineer. For each requirement tell me whether it is testable, whether it has an owner, and whether it depends on another requirement. Then list the requirements that are missing for a project of this type: [type, e.g. internal CRM migration]. Output as a table with columns: ID, requirement, testable (yes/no), owner, dependency, comment.
Prompt 3: Success metrics and definition of done
The project is [one-line description]. The sponsor wants [stated goal]. Propose 3 to 5 measurable success metrics with a baseline, a target and a measurement method for each. Then write a definition of done for the whole project in no more than 8 bullet points that a non-technical sponsor could sign.
Prompt 4: Build, buy or partner options
We need [capability]. Constraints: budget [amount], deadline [date], team of [number] with skills in [skills]. Lay out three delivery options (build in-house, buy a tool, use a partner) in a table with columns: option, time to value, cost range in general terms, main risk, what we give up. Finish with a recommendation and the two questions I should ask before committing.
Prompt 5: Phased roadmap
Split [project name] into 3 or 4 phases. For each phase give: name, goal, main deliverables, exit criteria, and the earliest point the business gets value. Total duration must fit within [number] months. Explain in two sentences why this order and not another.
Scheduling and estimation (prompts 6 to 10)
Prompt 6: Three-point estimate
For each task below give an optimistic, most likely and pessimistic estimate in days, then the expected value using (O + 4M + P) / 6. Tasks: [paste task list]. Assumptions about the team: [size, seniority, other commitments]. Output a table and add a final row with the total. State the two tasks with the widest spread and why.
Prompt 7: Dependency map and critical path
Here are the tasks with durations and predecessors: [paste, format: task, days, depends on]. Identify the critical path, the total project duration, and every task with float of 2 days or more. Then tell me which single task, if it slips by 3 days, hurts the end date most. Show the result as a table plus a plain-text list of the critical path in order.
Prompt 8: Capacity plan for the next quarter
Team: [names, roles, available days per week, planned leave]. Committed work: [list with estimates]. Build a capacity table by person and by month for [quarter]. Show planned load as a percentage of available days, mark anyone above 85 percent, and suggest what to move or drop to bring everyone under that line.
Prompt 9: Milestone schedule from a deadline
The hard deadline is [date]. Today is [date]. Deliverables: [list]. Work backwards and propose a milestone schedule with dates, including a review buffer of [number] days before the deadline and a code or content freeze. Flag any milestone that lands on or next to a public holiday in [country].
Prompt 10: Sprint plan from a backlog
Sprint length: [days]. Team velocity over the last three sprints: [numbers]. Sprint goal: [goal]. Backlog with story points and priority: [paste]. Propose the sprint contents so the total stays within 90 percent of average velocity, list what is deliberately left out, and write the sprint goal in one sentence the team can put on the board.
Risk and issues (prompts 11 to 15)
Prompt 11: Risk register from scratch
Project: [description]. Phase: [phase]. Known concerns: [list]. Build a risk register with columns: ID, risk (cause, event, effect in one sentence), category (scope, schedule, cost, people, technical, external), probability (1 to 5), impact (1 to 5), score, owner, response strategy (avoid, reduce, transfer, accept), next action, review date. Include at least 10 risks, and at least 3 I have not mentioned that are typical for this kind of project.
Prompt 12: Pre-mortem
Imagine it is [end date] and [project name] has failed badly. Write the post-mortem as if it already happened: the top 5 reasons it failed, ranked by likelihood, each with the early warning sign we ignored. Then convert each reason into a preventive action I can start this week, with an owner.
Prompt 13: Issue triage
Here is the open issue list: [paste with dates and descriptions]. Classify each issue by severity (blocker, major, minor), by whether it needs a decision or just work, and by who should own it. Output a table sorted by severity, then a short "decisions needed this week" list I can bring to the sponsor.
Prompt 14: Assumption log
Read this project plan: [paste]. Extract every assumption it relies on, stated or implied. For each, rate how confident we can be (high, medium, low), what happens if it is wrong, and how we could validate it cheaply in under a week. Output as a table.
Prompt 15: Vendor dependency risk
We depend on [vendor or team] for [deliverable] by [date]. Our contract or agreement says: [key terms]. List the ways this dependency could fail, what evidence I should ask for at each checkpoint, a fallback for each failure, and a one-paragraph escalation note I can send if they miss the first checkpoint.
Risk register template
If you only need the structure, this is the risk register template that prompt 11 fills in. Copy the headings into a sheet and the model can populate rows from any project description.
- ID and date raised
- Risk statement in cause, event, effect form
- Category: scope, schedule, cost, people, technical, external
- Probability (1 to 5) and impact (1 to 5), multiplied into a score
- Owner
- Response strategy: avoid, reduce, transfer, accept
- Next action and due date
- Trigger or early warning sign
- Status: open, monitoring, closed, became an issue
- Review date
Stakeholders and communication (prompts 16 to 20)
Prompt 16: Stakeholder map
Stakeholders for [project name]: [names, roles, what they care about, how much they can block or help]. Place each on a power versus interest grid, then give me a communication plan per quadrant: channel, frequency, what they need to hear, what they must never be surprised by. Output as two tables.
Prompt 17: Bad news, delivered well
I need to tell [stakeholder, role] that [the problem: budget overrun, missed date, dropped feature]. Cause: [cause]. Options we have: [options]. Write a message of no more than 200 words that states the problem in the first sentence, gives the cause without blaming anyone, presents the options with your recommendation, and asks for one specific decision by [date]. Tone: calm, direct, no apologies longer than one clause.
Prompt 18: Steering committee pre-read
Turn these notes into a two-page steering committee pre-read: [paste status, risks, decisions needed]. Structure: headline in one sentence, progress against plan, top 3 risks with our response, decisions required today with the recommended option, and what happens if no decision is made. Write for executives who will read it on a phone in four minutes.
Prompt 19: Pushing back on a request
[Stakeholder] has asked for [request] by [date]. Adding it would mean [impact on scope, dates or cost]. Write a reply that acknowledges the value of the request, explains the trade-off in concrete terms, and offers two alternatives: a smaller version now, or the full version in [later phase]. Keep it under 150 words and end with a question.
Prompt 20: Decision record
We decided [decision] on [date]. Context: [paste discussion or notes]. Write a decision record with: decision, who decided, options considered with pros and cons, why this option won, consequences we accept, and the date we will revisit it. Keep it under 300 words so it fits on one wiki page.
Team and ceremonies (prompts 21 to 25)
Prompt 21: Stand-up summary from chat
Here is today's stand-up thread or transcript: [paste]. Summarise it as: done since yesterday, planned today, blockers with owner, and anything that sounds like a risk nobody named. Maximum 12 lines. Do not include pleasantries or people who only said "no update".
Prompt 22: Retro themes from raw feedback
Here are the anonymous retro cards from the team: [paste]. Group them into themes, count how many cards support each theme, and for the top 3 themes propose one experiment we can run next sprint with a clear way to tell if it worked. Do not soften the criticism; keep the team's words where they are specific.
Prompt 23: Onboarding plan for a new team member
A new [role] joins [project name] on [date]. The project is at [phase]. Write a two-week onboarding plan: what to read on day one, who to meet and why, the first small task they can ship in week one, and the questions I should ask them at the end of week two to check they are set up to succeed.
Prompt 24: RACI matrix
Work packages: [list]. People and roles: [list]. Build a RACI matrix (Responsible, Accountable, Consulted, Informed). Every row must have exactly one A. Then point out any person who is Accountable for more than [number] packages, and any package where the Responsible person is not on the team full time.
Prompt 25: Working agreement for a mixed team
The team is [number] people across [locations and time zones], mixing [employees, contractors, vendor staff]. Draft a one-page working agreement covering: core overlap hours, response time expectations by channel, how we make and record decisions, how we handle disagreement, and what "done" means. Write it as short rules the team could vote on, not paragraphs.
Reporting and closure (prompts 26 to 30)
Prompt 26: Weekly status from tickets and chat
Here is this week's raw material: [paste closed tickets, open blockers, chat highlights, budget line]. Write a weekly status report with: overall RAG status and one sentence why, three things done, three things next, blockers with owner and date, budget spent versus plan, and one ask for leadership. Keep the whole thing under 250 words.
Prompt 27: Budget variance explanation
Planned spend to date: [amount]. Actual spend to date: [amount]. Line items: [paste]. Explain the variance in plain language for a finance reviewer: which lines drove it, whether each is timing or a real overrun, the forecast at completion, and two actions to bring it back toward plan. No jargon, no more than 200 words. This is not financial advice, just a variance narrative for my report.
Prompt 28: Go-live readiness checklist
We go live with [system or deliverable] on [date]. Environment: [details]. Build a readiness checklist grouped by: technical, data, people and training, support, communications, rollback. Each item gets an owner column and a status column. Add the five items teams most often forget for this kind of launch.
Prompt 29: Lessons learned report
Project: [name]. Planned versus actual: dates [planned/actual], budget [planned/actual], scope changes [list]. Retro notes: [paste]. Write a lessons learned report with: what went well and why, what did not and why, what we would do differently, and three recommendations for the next project of this type. Make each recommendation specific enough that someone could act on it without asking me.
Prompt 30: Handover to operations
The project [name] closes on [date] and [team or person] takes over running it. Write a handover document with: what was delivered, how to operate it day to day, known issues and workarounds, open items with owners, key contacts, where the documentation lives, and the support arrangement for the first [number] weeks. Use headings and short bullets.
Project plan template
Several prompts above produce parts of a project plan. If you want the whole thing, this is the project plan template structure to ask for, section by section:
- Summary: objective, sponsor, project manager, dates, budget
- Scope: in scope, out of scope, deliverables
- Success metrics and definition of done (prompt 3)
- Approach and phases (prompt 5)
- Work breakdown and estimates (prompt 6)
- Schedule, milestones and critical path (prompts 7 and 9)
- Team, roles and RACI (prompt 24)
- Stakeholders and communication plan (prompt 16)
- Risk register and assumption log (prompts 11 and 14)
- Budget and variance tracking (prompt 27)
- Quality, acceptance and go-live criteria (prompt 28)
- Change control and decision log (prompt 20)
Task to prompt to template to skill
A prompt is the fastest way to start. A generator skill is faster when the output is a formal document with a fixed structure. A persona skill is the right tool when you want the model to hold the whole project in memory across weeks. The table maps eight common PM tasks to all three.
| PM task |
Prompt in this article |
Document or template generator |
Persona skill |
| Define scope with a client or vendor |
Prompts 1, 2 |
AI Statement of Work Generator ($4.99) |
Diego - Agency Project Manager ($29) |
| Write product requirements |
Prompts 2, 3 |
AI PRD Generator ($29) |
Ulric - Technical Program Manager ($29) |
| Plan a sprint and run ceremonies |
Prompts 10, 21, 22 |
AI Meeting Notes Generator ($2.99) |
Perrin - Scrum Master ($29) |
| Build and maintain a risk register |
Prompts 11, 12, 14 |
Risk register template above |
Cressida - Program Manager ($29) |
| Report to executives |
Prompts 18, 26 |
AI Executive Summary Generator ($4.99) |
Cressida - Program Manager ($29) |
| Respond to a tender or client proposal |
Prompts 4, 19 |
AI RFP / Proposal Writer ($29) |
Diego - Agency Project Manager ($29) |
| Manage delivery across several teams |
Prompts 7, 8, 15 |
Project plan template above |
Torsten - Delivery Manager ($29) |
| Close the project and hand over |
Prompts 28, 29, 30 |
AI Meeting Notes Generator ($2.99) for the closure meeting |
Torsten - Delivery Manager ($29) |
Every skill is a one-time purchase: a .md skill file plus a README, and it works in Claude (including Claude Code), ChatGPT as a custom GPT, Gemini as a Gem, and Copilot. All come with a 30-day money-back guarantee, no questions asked. If your work is broader than project management, the ChatGPT prompts hub covers the other roles.
Frequently asked questions
Can ChatGPT or Claude replace an AI project manager tool?
Not on their own. A chat model drafts documents, analyses lists and summarises meetings very well, but it does not track tasks over time or connect to your ticketing system. Most PMs use the prompts here alongside Jira, Asana or a similar tool, and save recurring prompts as a skill so the persona and format stay consistent.
Which model is better for project management prompts, ChatGPT or Claude?
Both handle all 30 prompts. Claude tends to do well with long pasted material such as transcripts and full plans, and with strict formatting. ChatGPT is convenient if your team already lives in custom GPTs. Try the same prompt in both with real data and keep the one whose output needs fewer edits.
Do I need a project plan template if I use these prompts?
The prompts produce the parts; the template tells you what parts a complete plan needs. Use the project plan template section above as the checklist, then run the linked prompts to fill each section. That way nothing is missing when the sponsor asks for the plan.
How do I keep confidential project data safe when prompting?
Remove names, client identifiers and commercial figures you are not allowed to share, or use placeholders. Check your organisation's AI policy and whether your ChatGPT or Claude plan excludes your data from training. Enterprise and team plans usually do; consumer plans may not by default.
What is the difference between these prompts and the skills you sell?
The prompts are free and you can use them right now. A skill packages a persona, its methods and output formats into one file, so you stop re-pasting instructions and the model behaves the same way every week. Cressida, for example, runs status reports, RAID logs and steering updates from a single "here is this week's material" message.
The bottom line
Thirty prompts is more than most project managers need in a week, and that is the point: pick the five that match your recurring tasks, paste real data into them, and keep the output formats. When you find yourself running the same prompt every Monday, move it into a skill so the model remembers the project and you stop retyping the setup. Combined with the 10 more prompts on the landing page, you have a complete PM prompt library for planning, delivery and closure.
Prompt library for business and operations
Business & Operations Prompt Library
Ready-to-run prompts for planning, reporting, process documentation and stakeholder communication, organised by task so you find the right one in seconds.
$27
Get it now →
Browse all AI project manager skills at KissMySkills.
