Project Management prompts

Frame the project before it starts.

Draft a project charter for a [type] project. Details: objective [goal], sponsor [role], key deliverables [list], rough timeline [range], and known constraints [list]. Structure it with purpose, objectives, scope and out-of-scope, key stakeholders, high-level milestones, assumptions, and risks. Mark anything I left blank as a question to resolve, not a guess.

Nail scope, in and out.

Write a clear scope statement for this project: [describe]. Spell out what is explicitly in scope, what is explicitly out of scope, the key deliverables, and the acceptance criteria for each. Make the out-of-scope section thorough, since that's where scope creep starts.

Start the project aligned.

Create a kickoff meeting agenda for a [type] project with [who's attending]. Cover objectives, scope, roles, timeline, ways of working, risks, and questions, with rough timings for a [length] session, and end with a clear list of decisions we need to leave the room with.

Pin down scope before committing.

What are the sharpest questions I should ask stakeholders to pin down scope for a [type] project before I commit to a plan? Group them by area, objectives, constraints, dependencies, success criteria, and for each note why it matters so I can push past a vague answer.

Break the goal into tasks.

Break this project goal into a work breakdown structure: [describe the goal and scope]. Give me the major phases and, under each, the concrete tasks needed to complete it, as a nested list. Keep tasks at a level I could actually assign and track, and flag anything that looks like it hides a lot of unknown work.

Find the critical path.

Here's my task list for a project: [paste]. Help me sequence it: identify the dependencies, what must finish before what, suggest a sensible order, and point out the likely critical path. Don't assign durations, just the logic of what depends on what.

Make progress measurable.

Turn these phases and tasks into a milestone schedule outline: [paste]. Group the work into meaningful milestones with clear completion criteria for each, so progress is measurable, and flag the two or three milestones most likely to slip and why.

Plan a sprint without overcommitting.

Act as a senior agile PM. Draft a sprint planning outline for a [length] sprint. The team capacity is [describe], the sprint goal is [goal], and the candidate work is [paste]. Include the sprint goal, the stories or tasks that fit the capacity, and the risks to the goal. Don't overcommit the team.

Surface the hidden effort.

I need to estimate this piece of work with my team: [describe]. Give me a set of questions to ask that surface the hidden effort, unknowns, dependencies, testing, review, and a simple structure for capturing three-point estimates. I'll get the numbers from the team; help me ask better.

Surface the risks you forgot.

Create a risk register for a [type] project: [describe scope and context]. Identify 10 to 15 risks across technical, resource, schedule, vendor, and organisational categories. For each, give a short description, likelihood and impact as high, medium, or low, a risk score, a suggested owner, and a mitigation and contingency. Sort by score, highest first.

Sort risks, assumptions, issues, dependencies.

Build a RAID log for my project from these notes: [paste]. Sort what I've told you into risks, assumptions, issues, and dependencies, add anything obvious I've missed in each, and flag the two items in each category most worth acting on this week.

Stress-test a single risk.

Run a scenario analysis on this project risk: [describe]. Walk through what happens if it materialises, the knock-on effects on scope, schedule, and budget, the early warning signs to watch for, and the two or three responses ranked by cost versus effectiveness.

Brief the steering group.

Turn this risk register into a short risk review for a steering meeting: [paste]. Written plainly in the voice of a competent PM, no hype or filler, focused on the top risks, what's changed since last time, and the decisions or support I need from the steering group.

Structure the response fast.

An issue has come up mid-project: [describe]. Help me structure my response: the immediate impact, the options to resolve it with trade-offs, the recommendation, and how I'd communicate it to stakeholders without either downplaying it or causing a panic.

Honest, skimmable weekly update.

Write a weekly project status report from these notes: [paste]. Structure it as overall status (RAG), progress since last week, what's planned next, risks and issues, and decisions or help needed. Confident but honest about anything slipping, skimmable, and short enough that a busy sponsor actually reads it.

Give execs the point first.

Draft a steering committee update for a [type] project: [paste context]. Lead with status and the headline, then progress against milestones, the top risks, the budget position, and the specific decisions I need from them. Written for executives who want the point in the first two lines.

Own the slip, honestly.

I need to tell stakeholders the project is slipping by [time] because [reason]. Draft a straight, professional message: what changed, the impact on scope and dates, the recovery plan or the trade-off, and what I need from them. Own it without over-apologising, and end with the one clear ask.

Escalate without blaming.

Help me write an escalation about a blocker: [describe the blocker and who owns it]. Make it factual not blaming, clear about the impact if it isn't resolved by [when], and specific about the decision or action I'm asking for. Keep it short enough to act on quickly.

Map influence and interest.

Build a stakeholder map for this project: [describe the players and dynamics]. For each stakeholder, note their interest, their influence, what they care about, and how often and how I should communicate with them. Flag who could quietly derail this and how to keep them engaged.

Kill the status theatre.

Design a format for our [daily standup / weekly sync] that stays useful and doesn't drift into a status theatre. Give me the structure, the three questions or prompts that keep it focused, a time box, and one rule for handling the tangents that eat these meetings.

Turn notes into actions.

Turn my messy meeting notes into clean minutes: [paste]. Pull out the decisions made, the action items with owners and due dates, and the open questions, in a format people will actually read and act on. Keep it factual, and flag any action without a clear owner.

Get past 'it was fine'.

Design a retrospective for a team that's just finished [a sprint / a project phase] that went [well / badly]: [context]. Give me the format, the questions that get past 'it was fine' to real insight, and how to turn the discussion into two or three concrete changes rather than a vent.

Steer, don't referee.

Prep me to facilitate a difficult conversation between [parties] about [the disagreement]. Give me a neutral framing to open with, the questions that surface the real issue, and a structure to move from disagreement toward a decision, so I'm steering rather than refereeing.

Make the cost visible.

A stakeholder wants to add [the new request] mid-project. Help me draft a change request: what's being asked, the impact on scope, schedule, budget, and risk, the options, and a recommendation. Frame it as a decision for the sponsor, not a fight, and make the cost of the change visible.

Push back without obstructing.

I'm dealing with steady scope creep: [describe the small additions]. Draft a message that acknowledges the ideas, explains why unmanaged additions put the deadline at risk, and offers a clear process, log it, assess it, decide it, without sounding rigid or obstructive.

Know the cost before yes.

Assess the impact of this proposed change: [describe the change and the current plan]. Walk through the effect on the critical path, the resources, the budget, and the risks, and give me the questions I should answer before saying yes, so the decision is informed rather than reactive.

Stop relitigating settled calls.

Help me set up a simple decision log for this project. Given these recent decisions: [paste], structure each as the decision, the date, the rationale, who made it, and what it affects, so we stop relitigating settled questions and new people can catch up.

Balance people against time.

Help me think through resource allocation for a [type] project. The team is [describe skills and availability], the deadline is [when], and the work is [paste]. Suggest a sensible allocation, flag where I'm over-relying on one person, and lay out the trade-off between adding people and extending the timeline.

See the overloaded weeks.

I'm running [number] projects in parallel with a shared team: [describe]. Help me see the capacity conflicts, which weeks are overloaded and for whom, and suggest how to sequence or rebalance the work so nothing critical is starved. Tell me the trade-offs I'm choosing.

Cover the gap, fast.

A key person just became unavailable: [describe the situation and their work]. Help me plan the response: what's at risk, the options for covering it, ranked by disruption, and how I'd communicate the impact and the plan to stakeholders honestly.

One accountable per row.

Build a RACI matrix for this project. Here are the key activities: [list], and the roles or people involved: [list]. Assign responsible, accountable, consulted, and informed for each, flag any activity with no clear accountable owner or with too many, and keep exactly one accountable per row.

Close the gaps and overlaps.

Help me define clear roles and responsibilities for a [type] project team: [describe the roles]. For each role, spell out what they own, what they decide, and where the boundaries with other roles sit, so we avoid the gaps and the overlaps that cause friction later.

Honest about the misses.

Draft a project closure report from these notes: [paste]. Cover what was delivered against the original scope, the schedule and budget outcome, what went well, what didn't, and the key lessons. Honest about the misses, since a closure report that only lists wins helps no one.

Make lessons the next project uses.

Synthesise our lessons-learned notes into something the next project can actually use: [paste raw notes]. Group them into themes, turn each into a specific recommendation rather than a vague 'communicate better', and flag the two or three worth building into how we run projects from now on.