AI Project Manager — Plans, Tasks & Status Updates

Help me create a project scope document for the following initiative. **Project Overview:** - Project name: [e.g., 'Q3 Website Redesign' / 'New Customer Onboarding Flow' / 'Office Relocation'] - What we're trying to accomplish: [2-3 sentences describing the goal] - Why this matters: [Business impact — e.g., 'Current checkout conversion is 2.1%, industry average is 3.8%, this project targets 3.5%'] - Who requested this: [Stakeholder name/role] **Constraints:** - Deadline: [Hard deadline or target date] - Budget: [Dollar amount or 'TBD'] - Team: [Who's working on this — roles, not names, e.g., '1 designer, 2 engineers, 1 PM'] - Dependencies: [What must be done first, or what other teams/systems are involved] - Known blockers: [Anything that could slow this down] **Out of Scope (important — what are we NOT doing):** - [List 2-3 things that might seem related but are explicitly excluded] Based on this, produce: 1. A one-paragraph project summary I can paste into a kickoff email 2. A SMART goal statement (Specific, Measurable, Achievable, Relevant, Time-bound) 3. A list of 5-8 success criteria — how will we know the project succeeded? 4. A risk register with the top 5 risks, their likelihood (High/Medium/Low), impact (High/Medium/Low), and a mitigation strategy for each 5. Key assumptions we're making that, if wrong, would change the project significantly Flag anything in my description that seems contradictory or unclear before proceeding.

Create a detailed Work Breakdown Structure (WBS) for this project: **Project:** [Project name from previous step] **Total timeline:** [e.g., '8 weeks' / '3 months' / 'by October 15'] **Methodology:** [Agile sprints / Waterfall phases / Kanban / Flexible — just use what makes sense] **Team and roles:** - [Role 1, e.g., 'Project Manager']: responsible for [what they own] - [Role 2, e.g., 'Designer']: responsible for [what they own] - [Role 3, e.g., 'Engineer']: responsible for [what they own] - [Add more roles as needed] Break this project into: **Phase/Milestone structure:** - Phase 1: [Discovery / Planning / Research] - Phase 2: [Design / Architecture / Prototyping] - Phase 3: [Build / Implementation / Development] - Phase 4: [Testing / Review / QA] - Phase 5: [Launch / Deployment / Delivery] - Phase 6: [Post-launch / Monitoring / Retrospective] For each phase, give me: 1. All tasks required to complete it (5-10 tasks per phase) 2. Estimated effort for each task in hours or days 3. Who owns each task (which role) 4. Dependencies — which tasks must be completed before this one can start 5. Definition of Done — what does 'completed' look like for this task Also flag: - Which tasks are on the critical path (delays here delay the whole project) - Which tasks can be parallelized - Any tasks I probably forgot to include based on projects like this Format the output as a table I can import into a project management tool.

Write detailed task descriptions for the following tasks from our project. For each task, produce a ready-to-use ticket description. **Project context:** [One sentence about the project] **Team context:** [Who will be doing these tasks — e.g., 'Junior designer who is new to the team' / 'Experienced backend engineer'] **Tasks to describe:** 1. [Task name, e.g., 'Conduct user interviews for checkout flow redesign'] 2. [Task name] 3. [Task name] 4. [Task name] 5. [Task name] For each task, write: **Title:** [Clear, action-oriented task name] **Owner:** [Role] **Estimated effort:** [Hours/days] **Priority:** [Critical / High / Medium / Low] **Description:** [2-3 sentences explaining what this task is, why it matters, and how it fits into the broader project] **Context and background:** [Relevant information the person doing this task needs to know — links to related docs, decisions already made, constraints to respect] **Steps to complete:** 1. [Step 1] 2. [Step 2] 3. [Continue as needed] **Acceptance criteria (Definition of Done):** - [ ] [Specific, verifiable condition 1] - [ ] [Specific, verifiable condition 2] - [ ] [Specific, verifiable condition 3] **Resources and dependencies:** - Depends on: [Task that must be done first] - Blocks: [Task that can't start until this is done] - Resources needed: [Tools, access, approvals] **Notes:** [Anything else the assignee should know]

Write a project status update for the following situation. **Project:** [Project name] **Report period:** [e.g., 'Week of March 17, 2026' / 'Sprint 4 (March 10-17)'] **Audience:** [e.g., 'Executive stakeholders' / 'Direct team members' / 'Client' / 'Cross-functional partners'] **Format:** [Email / Slack message / Document / Meeting agenda item] **What happened this week:** - Completed: [List tasks/milestones completed] - In progress: [List what's actively being worked on] - Blocked: [List anything stuck and why] - Not started (but planned): [List anything that was planned but didn't happen] **Metrics/progress:** - Overall project: [X% complete / On track / At risk / Off track] - Current milestone: [Name and % complete] - Budget: [On track / Over by X% / Under by X%] - Timeline: [On schedule / X days ahead / X days behind] **Key decisions made this week:** - [Decision 1 and who made it] - [Decision 2 and who made it] **What needs stakeholder attention:** - [Any decisions, approvals, or information needed from stakeholders] **Next week's focus:** - [Top 3-5 priorities for next week] Write the update in a tone appropriate for the audience. For executives: lead with status (Red/Yellow/Green), surface only decisions and blockers that need their input, skip operational detail. For team members: be specific about what's next and who needs to do what. For clients: confident, progress-focused, no internal jargon. Also suggest: is there anything in this update that should be escalated or flagged as a risk?

Help me run a project retrospective and produce a useful lessons-learned document. **Project:** [Project name] **Duration:** [Start date to end date] **Team size:** [Number of people and roles] **Outcome:** [Did it hit the goal? On time? On budget? Quality?] **Raw input from team (paste notes from retro session, or answer these yourself):** What went well: - [Input 1] - [Input 2] - [Input 3] What didn't go well: - [Input 1] - [Input 2] - [Input 3] What was confusing or unclear: - [Input 1] - [Input 2] Surprises (things we didn't anticipate): - [Input 1] - [Input 2] Based on this, produce: 1. **Pattern analysis**: Group similar observations and identify the 3 most important themes 2. **Root cause analysis** for the top 3 problems: use the '5 Whys' technique to get past symptoms to root causes 3. **Actionable improvements** for each root cause: - What specifically should change? - Who owns this change? - How will we know it worked? 4. **What to preserve**: The 3 things we should explicitly replicate in future projects 5. **One-paragraph project summary** suitable for a company wiki or knowledge base 6. **Template improvements**: Based on what was hard or unclear, what should we add/change in our project planning template for next time? Write the output as a structured document, not bullet soup.