AI Prompt Library
Project Manager Edition

I am a project manager working on [PROJECT NAME]. Today is [DAY/DATE]. Here is my current task list: [PASTE YOUR TASK LIST HERE] My project deadline is [DEADLINE]. The most critical milestone this week is [MILESTONE]. From this list, identify my 3 non-negotiable priorities for today. These should be the tasks that, if left undone, put the project at the greatest risk. For each priority, give me: 1. The task 2. Why it is the most important today 3. The single next action to move it forward Keep it brief. I need clarity, not a lecture.

I am managing [PROJECT NAME]. Today is [DATE]. Current project status: - We are in [WEEK NUMBER] of [TOTAL WEEKS] - Deliverables due this week: [LIST DELIVERABLES] - Known blockers: [LIST ANY CURRENT BLOCKERS] - Team members involved today: [LIST NAMES/ROLES] Based on this situation, identify the single most likely risk that could cause a delay or problem TODAY. Give me: 1. The risk in one sentence 2. Why it is the highest priority risk right now 3. One specific action I can take in the next 2 hours to mitigate it 4. Who I should flag this to

Write a brief project status update for [STAKEHOLDER NAME/ROLE]. Project: [PROJECT NAME] Today's date: [DATE] Overall status: [ON TRACK / AT RISK / DELAYED] Progress today: - Completed: [WHAT WAS DONE] - In progress: [WHAT IS BEING WORKED ON] - Blocked: [ANYTHING BLOCKED — or write "nothing blocked"] Risk to flag: [ONE RISK OR "no risks today"] Decision needed from them: [SPECIFIC DECISION — or write "no decision needed"] Write this as a professional 4-6 line update. Direct tone. No jargon. Should take them less than 30 seconds to read. End with: "No action needed from you today" unless a decision is required.

Help me close out today and prepare for tomorrow. Project: [PROJECT NAME] Date: [TODAY'S DATE] What I completed today: [LIST COMPLETED TASKS] What I did not finish: [LIST INCOMPLETE TASKS] New issues that came up: [ANY SURPRISES OR NEW PROBLEMS] Decisions made today: [LIST ANY DECISIONS] Based on this, give me: 1. A one-paragraph end-of-day summary I can log in my project notes 2. My recommended 3 priorities for tomorrow morning 3. Any risks I should flag before I log off today 4. Any stakeholders I should send a quick update to before tomorrow

Here are my notes from a project meeting. Please process them and give me a clean output. Meeting: [MEETING NAME] Date: [DATE] Attendees: [LIST NAMES AND ROLES] Raw notes: [PASTE YOUR RAW MEETING NOTES HERE] Please give me: 1. A 3-sentence meeting summary (what was discussed, what was decided, what is next) 2. Action items table with: Action / Owner / Deadline 3. Decisions made (list each one clearly) 4. Open questions that still need answers (and who owns answering them) 5. Risks or blockers mentioned Format clearly. This will be sent to all attendees.

Create a structured meeting agenda for the following: Meeting type: [KICKOFF / STATUS UPDATE / DECISION MEETING / RETROSPECTIVE] Project: [PROJECT NAME] Duration: [LENGTH IN MINUTES] Attendees: [LIST ROLES — not names] Goal of this meeting: [WHAT MUST BE DECIDED OR RESOLVED] Topics to cover: [LIST YOUR TOPICS] For each agenda item include: - Time allocation (in minutes) - The specific question to be answered or decision to be made - Who leads that section - What preparation attendees need to do beforehand End the agenda with a "Decisions Required" section listing what must be agreed before the meeting closes.

Write a professional post-meeting email to send to all attendees. Meeting: [MEETING NAME] Date: [DATE] Project: [PROJECT NAME] Decisions made: [LIST DECISIONS] Action items: [LIST: TASK — OWNER — DEADLINE] Next meeting: [DATE AND PURPOSE — or "TBC"] Anything requiring urgent response: [OR write "none"] Write this as a clear, professional email. Subject line included. Warm but direct tone. Should take under 60 seconds to read. Close with the next step everyone needs to take.

Analyse these meeting notes and identify hidden blockers, unresolved issues, and risks that were mentioned but not fully addressed. Meeting notes / transcript: [PASTE MEETING NOTES OR TRANSCRIPT] Look specifically for: 1. Things people said they were "waiting on" or "hoping for" 2. Vague commitments without clear owners or deadlines 3. Disagreements that were not fully resolved 4. Risks mentioned in passing but not logged 5. Dependencies that could delay other work For each item found, give me: - What was said (quote or paraphrase) - Why it is a potential blocker - Recommended next action - Who should own it

Write a professional weekly project status report. Project: [PROJECT NAME] Week ending: [DATE] Overall status: [GREEN — on track / AMBER — at risk / RED — off track] % complete: [PERCENTAGE] Accomplishments this week: [LIST WHAT WAS COMPLETED] Planned for next week: [LIST WHAT WILL BE DONE] Issues and risks: [LIST ANY PROBLEMS OR RISKS] Decisions needed: [LIST ANY DECISIONS REQUIRED FROM STAKEHOLDERS — or "none"] Budget status: [ON BUDGET / OVER BY X / UNDER BY X] Format as a professional status report. Include a one-paragraph executive summary at the top. Use clear headings. Should be readable in under 2 minutes.

Write an executive summary for a senior leader who wants the big picture — not the details. Project: [PROJECT NAME] Audience: [TITLE OF EXECUTIVE — e.g. CEO, VP Operations] Project status: [ON TRACK / AT RISK / DELAYED] Original deadline: [DATE] Current forecast: [DATE] Business context: [WHY THIS PROJECT MATTERS TO THE BUSINESS] Key facts: - Budget: [STATUS] - Timeline: [STATUS] - Key risk: [ONE SENTENCE] - Decision needed from leadership: [OR "none at this time"] Write 3 short paragraphs maximum. No jargon. No technical detail. Lead with business impact. Executives read the first sentence of each paragraph and skip the rest — make those sentences count.

Assess the health of my project and provide a RAG (Red/Amber/Green) status report. Project: [PROJECT NAME] Current week: [WEEK X of Y] Here is the current situation: - Schedule: [AHEAD / ON TRACK / BEHIND — by how much?] - Budget: [AMOUNT SPENT vs BUDGET] - Scope: [ANY CHANGES SINCE START?] - Team: [ANY RESOURCE ISSUES?] - Risks: [LIST ACTIVE RISKS] - Stakeholder satisfaction: [HIGH / MEDIUM / LOW] - Quality of deliverables: [ANY CONCERNS?] For each dimension, assign RED / AMBER / GREEN with a one-sentence justification. Then give me: 1. Overall project RAG status with reasoning 2. Top 3 actions to take this week to improve the health score 3. What I should communicate to my sponsor today

Write a milestone completion announcement to send to the project team and stakeholders. Project: [PROJECT NAME] Milestone completed: [MILESTONE NAME] Completion date: [DATE] Originally planned for: [ORIGINAL DATE] Who delivered it: [TEAM/PERSON RESPONSIBLE] Business impact: [WHAT THIS MILESTONE ENABLES OR UNLOCKS] Next milestone: [NAME AND DATE] Write this as a short, professional announcement. Acknowledge the team's work specifically. Communicate what this milestone means for the project. Create momentum toward the next milestone. Keep it under 150 words.

Evaluate the following change request and tell me if it is scope creep, a legitimate change, or a clarification of existing scope. Project name: [PROJECT NAME] Original scope statement: [PASTE YOUR ORIGINAL SCOPE OR KEY DELIVERABLES] Change requested: [DESCRIBE THE CHANGE REQUEST IN DETAIL] Requested by: [STAKEHOLDER NAME/ROLE] Reason given: [WHY THEY ARE REQUESTING IT] Assess: 1. Is this within, outside, or on the edge of the agreed scope? 2. What is the estimated impact on timeline? (rough estimate) 3. What is the estimated impact on budget? (rough estimate) 4. Should this be approved, declined, or deferred to next phase? 5. What is the one question I should ask before making a decision? Be direct. I need to respond to this stakeholder today.

Conduct a risk assessment for my project and identify risks I may not have considered. Project: [PROJECT NAME] Type of project: [e.g. software launch, office relocation, marketing campaign, process change] Team size: [NUMBER] people across [DEPARTMENTS] Timeline: [X weeks] Budget: [$AMOUNT] Key dependencies: [LIST EXTERNAL VENDORS, APPROVALS, OR TEAMS YOU DEPEND ON] Known risks already logged: [LIST ANY RISKS YOU ALREADY KNOW ABOUT] Identify the top 8 risks across these categories: - Schedule risks - Resource risks - Scope risks - Stakeholder risks - Technical or vendor risks - External / environmental risks For each risk provide: - Risk description - Likelihood (Low/Medium/High) - Impact if it occurs (Low/Medium/High) - Recommended mitigation action - Suggested owner

Create a stakeholder communication plan for my project. Project: [PROJECT NAME] Duration: [X weeks] Stakeholders: 1. [NAME/ROLE] — [Their main concern in one sentence] 2. [NAME/ROLE] — [Their main concern in one sentence] 3. [NAME/ROLE] — [Their main concern in one sentence] 4. [NAME/ROLE] — [Their main concern in one sentence] For each stakeholder, recommend: - What to communicate (level of detail — summary vs full detail) - How often to communicate (daily / weekly / milestone only) - Best channel (email / meeting / instant message / formal report) - What NOT to include (what would overwhelm or confuse them) - The one thing they most want to know at each update Format as a simple table I can use as a reference throughout the project.

Help me write a difficult message to a stakeholder about a project problem. Recipient: [NAME AND ROLE] Relationship: [DIRECT MANAGER / SPONSOR / CLIENT / PEER] The situation: [DESCRIBE WHAT HAPPENED — delay, budget issue, scope problem, missed deadline] What I have already done to address it: [ACTIONS TAKEN SO FAR] What I am proposing to do next: [YOUR RECOVERY PLAN] What I need from them: [DECISION / APPROVAL / INFORMATION / JUST AWARENESS] Write this message with: - Direct acknowledgment of the situation (no softening or burying the lead) - Brief explanation without excuses - Clear statement of what is being done about it - Specific ask (if any) - Professional, confident tone — not apologetic or panicked This person needs to trust me after reading this. Write accordingly.

Create a lessons learned document for a completed project. Project: [PROJECT NAME] Duration: [START DATE to END DATE] Delivered on time: [YES / NO — if no, by how long?] Delivered on budget: [YES / NO — if no, by how much?] Team size: [NUMBER] What went well: [LIST 3-5 THINGS THAT WORKED] What did not go well: [LIST 3-5 THINGS THAT CAUSED PROBLEMS] What surprised us: [LIST ANYTHING UNEXPECTED — positive or negative] What we would do differently: [YOUR OWN REFLECTION] Create a professional lessons learned document with: 1. Executive summary (3 sentences) 2. What worked — with specific recommendations to repeat 3. What did not work — with specific recommendations to avoid or change 4. Process improvements for the next project 5. A one-page summary suitable for the project archive Make this useful for the next PM who runs a similar project — not just a formality.

Write a final project completion report to send to all stakeholders. Project: [PROJECT NAME] PM: [YOUR NAME] Start date: [DATE] — End date: [DATE] Original deadline: [DATE] — Actual delivery: [DATE] Original budget: [$AMOUNT] — Final cost: [$AMOUNT] Deliverables completed: [LIST EACH DELIVERABLE AND ITS STATUS] Key outcomes achieved: [LIST MEASURABLE BUSINESS RESULTS] Challenges overcome: [BRIEFLY DESCRIBE 2-3 CHALLENGES AND HOW THEY WERE RESOLVED] Team members to acknowledge: [LIST NAMES AND THEIR CONTRIBUTION] Write a professional completion report that: - Leads with what was achieved for the business - States timeline and budget performance clearly - Acknowledges the team - Closes the project formally - Leaves a positive lasting impression with all stakeholders

Write a team release and thank-you message for the end of a project. Project: [PROJECT NAME] Duration: [X weeks/months] Team members: [LIST NAMES AND ROLES] Specific contributions to mention: - [PERSON]: [WHAT THEY DID THAT DESERVES SPECIFIC MENTION] - [PERSON]: [WHAT THEY DID THAT DESERVES SPECIFIC MENTION] Project outcome: [DELIVERED ON TIME / LATE / EARLY — and the key result] Tone: [WARM AND PERSONAL / PROFESSIONAL / CELEBRATORY] Write a message that: - Formally releases team members from project responsibilities - Acknowledges specific contributions (not generic praise) - States what was accomplished together - Closes the project psychologically for the team - Leaves every person feeling their work mattered Keep it under 200 words. Genuine, not corporate.

Create a one-page project archive summary for our project knowledge base. Project: [PROJECT NAME] Type: [TYPE OF PROJECT] Duration: [DATES] Team: [SIZE AND DEPARTMENTS] Budget: [FINAL COST] Outcome: [SUCCESS / PARTIAL SUCCESS / CANCELLED — brief reason] Key facts: - Biggest challenge: [ONE SENTENCE] - Biggest success: [ONE SENTENCE] - Technology/tools used: [LIST] - Vendors/suppliers involved: [LIST] - Stakeholders: [LIST ROLES — not names] Top 3 recommendations for anyone running a similar project: [YOUR TOP 3 PIECES OF ADVICE] Top 3 things to avoid: [YOUR TOP 3 WARNINGS] Format as a clean one-page document. Someone should be able to read this in 2 minutes and understand everything they need to know before starting a similar project.