Best ChatGPT Prompts for Project Managers (2026)

You are a project management assistant helping a project manager draft a project charter. Write a structured project charter outline for the project described below. Include: project title and version, purpose and business justification (why this project exists and what problem it solves), project objectives (3–5 SMART goals), scope (what is in scope and explicitly what is out of scope), key deliverables (the concrete outputs of this project), high-level milestones and target dates, key stakeholders and their roles (sponsor, PM, core team, key influencers), assumed resources and budget range, known constraints and assumptions, and a preliminary risk summary (2–3 top risks). Format as a structured document a project sponsor can review and approve.

PROJECT DETAILS:
- Project name: [NAME]
- Project sponsor: [ROLE/DEPARTMENT]
- Project type: [SOFTWARE DEVELOPMENT / PROCESS IMPROVEMENT / PRODUCT LAUNCH / INFRASTRUCTURE / OTHER]
- Methodology: [WATERFALL / AGILE / HYBRID / PRINCE2 / OTHER]
- Business problem or opportunity: [DESCRIBE THE DRIVER — what pain point or opportunity is this addressing?]
- Target completion: [DATE OR TIMEFRAME]
- Approximate team size: [NUMBER AND ROLES]
- Known constraints: [BUDGET LIMIT / DEADLINE / RESOURCES / REGULATORY / OTHER]
- Key stakeholders: [LIST MAIN STAKEHOLDERS AND THEIR INTEREST]

Write a clear, professional project scope statement for the project described below. The scope statement should include: project purpose (one paragraph explaining the business case), deliverables (a numbered list of what this project will produce — be specific), inclusions (what tasks, systems, or work are definitely in scope), exclusions (what is explicitly NOT in scope — this is critical for scope management), acceptance criteria (how will the project sponsor and stakeholders verify each deliverable is complete and acceptable), and constraints and assumptions (list any known constraints that bound the project and assumptions that must hold true for the scope to remain valid). This document will be used as the baseline for scope change management — write with precision.

PROJECT DETAILS:
- Project name: [NAME]
- Project type: [DESCRIBE THE TYPE OF PROJECT]
- Methodology: [AGILE / WATERFALL / HYBRID]
- End goal (in one sentence): [WHAT THE PROJECT MUST ACHIEVE]
- What is definitely in scope: [LIST THE MAJOR WORKSTREAMS, FEATURES, OR ACTIVITIES]
- What might be confused as in scope but isn't: [EXCLUSIONS TO MAKE EXPLICIT]
- Key stakeholders approving scope: [ROLES]
- Expected duration: [TIMEFRAME]
- Known constraints: [BUDGET / HEADCOUNT / TECHNOLOGY / DEADLINE]

Break down the high-level project goal described below into a structured milestone plan. For each milestone provide: milestone name and description (what has been completed by this point), target date or phase, key deliverables included, dependencies (what must be true before this milestone can be reached), and success criteria (how you will know the milestone is achieved). Order the milestones sequentially. After the milestone list, add a brief section on critical path risk — identify which milestone is most likely to slip and why, and what buffer or contingency should be built around it.

PROJECT DETAILS:
- Project goal (in one sentence): [THE END STATE YOU ARE TRYING TO REACH]
- Project type: [DESCRIBE]
- Methodology: [WATERFALL / AGILE / HYBRID]
- Team size: [NUMBER AND KEY ROLES]
- Target end date: [DATE]
- Known constraints: [BUDGET / RESOURCES / EXTERNAL DEPENDENCIES]
- High-level phases or themes already identified: [LIST IF KNOWN — or "none, start from scratch"]
- Any fixed milestones or gates (e.g., board approval, go-live date): [LIST]

Generate a Work Breakdown Structure (WBS) for the project described below. Organize the WBS into: Level 1 — the project as a whole, Level 2 — major deliverables or project phases (5–8 items), Level 3 — work packages within each deliverable (3–5 items per Level 2 node), Level 4 — tasks within each work package where detail is warranted. For each work package at Level 3, include a brief description of what it produces and who is typically responsible (by role). Format as an outline with numbered coding (1.0, 1.1, 1.1.1, etc.). After the WBS, add a section identifying the 3 most complex or risky work packages and briefly explain why.

PROJECT DETAILS:
- Project name: [NAME]
- Project type: [SOFTWARE / INFRASTRUCTURE / PROCESS / PRODUCT LAUNCH / ORGANIZATIONAL CHANGE / OTHER]
- Methodology: [WATERFALL / AGILE — note: for Agile, map the WBS to epics and user stories]
- Key deliverables (high-level): [LIST 4–6 MAJOR OUTPUTS]
- Team composition (by role): [LIST ROLES — e.g., PM, developer x2, QA, business analyst, SME]
- Duration: [TIMEFRAME]
- Any workstreams to explicitly include: [LIST]
- Any workstreams to exclude: [LIST OR "none"]

Write a concise executive status update for the project described below. The update should be readable in under 2 minutes and include: overall project status (RAG — Red/Amber/Green — with one sentence explaining the rating), progress summary (what was completed since the last update — bullet points, not prose), upcoming milestones (next 2–4 key milestones with target dates), issues and risks requiring executive awareness (only items that need escalation or decision — not a full risk register), decisions needed (if any — be explicit about what you need from the executive, by when), and budget status (current spend vs. plan, plus any variance). Tone: direct, factual, no padding. Format: executive memo or slide narrative, under 400 words.

PROJECT DETAILS:
- Project name: [NAME]
- Reporting period: [DATE RANGE]
- Overall status: [RED / AMBER / GREEN] — reason: [ONE SENTENCE]
- Key accomplishments this period: [BULLET LIST]
- Upcoming milestones: [NEXT 2–4 MILESTONES WITH DATES]
- Issues or risks needing executive attention: [LIST — or "none at this time"]
- Decisions needed from leadership: [WHAT, BY WHEN — or "none at this time"]
- Budget: [SPENT TO DATE] vs. [APPROVED BUDGET] — variance: [AMOUNT / %]

Write a stakeholder-facing risk summary for the project described below, suitable for inclusion in a project status report or steering committee update. For each risk listed, structure the entry as: risk ID and name, brief plain-language description (what could go wrong and why), likelihood (High/Medium/Low), impact (High/Medium/Low), overall risk rating, current status (open, mitigating, or closed), mitigation strategy (what is being done to reduce likelihood or impact), and owner (by role). After the risk entries, add a summary paragraph: current overall risk posture of the project, any risks that have materialized since the last report, and any risks that have been closed. Format for a non-technical audience — avoid jargon.

RISK DETAILS:
- Project name: [NAME]
- Project phase: [PLANNING / EXECUTION / TESTING / CLOSE-OUT]
- Risks to document: [LIST EACH RISK — describe what could go wrong]
- For each risk, provide: likelihood, impact, current mitigation in place, risk owner (role)
- Any risks that have materialized (became issues): [LIST OR "none"]
- Any risks closed since last report: [LIST OR "none"]
- Audience: [EXECUTIVE STEERING COMMITTEE / SPONSOR / CLIENT / INTERNAL TEAM]

Create a structured project kickoff meeting agenda for the project and team described below. The agenda should: open with introductions and attendee roles (time-boxed), cover the project purpose and business case (why we are doing this — not assumed knowledge), review the scope, deliverables, and what is out of scope, walk through the project plan and key milestones, cover team structure, RACI assignments, and communication norms (how the team will work together), address known risks and open questions, and close with agreed next steps and owners. Include facilitator notes for each section, a recommended time allocation, and a short pre-read list (what attendees should review before the meeting). Format as a shareable agenda document.

KICKOFF DETAILS:
- Project name: [NAME]
- Date, time, and format: [IN-PERSON / VIRTUAL / HYBRID — platform if virtual]
- Estimated duration: [60 / 90 / 120 MINUTES]
- Attendees and roles: [LIST — e.g., project sponsor, PM, core team members, key stakeholders]
- Project methodology: [WATERFALL / AGILE / HYBRID]
- Key items to cover (add to standard agenda): [ANY SPECIFIC TOPICS — vendor intro, tool demo, org context]
- Tone of the meeting: [FORMAL STEERING COMMITTEE / COLLABORATIVE TEAM LAUNCH / CLIENT-FACING]
- Pre-read materials to reference: [DOCUMENTS OR "to be distributed by PM"]

Write a professional meeting recap for the meeting described below. The recap should include: meeting metadata (project name, meeting type, date, attendees by name/role), a 2–3 sentence summary of what was discussed and the key outcomes or decisions reached, a detailed decisions log (each decision made, who owns it, any conditions or caveats), a numbered action item list (each item: description, owner by role, due date, priority), open items or questions raised but not resolved (with planned resolution path), and next meeting date and agenda preview if applicable. Tone: clear and factual — this document becomes the project record. It should be usable without attending the meeting.

MEETING DETAILS:
- Project name: [NAME]
- Meeting type: [STATUS UPDATE / DECISION MEETING / DESIGN REVIEW / RETROSPECTIVE / KICKOFF / OTHER]
- Date and duration: [DATE, LENGTH]
- Attendees: [NAMES/ROLES]
- Key discussion topics: [BULLET LIST — what was talked about]
- Decisions made: [WHAT WAS DECIDED — who decided, any conditions]
- Action items: [EACH ITEM WITH OWNER AND DUE DATE]
- Unresolved items or questions: [LIST OR "none"]
- Next meeting: [DATE / "TBD"]

Generate a comprehensive risk register for the project described in the brief below. For each risk, include: risk ID, risk category (schedule / budget / resource / technical / stakeholder / compliance / external), risk description (what could go wrong — written as an event, not a condition), root cause (why this risk exists), likelihood (1–5 scale), impact (1–5 scale), risk score (likelihood × impact), risk rating (High 15–25 / Medium 6–14 / Low 1–5), risk owner (by role), current status, mitigation strategy (what will reduce likelihood), contingency plan (what will happen if the risk materializes), and trigger (the early warning sign that indicates this risk is becoming an issue). Include at least 8–10 risks. Prioritize by risk score, highest first.

PROJECT BRIEF:
- Project name: [NAME]
- Project type: [DESCRIBE]
- Methodology: [AGILE / WATERFALL / HYBRID]
- Project phase: [PLANNING / INITIATION / EXECUTION]
- Team size: [NUMBER AND KEY ROLES]
- Budget: [APPROXIMATE AMOUNT OR RANGE]
- Timeline: [START DATE — END DATE]
- Key dependencies: [EXTERNAL VENDORS / OTHER PROJECTS / REGULATORY APPROVALS / etc.]
- Known constraints: [LIST]
- Business context: [STRATEGIC IMPORTANCE, ORGANIZATIONAL PRESSURES, STAKEHOLDER SENSITIVITIES]

Write a professional issue escalation memo for the project issue described below. The memo should: clearly state the issue in the subject line and first sentence (no burying the lead), provide the background context needed to understand the issue (when it emerged, what triggered it), explain the current impact (on timeline, budget, team capacity, scope, or stakeholder relationships — be specific with numbers where possible), describe what has already been tried to resolve the issue at the team level, state explicitly why escalation is needed (decision authority, resources, or stakeholder access beyond PM scope), present 2–3 resolution options with pros/cons and a recommendation, specify the decision or action needed from the escalation recipient, and state the deadline by which the decision is needed and the consequences of delay. Tone: urgent but professional. Length: under one page.

ESCALATION DETAILS:
- Project name: [NAME]
- Issue summary: [ONE SENTENCE — what the issue is]
- Issue type: [SCOPE CHANGE / RESOURCE CONFLICT / TECHNICAL BLOCKER / VENDOR FAILURE / STAKEHOLDER CONFLICT / BUDGET OVERRUN / REGULATORY / OTHER]
- When it emerged: [DATE / PHASE]
- Impact: [DESCRIBE — days of delay, cost overrun, scope at risk, team affected]
- What has been tried: [ACTIONS ALREADY TAKEN AT PM LEVEL]
- Why escalation is needed: [WHAT REQUIRES AUTHORITY OR ACCESS BEYOND PM]
- Resolution options: [2–3 OPTIONS WITH QUICK PRO/CON SUMMARY]
- Your recommendation: [WHAT YOU THINK SHOULD HAPPEN]
- Decision needed by: [DATE — and what happens if no decision is made]
- Escalating to: [ROLE / LEVEL]

Build a detailed risk mitigation plan for the project risk described below. The plan should include: risk statement (full description of the risk event and its potential consequences), risk context (why this risk exists in this project — root cause analysis), current risk rating (likelihood and impact with scoring rationale), mitigation actions (a numbered list of specific, actionable steps that will reduce the likelihood or impact of this risk — each with an owner, start date, completion date, and success metric), contingency actions (what the team will do if the risk materializes despite mitigation — trigger criteria, response steps, owner, and escalation path), residual risk assessment (what the risk rating becomes after mitigation is in place), monitoring approach (how the team will track this risk — review cadence, leading indicators, responsible party), and budget estimate for mitigation activities if applicable. Format as a standalone risk mitigation document.

RISK DETAILS:
- Project name: [NAME]
- Risk description: [WHAT COULD GO WRONG]
- Risk category: [SCHEDULE / BUDGET / TECHNICAL / RESOURCE / STAKEHOLDER / COMPLIANCE / EXTERNAL]
- Current likelihood: [HIGH / MEDIUM / LOW] — reason: [BRIEF RATIONALE]
- Current impact if it occurs: [HIGH / MEDIUM / LOW] — reason: [BRIEF RATIONALE]
- What has already been done to address this risk: [OR "nothing yet"]
- Key stakeholders affected: [ROLES / DEPARTMENTS]
- Available resources for mitigation: [HEADCOUNT, BUDGET, OR CONSTRAINTS]
- Trigger for contingency activation: [WHAT EVENT SIGNALS THE RISK HAS MATERIALIZED]

Create a structured post-mortem (lessons learned) framework for the completed project described below. The framework should facilitate an honest, blame-free retrospective and produce actionable recommendations. Include: an opening section summarizing project outcomes vs. original plan (scope, schedule, budget, and quality), a "what went well" section structured to capture the specific practices, decisions, and team behaviors that drove success — not generic praise, a "what could be improved" section organized by project domain (planning, execution, communication, risk management, tools, team dynamics) — each item should include the root cause and a specific recommendation, a section on major risks and issues that materialized — what the team learned from each, a stakeholder and communication debrief (how well did stakeholder management work? what would change?), proposed process changes for future projects (ranked by expected impact), and a summary of key metrics: planned vs. actual timeline, budget variance, scope changes requested vs. approved, and team utilization.

PROJECT DETAILS:
- Project name: [NAME]
- Project type: [DESCRIBE]
- Duration: [PLANNED vs. ACTUAL]
- Budget: [PLANNED vs. ACTUAL]
- Scope: [DELIVERED vs. ORIGINAL SCOPE — any changes?]
- Team size: [NUMBER AND ROLES]
- What went well (from your perspective): [LIST — or "to be discussed in the session"]
- What did not go well or caused friction: [LIST — or "to be discussed"]
- Major risks that materialized: [LIST OR "none"]
- Key stakeholder feedback received: [SUMMARY OR "not yet gathered"]
- Post-mortem format: [FACILITATED WORKSHOP / ASYNC SURVEY + SYNC DISCUSSION / DOCUMENT-ONLY]

Create a structured sprint retrospective agenda for the agile team described below. The agenda should: be time-boxed to the duration specified, open with a brief icebreaker or energizer (5 minutes — appropriate to the team's culture), review the sprint goal and what was delivered vs. committed (5 minutes — data only, no blame), run a structured retrospective activity appropriate for the team's maturity and current dynamics (this is the core — 40–50% of time; suggest 2 format options with instructions), synthesize the discussion into a prioritized list of improvement actions (3–5 maximum — with owner, target sprint, and success metric), close with a team appreciation moment (individual or group acknowledgment), and assign a follow-up owner who ensures retro actions are tracked. Include a facilitator guide with timing, suggested questions for each section, and notes on how to handle common dysfunction (silence, one dominant voice, blame language). This prompt works for both chatgpt for agile teams running Scrum and chatgpt prompts for scrum masters facilitating regular cadences.

TEAM DETAILS:
- Team name: [NAME]
- Sprint number: [NUMBER]
- Sprint goal: [WHAT THE TEAM WAS TRYING TO ACHIEVE]
- What was completed vs. committed: [SUMMARY OR "to pull from sprint board"]
- Team size: [NUMBER]
- Team maturity: [FORMING / STORMING / NORMING / PERFORMING]
- Current team dynamic: [COLLABORATIVE / SOME TENSION / HIGH PERFORMING / STRUGGLING]
- Retrospective format: [IN-PERSON / REMOTE / HYBRID]
- Duration: [60 / 90 / 120 MINUTES]
- Any recurring issues to address: [LIST — or "general retrospective"]
- Any topics to avoid or handle with care: [LIST — or "none"]

Write structured, actionable performance feedback for the team member described below, suitable for a formal performance review, a mid-project check-in, or a 360-degree feedback submission. The feedback should: open with a specific, genuine strength observation (not generic praise — cite a concrete example), address 1–2 areas for development (framed as growth opportunities, not criticisms — each with a specific, observable behavior and a clear suggestion for what to do differently), note the impact of this person's work on the project and team, include a specific forward-looking statement (what you are counting on from them in the next phase), and close with a sincere statement of confidence or appreciation. Tone: direct, supportive, and professional. Length: 200–350 words. Do not use vague phrases like "great attitude" or "team player" without specifics.

TEAM MEMBER DETAILS:
- Role: [PROJECT MANAGER / BUSINESS ANALYST / DEVELOPER / QA / SCRUM MASTER / PRODUCT OWNER / etc.]
- Project context: [WHAT THE PROJECT IS, WHAT PHASE, WHAT THEY WERE RESPONSIBLE FOR]
- Specific strength to highlight: [DESCRIBE A CONCRETE EXAMPLE — what they did and what it achieved]
- Area for development: [DESCRIBE AN OBSERVED BEHAVIOR — what happened, what was the impact]
- Relationship (reviewer to reviewee): [PEER / DIRECT REPORT / UPWARD FEEDBACK]
- Tone calibration: [CRITICAL REVIEW NEEDED / MOSTLY POSITIVE WITH COACHING / STRONG POSITIVE]
- What you need from them in the next phase: [SPECIFIC EXPECTATION]

Create a 30-60-90 day onboarding plan for a new project manager joining the team and organization described below. For each phase include: key learning objectives (what they need to understand by the end of this period), activities (meetings, shadowing, reading, hands-on tasks — specific and sequenced), relationships to build (who they must connect with and why — by role), tools and systems to master (with priority level), deliverables or milestones (what they will produce or achieve to demonstrate progress), and a success check-in (what does success look like at the end of this phase?). The plan should balance cultural integration, technical upskilling, and relationship-building — and give the new PM clear line-of-sight to when they will be running independently.

CONTEXT DETAILS:
- New PM's background: [EXPERIENCED PM / INTERNAL PROMOTION / NEW TO PM / CAREER CHANGER]
- Role: [PROJECT MANAGER / SCRUM MASTER / PROGRAM MANAGER / DELIVERY LEAD]
- Team type: [PRODUCT / IT / OPERATIONS / CONSULTING / CROSS-FUNCTIONAL]
- Methodology used: [AGILE / SCRUM / WATERFALL / HYBRID]
- Key tools and systems: [PROJECT MANAGEMENT TOOL, COMMUNICATION TOOL, WIKI, etc.]
- Projects they will own: [DESCRIBE — existing projects or greenfield?]
- Team size and culture: [NUMBER OF PEOPLE, CULTURE DESCRIPTORS]
- Key stakeholders they need to build relationships with: [LIST ROLES]
- Manager's availability for support: [HIGH / MEDIUM / LIMITED — e.g., weekly 1:1 or more]

Write a structured conflict resolution script for a project manager mediating the team dispute described below. The script should: open with framing language that establishes a safe, neutral space (what the PM will say at the start of the mediation conversation), include active listening prompts for each party (what to ask to draw out each perspective without escalating), provide a technique for identifying the root issue vs. the presenting complaint (the "what's under the surface" moment), include language for establishing common ground and shared stakes (what both parties actually agree on, even if they don't know it yet), offer a structured problem-solving turn (how to move from positions to interests), end with a commitment protocol (how to close the conversation with clear agreements, follow-up, and accountability), and include a sidebar note on what to do if the conversation escalates. This is a coaching script — adapt to your voice and style.

CONFLICT DETAILS:
- Conflict type: [INTERPERSONAL / ROLE AMBIGUITY / RESOURCE ALLOCATION / TECHNICAL DISAGREEMENT / WORKLOAD / SCOPE / REPORTING LINE / OTHER]
- Parties involved (by role): [ROLE 1 vs. ROLE 2 — or team vs. individual]
- What each party wants (surface complaint): [WHAT THEY HAVE EACH SAID OR INDICATED]
- Likely underlying interest or fear: [WHAT YOU THINK IS REALLY DRIVING THIS]
- What you have tried so far: [OR "first intervention"]
- Project impact: [HOW THIS CONFLICT IS AFFECTING DELIVERY, MORALE, OR STAKEHOLDERS]
- Your role in this conflict: [NEUTRAL MEDIATOR / ALSO INVOLVED / LINE MANAGER OF ONE PARTY]
- Tone required: [INFORMAL CHECK-IN / FORMAL MEDIATION / URGENT INTERVENTION]

Write a complete Standard Operating Procedure (SOP) from the workflow description below. The SOP should include: a header section (SOP title, version number, effective date, process owner, review date, applicable teams), a purpose and scope section (what this process does and to whom it applies — and any explicit exclusions), a definitions section (key terms, acronyms, or role names used in the procedure), a prerequisites section (what must be true before the procedure begins — tools, access, approvals, prior steps), the step-by-step procedure (numbered steps in chronological order — each step with an action, the responsible role, the tool or system used, and any decision point branches), a quality and compliance section (how to verify the process was completed correctly, any audit trail or sign-off required), and a revision history table. Write at a level of detail that allows a new team member with general professional competence to execute the procedure correctly on the first attempt.

WORKFLOW DETAILS:
- Process name: [NAME]
- Process type: [ADMINISTRATIVE / TECHNICAL / CLIENT-FACING / OPERATIONAL / COMPLIANCE / OTHER]
- Frequency: [DAILY / WEEKLY / PER PROJECT / AD HOC / TRIGGERED BY EVENT]
- Roles involved: [LIST ALL ROLES WITH A STEP IN THIS PROCESS]
- Tools/systems used: [LIST WITH PURPOSE]
- Process steps (describe the workflow as you know it): [DESCRIBE IN PLAIN LANGUAGE — as many steps as you know]
- Key decision points: [WHERE DOES THE PROCESS BRANCH? WHAT TRIGGERS EACH PATH?]
- Common errors or failure modes: [WHAT GOES WRONG — and what should happen when it does]
- Compliance or quality requirements: [REGULATORY / INTERNAL AUDIT / CLIENT SLA / NONE]

Create a structured lessons learned document for the project described below. This document will be stored in the organization's project knowledge base and used to improve future project delivery. Organize it as: executive summary (3–4 sentences summarizing what type of project this was, how it performed overall, and the 2–3 most important lessons), project performance snapshot (planned vs. actual: timeline, budget, scope, and quality rating), key findings organized by category — planning and scope management, risk and issue management, stakeholder and communication management, team and resource management, tools and process efficiency — for each category: what worked, what didn't, root cause of issues, and the specific recommendation for future projects, top 5 recommendations (ranked by expected impact on future delivery, with the role responsible for implementing each), and an artifacts index (list of project documents available for reference, with storage location). Write in a tone that is honest and forward-looking — not a performance review, not a blame document.

PROJECT DETAILS:
- Project name: [NAME]
- Project type: [DESCRIBE]
- Duration: [PLANNED vs. ACTUAL — note any slippage]
- Budget: [PLANNED vs. ACTUAL — note any overrun]
- Scope changes: [NUMBER OF APPROVED CHANGES / SCOPE CREEP INCIDENTS]
- Team size: [NUMBER AND COMPOSITION]
- Top 3 things that went well: [BE SPECIFIC]
- Top 3 things that caused problems: [BE SPECIFIC — what happened and why]
- Key risks that materialized: [LIST OR "none significant"]
- Stakeholder satisfaction: [HIGH / MEDIUM / LOW — any specific feedback]
- Methodology used: [AGILE / WATERFALL / HYBRID]

Conduct a structured process gap analysis for the process described below. The analysis should produce: a current-state summary (how the process works today, based on the input I provide), a desired-state definition (how the process should ideally work — derive from the goals and constraints I provide), a gap table (for each dimension of the process — inputs, activities, tools, roles, outputs, timing, and quality controls — describe the current state, the desired state, the gap, and a recommended action to close it), a root cause analysis section (for the top 2–3 gaps: what is the underlying cause — system, process design, knowledge, resource, culture, or incentive?), a prioritized improvement roadmap (rank the gaps by: impact on performance, ease of implementation, and dependencies between improvements — output as a 3-column table: quick wins / medium-term / long-term), and success metrics (how will you know the gap has been closed? define a measurable indicator for each top-priority gap).

PROCESS DETAILS:
- Process name: [NAME]
- Process type: [OPERATIONAL / ADMINISTRATIVE / TECHNICAL / CLIENT-FACING / REPORTING / OTHER]
- Current-state description: [HOW THE PROCESS WORKS TODAY — as much detail as you know]
- Known problems or pain points: [WHAT IS GOING WRONG OR WHAT STAKEHOLDERS COMPLAIN ABOUT]
- Desired outcomes: [WHAT SUCCESS LOOKS LIKE — speed, accuracy, cost, experience, compliance]
- Stakeholders affected: [LIST ROLES WHO PARTICIPATE IN OR ARE IMPACTED BY THIS PROCESS]
- Constraints: [WHAT CANNOT CHANGE — budget, tools, headcount, regulatory requirements]
- Comparison reference: [INDUSTRY BEST PRACTICE / INTERNAL BENCHMARK / CLIENT REQUIREMENT / OTHER]

Generate a RACI matrix for the project described below. For each project activity or deliverable listed, assign a RACI designation to each stakeholder role: R (Responsible — the role doing the work), A (Accountable — the role who owns the outcome and signs off — only one per row), C (Consulted — roles whose input is needed before or during the work), I (Informed — roles who are updated on progress or decisions but don't input). After the matrix, add: a RACI legend explaining each designation, a summary of accountability concentrations (which roles carry the most accountable items — are any over-loaded or under-leveraged?), a list of any ambiguous or conflicting assignments that should be discussed with the team, and 3 recommendations for improving role clarity on this project based on the RACI pattern. Format as a table.

PROJECT DETAILS:
- Project name: [NAME]
- Project type: [DESCRIBE]
- Methodology: [AGILE — adapt to epics/stories if needed / WATERFALL / HYBRID]
- Stakeholder roles to include in the matrix: [LIST ALL ROLES — e.g., Project Sponsor, PM, Business Analyst, Tech Lead, Developer, QA, Operations, Legal, Finance, End User]
- Project activities or deliverables to assign (list them): [LIST EACH DELIVERABLE OR MAJOR ACTIVITY — e.g., Project Charter, Requirements Gathering, Solution Design, Development, Testing, Deployment, Training, Post-Launch Support, Project Close]
- Any known confusion or conflict around responsibilities: [DESCRIBE SPECIFIC TENSIONS — or "generate from standard PM practice"]
- Team size: [NUMBER]
- Key decision-making norms: [CONSENSUS / SINGLE OWNER / SPONSOR-LED]