40 Claude Prompts for Project Managers
A PM's actual job is rarely the plan itself — it's the constant translation between stakeholders, timelines, and status updates. Here are 40 claude prompts for project managers built around that translation work.
Turn this messy meeting transcript into a structured action item list with owners and due dates: [paste transcript]
A project manager's actual job is rarely building the plan itself — plans get built once and revised occasionally. The daily work is translation: turning a messy stakeholder request into a scoped task, turning a status update into something an executive will actually read, turning a risk into language a team will take seriously without panicking. These 40 claude prompts for project managers are organized around that translation work.
Quick-Start (Copy These Right Now)
Turn this messy meeting transcript into a structured action item list
with owners and due dates: [paste transcript]What this does: this single prompt, run after nearly every meeting, probably saves more collective PM time across the industry than any other single use case on this list — meeting notes are messy by nature, and structuring them manually is exactly the kind of task worth offloading.
⚡ Pro tip: paste the full messy transcript, don't pre-clean it yourself. Claude is good at extracting structure from genuinely messy input; pre-cleaning it yourself just duplicates work Claude would have done anyway.
Planning and Scoping (Prompts 1-10)
1. Break this project description into a work breakdown structure
with phases and tasks: [describe project]
2. Draft a project charter covering goals, scope, and success
criteria for [project]
3. Turn this stakeholder wishlist into a prioritized scope, flagging
anything that looks out of scope for the stated timeline: [paste
wishlist]
4. Write a RACI matrix outline for [project] based on these team
roles: [list roles]
5. Draft a project timeline with milestones based on this scope and
a [X]-week deadline: [describe scope]
6. Turn this vague executive request into 3 clarifying questions to
ask before scoping: [paste request]
7. Draft a resource request explaining why [project] needs [specific
additional resource]
8. Write a project kickoff deck outline covering goals, timeline,
and roles
9. Draft a change request document for a scope addition to
[project], including impact on timeline and budget
10. Turn this list of dependencies into a sequenced order with
reasoning: [list dependencies]Status Updates and Reporting (Prompts 11-19)
11. Turn this raw progress data into a one-page status update for
executives: [paste data]
12. Write a status update explaining a timeline slip, factual and
without excessive apology
13. Draft a weekly team update summarizing progress across 3
workstreams: [describe workstreams]
14. Turn this project dashboard data into 3 key takeaways for a
steering committee: [paste data]
15. Write a "red status" escalation email flagging a project at risk,
with a proposed path forward
16. Draft a project close-out report summarizing outcomes against
original goals: [paste outcomes]
17. Turn these scattered Slack updates from team members into one
consolidated status report: [paste updates]
18. Write a stakeholder-facing summary of a technical issue, in
plain language without oversimplifying the impact
19. Draft a monthly portfolio summary across [X] active projects,
flagging the two that need the most attention⚠️ Common mistake: writing status updates that summarize activity instead of progress. "We had 12 meetings this week" isn't a status update. Ask Claude explicitly for a version framed around outcomes and remaining risk, not a log of what happened.
Risk and Issue Management (Prompts 20-26)
20. Turn this list of project concerns into a formal risk register
with likelihood and impact ratings: [list concerns]
21. Draft a mitigation plan for [specific risk]
22. Write an issue escalation email that's direct about the problem
without assigning blame
23. Turn this incident timeline into a post-mortem summary with
root cause and next steps: [paste timeline]
24. Draft a risk assessment for adding [new scope/vendor/dependency]
mid-project
25. Write a contingency plan outline for [specific risk scenario]
26. Turn this stakeholder complaint into a structured issue report
for the team: [paste complaint]⚡ Pro tip: when drafting a risk register from a list of vague concerns, ask Claude to flag which risks are missing likelihood or impact information rather than guessing at ratings — a risk register with invented confidence levels is worse than one with honest gaps.
Stakeholder and Team Communication (Prompts 27-35)
27. Draft a message setting expectations with a stakeholder who keeps
requesting scope additions mid-sprint
28. Write a project update tailored for a non-technical executive
audience, translating technical progress into business terms:
[paste technical update]
29. Draft a message pushing back on an unrealistic deadline, with
a proposed alternative
30. Write a recognition message for a team member's work on
[specific contribution]
31. Draft a difficult conversation script for addressing a team
member consistently missing deadlines
32. Turn this conflicting stakeholder feedback into a summary
highlighting where the actual disagreement is: [paste feedback]
33. Write a message explaining a resourcing decision that some team
members won't be happy about
34. Draft an agenda for a stakeholder alignment meeting on
[contentious topic]
35. Write a project retrospective facilitation guide with 5
discussion questionsDocumentation and Process (Prompts 36-40)
36. Turn this ad-hoc process into a documented, repeatable checklist:
[describe process]
37. Draft a project handoff document summarizing status, context,
and open items for an incoming PM
38. Write a template for project kickoff briefs I can reuse across
future projects
39. Turn these lessons learned notes into a one-page playbook for
the next similar project: [paste notes]
40. Draft a standard operating procedure for [recurring process]
based on how the team currently does it: [describe current
process]Pro-Level Variations
For PMs managing a portfolio of projects rather than one at a time, prompt 19 (the monthly portfolio summary) is worth running with a consistent structure every month, so trend data accumulates over time instead of each summary starting from scratch. A program manager at a healthcare software company built exactly this rhythm and found that flagging "the two that need the most attention" every month, rather than reviewing all projects equally, cut her steering committee meeting time nearly in half.
Troubleshooting Common Issues
If status updates keep coming back too long despite asking for "one page," that's usually a data problem, not a prompting problem — paste in more focused source data rather than everything you have, since Claude will try to use whatever detail you provide, and dense raw input produces dense output even when the format request is for brevity.
If risk register outputs feel generic, that's a sign the input concerns were too vague. "Timeline risk" isn't specific enough for a useful risk register entry; "vendor X's API integration has slipped twice already and a third slip pushes launch past the contractual deadline" gives Claude something concrete to actually assess.
Your Turn
Start with the meeting-notes prompt at the top of this list if you haven't already — it's the single highest-frequency, lowest-effort win on here. Then pick two or three more from whichever section matches your current biggest time sink, rather than trying to adopt all 40 in one week.
Once a handful of these become part of your regular PM rhythm, save your customized versions — with your actual project structure, stakeholder names, and reporting format baked in — in PromptABCD, so next sprint's status update starts from a template that already fits your team instead of a generic bracketed prompt.
Continue Reading
Save the prompts from this post
PromptABCD is a free prompt manager. Paste, organize, and reuse your best AI prompts — no more hunting through chat history.