40 AI Prompts for Project Managers: Plans, Standups, and Stakeholder Updates (2026)

You are a senior agile project manager with experience running Scrum teams in [INDUSTRY — e.g., fintech].

Create a sprint planning document for Sprint [NUMBER] of [PROJECT NAME].

Team capacity: [NUMBER] developers, [NUMBER] designers, [DAYS] working days
Sprint goal: [HIGH-LEVEL OBJECTIVE]
Carry-over items: [LIST ANY INCOMPLETE STORIES]

Include:
- Sprint goal statement (1-2 sentences)
- User stories prioritized by business value (format: As a [user], I want [action], so that [benefit])
- Story point estimates for each item
- Acceptance criteria for each story
- Dependencies and blockers
- Sprint capacity allocation (development, testing, meetings)
- Risk items and mitigation

Total committed story points should not exceed [VELOCITY — e.g., 34 points based on last 3 sprints].

Draft a project charter for [PROJECT NAME]: [ONE-SENTENCE DESCRIPTION].

Business sponsor: [NAME/ROLE]
Target launch: [DATE]
Budget: [AMOUNT or TBD]

Include:
- Project purpose and justification (tied to business objectives)
- Scope statement (in-scope and explicitly out-of-scope)
- Key deliverables with target dates
- Success criteria (measurable)
- Stakeholder list with roles and responsibilities
- High-level milestones
- Key assumptions and constraints
- Initial risk assessment (top 5 risks)
- Approval signatures section

Keep it to 2-3 pages. This needs to be concise enough that executives actually read it.

Create a detailed work breakdown structure (WBS) for [PROJECT — e.g., migrating a monolithic application to microservices].

Project duration: [TIMELINE]
Team size: [NUMBER]

Provide 3 levels of decomposition:
- Level 1: Major phases/workstreams
- Level 2: Deliverables within each phase
- Level 3: Work packages with estimated effort (in person-days)

Include:
- Dependencies between work packages
- Critical path identification
- Milestone markers
- Resource type needed for each work package (dev, design, QA, DevOps)

Format as an indented list with effort estimates.

Create a resource allocation plan for [NUMBER] projects running simultaneously over [TIMEFRAME].

Projects:
1. [PROJECT 1]: [BRIEF DESCRIPTION], priority: [HIGH/MEDIUM/LOW]
2. [PROJECT 2]: [BRIEF DESCRIPTION], priority: [HIGH/MEDIUM/LOW]
3. [PROJECT 3]: [BRIEF DESCRIPTION], priority: [HIGH/MEDIUM/LOW]

Available team: [LIST ROLES AND HEADCOUNT]

Provide:
- Allocation percentages per person per project per [WEEK/MONTH]
- Conflict identification (where the same person is needed by multiple projects)
- Recommendations for resolving over-allocation
- Critical hiring or contractor needs
- Bench time / slack for unplanned work (aim for 15-20%)

Present as a table with narrative explanation of key tradeoffs.

Help me prioritize this feature backlog for [PRODUCT/PROJECT] using a RICE scoring framework.

Features to evaluate:
1. [FEATURE 1]
2. [FEATURE 2]
3. [FEATURE 3]
4. [FEATURE 4]
5. [FEATURE 5]

For each feature, estimate:
- Reach: How many users/customers affected per [QUARTER]
- Impact: [MINIMAL/LOW/MEDIUM/HIGH/MASSIVE] with scoring guide
- Confidence: [LOW/MEDIUM/HIGH] percentage
- Effort: Person-[WEEKS/MONTHS] required

Calculate RICE score, rank by score, and provide a recommended prioritization with rationale for the top 3.

Write a weekly executive status update email for [PROJECT NAME].

Recipients: [VP/C-SUITE TITLES]
Reporting period: [DATE RANGE]

Status: [GREEN/YELLOW/RED]
Overall progress: [X]% complete, [AHEAD/ON TRACK/BEHIND] schedule

Include:
- 3-line executive summary (what matters this week)
- Key accomplishments (3-5 bullet points)
- Upcoming milestones (next 2 weeks)
- Risks and issues (with severity and mitigation)
- Decisions needed from leadership (with deadline)
- Budget status (spent vs. planned)

Tone: Concise, data-driven, no filler. Executives should get the full picture in 60 seconds.

Create a stakeholder analysis matrix for [PROJECT/INITIATIVE].

Known stakeholders:
[LIST NAMES, TITLES, AND DEPARTMENTS]

For each stakeholder, assess:
- Interest level (LOW/MEDIUM/HIGH)
- Influence level (LOW/MEDIUM/HIGH)
- Current attitude (CHAMPION/SUPPORTER/NEUTRAL/RESISTANT/BLOCKER)
- Key concerns or motivations
- Recommended engagement strategy
- Communication frequency and channel

Present as a power/interest grid with quadrant strategies:
- High power, high interest: Manage closely
- High power, low interest: Keep satisfied
- Low power, high interest: Keep informed
- Low power, low interest: Monitor

Draft a formal change request document for [CHANGE DESCRIPTION].

Project: [PROJECT NAME]
Requested by: [NAME/ROLE]
Priority: [CRITICAL/HIGH/MEDIUM/LOW]

Include:
- Change description and justification
- Impact analysis:
  - Scope impact (new deliverables or modified deliverables)
  - Schedule impact (days added/removed)
  - Budget impact (additional cost)
  - Resource impact
  - Risk impact
- Alternatives considered
- Recommendation (approve/approve with modifications/reject)
- Approval workflow and sign-off lines

Be specific about tradeoffs — what gets delayed or dropped if this is approved.

Create a 90-minute project kickoff meeting agenda for [PROJECT NAME] with [TEAM SIZE] attendees from [DEPARTMENTS].

Include:
1. Welcome and introductions (5 min)
2. Project context and business case (10 min)
3. Scope, objectives, and success criteria (15 min)
4. Team roles and responsibilities — RACI overview (10 min)
5. Timeline and key milestones (10 min)
6. Ways of working (tools, meetings, communication channels) (10 min)
7. Risk discussion (10 min)
8. Q&A (10 min)
9. Immediate next steps and action items (10 min)

For each section, include:
- Presenter
- Key talking points
- Any pre-read materials to distribute beforehand

Add a follow-up email template with meeting notes and action items.

Write a project closure report for [PROJECT NAME].

Duration: [START DATE] to [END DATE]
Budget: [PLANNED] vs [ACTUAL]
Team: [SIZE AND KEY MEMBERS]

Include:
- Executive summary of outcomes
- Objectives vs. results (scorecard format)
- Key deliverables and acceptance status
- Budget summary with variance explanation
- Timeline analysis (planned vs. actual milestones)
- Key risks that materialized and how they were handled
- Lessons learned (what went well, what didn't, what to do differently)
- Outstanding items and transition plan
- Team recognition and acknowledgments

This document should be reusable as a reference for similar future projects.

Design a sprint retrospective for a team that has been [SITUATION — e.g., dealing with scope creep and missed commitments for 3 sprints].

Team size: [NUMBER]
Format: [IN-PERSON/REMOTE]
Duration: 60 minutes

Provide:
- Ice-breaker activity (5 min) — related to the theme
- Retrospective format (choose something beyond basic Start/Stop/Continue)
- Facilitation script with time boxes for each segment
- Specific prompting questions to surface the real issues
- Action item template (owner, deadline, success criteria)
- Follow-up plan for tracking action items

The team is [MORALE DESCRIPTION — e.g., frustrated but committed]. Adjust the tone accordingly.

Refine these rough feature ideas into well-structured user stories with acceptance criteria:

Raw ideas:
1. [ROUGH IDEA 1]
2. [ROUGH IDEA 2]
3. [ROUGH IDEA 3]

For each, provide:
- User story: "As a [persona], I want [action], so that [benefit]"
- Acceptance criteria (Given/When/Then format, 3-5 per story)
- Edge cases to consider
- Technical notes or dependencies
- Suggested story point estimate (using Fibonacci: 1, 2, 3, 5, 8, 13)
- Definition of done checklist

Create a risk register for [PROJECT NAME] in [INDUSTRY].

Identify 10-15 risks across categories:
- Technical risks
- Resource risks
- Schedule risks
- External/vendor risks
- Organizational/political risks

For each risk:
- Description
- Probability (1-5)
- Impact (1-5)
- Risk score (P × I)
- Risk owner
- Mitigation strategy
- Contingency plan
- Status (open/mitigating/closed)

Sort by risk score descending. Include a risk heat map summary.

Draft an issue escalation brief for [ISSUE — e.g., critical vendor missing delivery deadline by 3 weeks].

Format for: [AUDIENCE — e.g., VP of Engineering and Product]

Include:
- Issue summary (2 sentences max)
- Impact: What breaks if we don't act (specific deliverables, dates, revenue)
- Root cause analysis (what we know and don't know)
- Options (3 options with pros, cons, cost, and timeline for each)
- Recommendation with rationale
- Decision needed by: [DATE]
- Escalation: What happens if no decision is made

One page maximum. Lead with the ask.