Project plans collapse when they list tasks without ranking by impact, never name an owner, and bury risks in a slide nobody reopens. These prompts force milestone-level deliverables, explicit assumptions, a ranked risk register, and a scope-cut menu — so when reality hits week three, you cut painlessly instead of slipping silently. Pair with project risk analysis prompts for deeper risk work.
Best for
- Sprint planning
- New initiative scoping
- Multi-team programs
- Cross-functional launch plans
- Personal big projects (book, move, course)
1. Goal → milestones (with assumptions)
My goal: {1 sentence}. Constraints: {time, team, budget}. Break into 4-6 milestones. For each: deliverable, success criteria, 1 key assumption that could invalidate it. Flag the milestone whose assumption is shakiest — that's where to test first.2. Milestone → tasks
Milestone: {description}. Owner: {team}. Available time: {N weeks}. Break into tasks ≤2 days each. Mark dependencies between tasks. Estimate optimistic / realistic / pessimistic days for each.3. 2-week sprint plan
Given backlog (paste), team capacity {N points}, top priority {goal}: plan a 2-week sprint. Output: sprint goal in 1 sentence, committed items, stretch items, risks. Reserve 20% capacity for unplanned work.
{paste}4. Risk register
My project plan (paste). Identify top 8 risks. For each: probability (L/M/H), impact (L/M/H), mitigation, contingency, owner. Sort by probability × impact. Distinguish risks (uncertain) from issues (already happening).
{paste}5. RACI matrix
Project: {summary}. Stakeholders: {list with roles}. Build a RACI matrix for the 8 most important workstreams. Flag any workstream with more than 1 Accountable — that's a problem.6. Critical-path identification
Below are my project tasks with dependencies. Identify the critical path. Mark the 3 tasks where slipping by 1 day slips the whole project by 1 day. Suggest 2 ways to compress the critical path: fast-track (parallelize) or crash (add resources).
{paste}7. Status update from plan + reality
My plan: {paste}. What actually happened this week: {paste reality}. Write a 150-word status update: on track / at risk / blocked, with one specific next-week priority and a single "what I need from you" ask.8. Scope cut menu
I have 3 weeks left and likely 5 weeks of work. Plan: {paste}. Produce a "scope cut menu": 5 items I could cut, what we lose, what we keep, who would notice. Rank by least painful first.9. Pre-mortem on the plan
Project: {summary}. Plan: {paste}. Imagine it's 6 months from now and the project failed. Write the postmortem: top 5 reasons it failed, sorted by likelihood. For each, name the leading indicator we'd see in week 2 if we were heading toward that failure.
{paste}10. Stakeholder communication cadence
Project: {summary}. Stakeholders: {list with seniority + interest level}. Design a communication cadence: who gets updates, in what format (Slack thread / weekly email / monthly review), at what frequency, and what decision each update is meant to enable. Avoid status-for-status's-sake.11. Kickoff meeting agenda
Project: {summary}. Team: {list}. Design a 60-minute kickoff agenda that ends with these artifacts: a shared goal in 1 sentence, top 3 risks, owner per workstream, the 1 question we'd most regret not asking. Include rough timeboxes per section.Common mistakes
- Listing tasks without milestones or outcomes — the plan reads like a to-do list, not a project
- No risks captured, or risks captured once and never revisited as new ones emerge
- No explicit Accountable per workstream — everyone thinks someone else owns it
- Critical path never identified, so the team optimizes the wrong tasks
- No scope-cut menu prepared in advance — when slip happens, cuts get made under panic
- Status updates that report activity (“did 12 things”) instead of outcomes against the goal