1. Write a Clear Project Scope Document in Minutes
Scope documents set the foundation for every project. This prompt produces a clean, professional document in seconds — just fill in your project details.
Copy-paste prompt
You are a senior project manager. Write a project scope document for the following project: Project name: [PROJECT NAME] Client/stakeholder: [CLIENT NAME] Objective: [WHAT WE'RE BUILDING OR DOING] Key deliverables: [LIST 3-5 DELIVERABLES] Timeline: [START DATE] to [END DATE] Budget: [BUDGET OR "TBD"] Out of scope: [WHAT IS EXPLICITLY NOT INCLUDED] Format the document with these sections: Project Overview, Goals & Objectives, Deliverables, Timeline, Budget, Out of Scope, Success Criteria, Stakeholder Sign-Off. Use clear, professional language suitable for a client-facing document.
2. Write a Weekly Project Status Report (That People Actually Read)
Status reports are the most recurring PM writing task. This prompt keeps them scannable, consistent, and actually read — not buried in inboxes.
Copy-paste prompt
You are a project manager writing a weekly status report for [PROJECT NAME]. Here are this week's updates: Status: [GREEN / YELLOW / RED] Completed this week: [LIST 3-5 ITEMS] In progress: [LIST 2-4 ITEMS] Blocked or at risk: [LIST ANY BLOCKERS, or "None"] Key metrics: [RELEVANT NUMBERS — % complete, budget used, etc.] Next week's priorities: [LIST 3-4 ITEMS] Write a concise status report (under 250 words) that: - Opens with a 1-sentence overall summary - Uses bullet points for completed/in-progress/next steps - Flags blockers clearly without causing panic - Closes with a clear ask or next action if needed Tone: professional but direct. No corporate fluff.
3. Draft a Stakeholder Update Email for Any Situation
Stakeholder communication is where projects get made or broken. This prompt handles everything from milestone celebrations to delay notifications — just change the situation and tone. For broader outreach writing, the patterns in how to write cold email with AI are also useful when you need to get a stakeholder’s attention for the first time.
Copy-paste prompt
You are a project manager. Draft a stakeholder update email for the following situation: Project: [PROJECT NAME] Situation: [DESCRIBE WHAT HAPPENED — milestone hit, delay, scope change, budget issue, etc.] Key message: [WHAT DO YOU WANT STAKEHOLDERS TO KNOW OR DO?] Tone needed: [REASSURING / CELEBRATORY / URGENT / MATTER-OF-FACT] Next step or ask: [WHAT ACTION OR RESPONSE DO YOU NEED FROM THEM?] Write a professional email (150-200 words) with: - A subject line - A 1-sentence opener that states the purpose clearly - 2-3 sentences of context and key details - A clear next step or ask - A professional close Do not use jargon, hedge excessively, or bury the lead.
Nexus Vault
Need more than the free prompts?
Get 200 business prompts, instant download, and no subscription.
4. Turn Any Risk Into a Documented Risk Log Entry
Risk logs are often neglected until something goes wrong. This prompt makes it fast to document risks properly, so your log stays current without becoming a burden. If your team’s HR or people operations are growing alongside the project, the AI prompts for HR managers cover team communication and hiring tasks that run parallel to PM work.
Copy-paste prompt
You are a project manager. I need to document a project risk. Here are the details: Risk description: [DESCRIBE THE RISK] Project: [PROJECT NAME] Likelihood: [LOW / MEDIUM / HIGH] Impact if it occurs: [LOW / MEDIUM / HIGH] Affected areas: [TIMELINE / BUDGET / SCOPE / QUALITY / TEAM] Write a formal risk log entry with the following fields: - Risk ID: [assign a sequential number, e.g. RISK-004] - Risk Description: [clear, jargon-free description] - Likelihood: [rating + 1-sentence rationale] - Impact: [rating + 1-sentence description of consequences] - Risk Score: [Low/Medium/High/Critical based on likelihood × impact] - Mitigation Strategy: [2-3 specific, actionable steps to reduce likelihood or impact] - Contingency Plan: [what to do if the risk materializes] - Owner: [RISK OWNER NAME OR ROLE] - Review Date: [DATE]
5. Run a Project Retrospective That Actually Improves Things
Retrospectives only improve future projects if they’re documented. This prompt turns a team debrief into a structured report with actual action items — not just a meeting that everyone forgets.
Copy-paste prompt
You are a project manager running a post-project retrospective for [PROJECT NAME]. Here is a summary of the project: Duration: [START DATE] to [END DATE] Team size: [NUMBER] people Outcome: [DELIVERED ON TIME / LATE / OVER BUDGET / UNDER BUDGET / SCOPE CHANGES] Key wins: [LIST 2-4 THINGS THAT WENT WELL] Key challenges: [LIST 2-4 THINGS THAT WENT POORLY OR WERE DIFFICULT] Team feedback themes: [OPTIONAL: any recurring themes from team feedback] Generate a structured retrospective report with these sections: 1. Project Summary (2-3 sentences) 2. What Went Well (bullet list with 1-sentence commentary on each) 3. What Didn't Go Well (bullet list with honest, non-blame analysis) 4. Root Cause Analysis (pick the top 2 challenges and do a brief 5-why analysis) 5. Action Items for Next Project (3-5 specific, assignable improvements) 6. Lessons Learned (2-3 key takeaways the team should remember) Tone: honest, constructive, forward-looking. No whitewashing.