Project managers spend too much time writing documents and not enough time managing. AI can handle the writing — freeing PMs to focus on decisions and people.

Project Plan Creation

Project Charter

Create a project charter for:

Project name: [name]
Business problem/opportunity: [what triggered this project]
Objectives: [3-5 specific, measurable objectives]
Scope: 
- In scope: [list]
- Out of scope: [list]
Stakeholders: [list key stakeholders and their roles]
Timeline: [start date, end date, key milestones]
Budget: [if known]
Constraints: [time, budget, technical, resource]
Dependencies: [what this project depends on]

Create a formal project charter document including:
- Executive summary (3-4 sentences)
- Problem/opportunity statement
- Objectives and success criteria
- Scope definition
- High-level timeline
- Resource requirements
- Risks and assumptions
- Approvals section

Work Breakdown Structure

Create a Work Breakdown Structure for:

Project: [description]
Duration: [X weeks]
Team: [roles available]

Break down into phases and deliverables. For each task:
- Task name
- Description (1-2 sentences)
- Owner role
- Duration estimate
- Dependencies

Format as a hierarchical list:
Phase 1: [Name]
  1.1 [Deliverable]
    1.1.1 [Task]
    1.1.2 [Task]
  1.2 [Deliverable]
...

Status Reports

Weekly Status Report

Write a weekly project status report:

Project: [name]
Week ending: [date]
Overall status: [Green/Yellow/Red]

Accomplishments this week:
[paste your notes/updates from the team]

Planned next week:
[list what's planned]

Issues/risks:
[describe any problems or risks]

Budget: [X% of budget used, X% of timeline elapsed]

Format as a professional status report for:
- Audience: [executive sponsors / steering committee / team]
- Length: [1-2 pages / brief executive version]

Make it factual and concise. Flag what needs attention.

Executive Summary Update

Convert this detailed status update into a 3-paragraph executive summary:

[paste full status report]

Executive audience: [describe — C-suite, board, client, etc.]
Their key concerns: [what they care most about]

Summary should:
- Para 1: Where we are and if we're on track
- Para 2: Key accomplishments and upcoming milestones
- Para 3: Issues that need attention and recommended decisions
- End with: any decisions needed from executives

Maximum 200 words. No jargon.

Risk Management

Risk Register

Create a risk register for this project:

Project: [description]
Key project aspects: [technology, team, timeline, dependencies, budget, scope]
Known concerns: [list any risks you're already aware of]

For each risk, provide:
- Risk ID
- Description
- Category (technical / schedule / budget / resource / external)
- Probability (Low/Medium/High)
- Impact (Low/Medium/High)
- Risk score (Probability × Impact)
- Mitigation strategy
- Contingency plan
- Owner
- Status

Generate 10-15 risks covering different categories. 
Prioritize by risk score.

Risk Analysis for a Specific Issue

Analyze this project risk:

Situation: [describe the issue or potential risk]
Project context: [what kind of project, what stage, team size]

Provide:
1. Root cause analysis (5 Whys)
2. Probability estimate with justification
3. Potential impacts (schedule, budget, quality, stakeholder confidence)
4. 3 mitigation options with pros/cons of each
5. Recommended mitigation and owner
6. Early warning indicators to monitor
7. Escalation trigger (when to escalate to sponsor)

Stakeholder Communication

Meeting Agenda

Create an agenda for:

Meeting: [type — kickoff / status review / issue resolution / retrospective]
Duration: [X minutes]
Attendees: [list roles]
Goal: [what the meeting must accomplish]
Key topics to cover: [list]

Format:
- Welcome (2 min)
- [Topic] (X min) — Owner: [role]
- ...
- Next steps and action items (5 min)

For each agenda item: include the objective and any pre-read needed.

Difficult Stakeholder Message

Help me communicate this difficult project news:

Situation: [what happened — delay, budget issue, scope change, missed milestone]
Recipients: [who needs to know and their likely reaction]
My relationship with them: [describe]
What I need from them: [decisions, approval, understanding, resources]

Draft a message that:
1. States the situation clearly and honestly upfront
2. Explains the cause without making excuses
3. Presents options or the recommended path forward
4. Asks specifically for what I need
5. Is professional and confidence-inspiring

Tone: [formal / direct / collaborative]
Delivery: [email / presentation / conversation script]

Retrospectives

Retrospective Facilitation Guide

Help me plan a project retrospective for:

Project: [description]
Duration: [1 hour / 90 minutes]
Team size: [N people]
Relationship dynamic: [close team / mixed seniority / remote]
What went well: [your observations]
What was challenging: [your observations]

Create:
1. Facilitation guide with timing
2. Ice-breaker activity
3. 3-4 structured activities (not just "what went well")
4. How to prioritize improvements
5. How to capture and commit to action items
6. How to close positively

The goal: real insights and commitments, not a list of complaints.

Meeting Notes Processing

Convert these raw meeting notes into a structured meeting summary:

[paste rough notes]

Format:
1. Meeting: [title]
2. Date and attendees
3. Decisions made: (numbered list)
4. Action items: (each with owner and due date)
   - [ ] [Task] — [Owner] by [Date]
5. Key discussion points
6. Open questions / parking lot
7. Next meeting and agenda preview

Make action items specific enough that the owner knows exactly what to do.

Project Closure

Lessons Learned Document

Draft a lessons learned document for:

Project: [name]
Outcome: [successful / partially successful / cancelled / delayed]
Timeline: [original vs. actual]
Budget: [original vs. actual]
Key challenges we faced: [list]
Key successes: [list]
Team feedback: [any feedback collected]

Document should include:
1. Executive summary (what worked, what didn't)
2. Timeline performance with root causes of variance
3. Budget performance with root causes
4. Technical lessons (specific to this project type)
5. Process lessons (what to do differently next time)
6. What to repeat (what worked well)
7. Recommendations for future projects

Audience: Project management team and future PMs who run similar projects.