10 prompts for Project Managers
Resource Allocation Plan
Create a resource allocation plan for [Project Name] with a team of [X] members. Project details: - Start date: [date] - End date: [date] - Budget for resources: [$amount] - Team members: [list names and roles] Resource plan should include: 1. TEAM ROSTER - Name, role, skills, availability % - Internal vs external resources - Cost per resource 2. RESOURCE REQUIREMENTS BY PHASE - Phase 1 [name]: Resources needed, hours, dates - Phase 2 [name]: Resources needed, hours, dates - Phase 3 [name]: Resources needed, hours, dates 3. RESOURCE CALENDAR - Weekly allocation by team member - Peak demand periods - Vacation and availability conflicts 4. RESOURCE RISKS - Key person dependencies - Skill gaps - Mitigation strategies 5. BUDGET BREAKDOWN - Cost per resource per phase - Total resource cost - Contingency reserve Format as professional resource plan with tables
Lessons Learned Document
Create a lessons learned document for [Project Name] completed on [date]. Project summary: - Project name: [name] - Duration: [X months] - Budget: [$amount actual vs $amount planned] - Team size: [X] - Overall outcome: [Successful/Partially successful/Unsuccessful] Lessons learned sections: 1. WHAT WENT WELL - Planning and preparation - Team collaboration - Technical execution - Stakeholder management - Risk management 2. WHAT COULD BE IMPROVED - Planning gaps - Communication issues - Resource challenges - Technical obstacles - Process inefficiencies 3. SPECIFIC LESSONS BY CATEGORY - Schedule management - Budget control - Risk management - Quality assurance - Team management 4. RECOMMENDATIONS FOR FUTURE PROJECTS - Process improvements - Tool recommendations - Template updates - Training needs 5. ACTION ITEMS - Who, what, when for each improvement Format as official project closure document
Change Request Document
Write a formal change request document for [Project Name]. Change details: - Change request ID: [CR-XXX] - Date submitted: [date] - Submitted by: [name/role] - Priority: [High/Medium/Low] - Change type: [Scope/Schedule/Budget/Resource] Change description: - Current situation: [describe what exists now] - Proposed change: [describe what is requested] - Reason for change: [business justification] Impact analysis: - Scope impact: [describe] - Schedule impact: [+/- X days/weeks] - Budget impact: [+/- $amount] - Resource impact: [describe] - Quality impact: [describe] - Risk impact: [describe] Options analysis: - Option 1: Approve as requested - Option 2: Approve with modifications - Option 3: Reject Recommendation: [option and rationale] Approval section: - Project Manager: [signature/date] - Project Sponsor: [signature/date] - Client: [signature/date]
Team Performance Review
Write a team performance review for [Team Name] for [quarter/year]. Team details: - Team name: [name] - Team size: [X members] - Project: [project name] - Review period: [date range] - Overall team rating: [Exceeds/Meets/Below Expectations] Review should cover: 1. TEAM ACHIEVEMENTS - Goals accomplished this period - Key milestones delivered - Quality of deliverables 2. TEAM METRICS - Velocity or productivity: [metrics] - On time delivery rate: [%] - Budget adherence: [%] - Quality metrics: [defect rate/rework] 3. TEAM STRENGTHS - Collaboration and communication - Technical excellence - Problem solving 4. AREAS FOR IMPROVEMENT - Specific challenges faced - Skills gaps identified - Process improvements needed 5. GOALS FOR NEXT PERIOD - Team objectives - Development plans - Process improvements Tone: Constructive and motivating Length: 400-500 words
Project Kickoff Meeting Agenda
Create a comprehensive project kickoff meeting agenda for [Project Name]. Meeting details: - Project: [name] - Date: [date] - Duration: [X hours] - Location/Platform: [in person/Zoom/Teams] - Attendees: [list roles] Kickoff agenda: 1. WELCOME AND INTRODUCTIONS (10 min) - Project sponsor welcome - Team introductions 2. PROJECT OVERVIEW (20 min) - Business case and objectives - Project scope - Key deliverables - Success criteria 3. TIMELINE AND MILESTONES (15 min) - Project schedule overview - Key milestones - Dependencies 4. ROLES AND RESPONSIBILITIES (15 min) - Team structure - RACI matrix overview - Decision making process 5. COMMUNICATION PLAN (10 min) - Meeting cadence - Reporting structure - Tools and platforms 6. RISKS AND CONCERNS (15 min) - Known risks - Open discussion 7. NEXT STEPS AND Q&A (15 min) - Immediate action items - Questions Include presenter notes for each section
Sprint Planning Meeting Agenda
Create a sprint planning meeting agenda for [Team Name] for Sprint [X] starting [date]. Sprint details: - Sprint number: [X] - Duration: [1/2] weeks - Team size: [X developers] - Velocity: [X story points] - Sprint goal: [describe goal] Meeting agenda (2-4 hours): 1. SPRINT REVIEW RECAP (15 min) - Previous sprint achievements - Incomplete items - Lessons learned 2. PRODUCT BACKLOG REVIEW (30 min) - Priority items from product owner - Backlog refinement - Story point estimates 3. SPRINT GOAL SETTING (15 min) - Define sprint goal - Team alignment 4. SPRINT BACKLOG SELECTION (60 min) - Select user stories - Confirm capacity - Task breakdown 5. COMMITMENT AND QUESTIONS (15 min) - Team commitment - Blockers identified - Action items Include facilitation tips for each section
Stakeholder Communication Plan
Create a stakeholder communication plan for [Project Name]. Project details: - Project name: [name] - Duration: [X months] - Team size: [X] - Key stakeholders: [list] For each stakeholder group provide: STAKEHOLDER ANALYSIS - Name/Group: [name] - Role: [sponsor/team/client/executive] - Interest level: [High/Medium/Low] - Influence level: [High/Medium/Low] - Communication needs: [what they need to know] COMMUNICATION MATRIX - Communication type: [report/meeting/email/dashboard] - Frequency: [daily/weekly/monthly] - Format: [written/verbal/presentation] - Owner: [who sends it] - Key messages: [what to include] COMMUNICATION TEMPLATES - Weekly status email template - Executive dashboard summary - Issue escalation process - Meeting agenda template Length: Comprehensive communication plan document
Risk Register Creator
Create a comprehensive risk register for [Project Name]. Project context: - Project type: [IT/Construction/Marketing/Other] - Duration: [X months] - Budget: [$amount] - Team size: [X people] - Key dependencies: [list] For each risk provide: - Risk ID - Risk description - Category: [Technical/Financial/Resource/External/Schedule] - Probability: [Low/Medium/High] - Impact: [Low/Medium/High] - Risk score: [1-9] - Risk owner - Mitigation strategy - Contingency plan - Status: [Open/Monitoring/Closed] Identify and document at least 10 risks covering: 1. Resource and staffing risks 2. Technical and technology risks 3. Budget and financial risks 4. Timeline and schedule risks 5. Stakeholder and communication risks 6. External and vendor risks 7. Scope creep risks 8. Quality risks Format as professional risk register table
Project Status Report Writer
Write a weekly project status report for [Project Name] for the week ending [date]. Project details: - Project name: [name] - Project manager: [name] - Overall status: [Green/Yellow/Red] - % Complete: [X]% - Budget status: [On track/Over/Under] - Schedule status: [On track/Ahead/Behind] Report sections: 1. Executive summary (3-4 sentences) 2. Accomplishments this week - [List completed tasks] 3. Planned for next week - [List upcoming tasks] 4. Issues and blockers - Issue: [describe] - Impact: [describe] - Action: [describe] 5. Risks update 6. Budget summary - Budgeted: [$amount] - Actual to date: [$amount] - Remaining: [$amount] 7. Key decisions needed 8. Stakeholder actions required Tone: Concise and professional Length: 300-400 words
Project Charter Writer
Write a comprehensive project charter for [Project Name] at [Company Name]. Project details: - Project name: [name] - Project manager: [name] - Sponsor: [name] - Start date: [date] - End date: [date] - Budget: [$amount] - Department: [department] Charter must include: 1. Project purpose and justification 2. Project objectives (SMART goals) 3. Scope — what is included and excluded 4. Key deliverables list 5. Milestones and timeline 6. Budget summary 7. Team members and roles 8. Key stakeholders 9. Assumptions and constraints 10. Risks and mitigation overview 11. Success criteria 12. Approval signatures section Tone: Professional and formal Format: Official project document Length: 500-700 words
Frequently Asked Questions
Which AI tool works best for project management documentation?
Claude produces more formally structured project documents that follow standard PM frameworks like PMBOK and Agile conventions. ChatGPT tends to produce more conversational stakeholder communications. For formal documents like project charters and risk registers, use Claude. For team updates and meeting agendas, either works well.
Can AI write project status reports?
Yes — the project status report prompt is one of the most time-saving in this collection. PMs who test it report cutting status report writing time from 45 minutes to under 10 minutes. The key is having your actual project data ready to fill in the brackets — the more specific your numbers and milestone details, the better the output.
Are these prompts suitable for Agile and Waterfall projects?
Yes — the collection covers both methodologies. The sprint planning agenda and lessons learned prompts are designed for Agile teams. The project charter, risk register, and stakeholder communication plan follow traditional Waterfall and PMBOK conventions. Specify your methodology in the brackets for best results.
Can I use these prompts for PMP exam preparation?
These prompts are based on standard PMBOK terminology and frameworks which align with PMP exam content. Using them to generate sample project documents and practice scenarios can be a useful study tool, though they are primarily designed for working project managers, not exam prep.
How do I get better results from project management prompts?
Always specify the project phase, stakeholder audience, and industry context in the brackets. A status report written for a technical development team reads very differently from one written for a C-suite executive audience. These prompts account for that distinction — use it by being specific about who will read the output.
Are these prompts suitable for IT and software project managers?
Yes — the sprint planning, risk register, and change request prompts are especially relevant for IT and software projects. The stakeholder communication plan and lessons learned document work well across all industries including IT, construction, marketing, and operations.