Create an execution-ready project plan for [PROJECT NAME]. Goal and context: [PROJECT GOAL] Scope: [DELIVERABLES AND EXCLUSIONS] Team: [PEOPLE, ROLES, CAPACITY, AND APPROVER] Constraints: [DEADLINE, BUDGET, FIXED DATES, RISKS] Known work: [REQUIREMENTS, DEPENDENCIES, RESEARCH, OPEN QUESTIONS] Ask up to 3 clarifying questions only if a required input is missing. Do not invent dates, staffing, approvals, estimates, or dependencies. Mark unknowns as assumptions or open questions. Produce: 1. A project charter with objective, measurable success criteria, deliverables, and exclusions. 2. A milestone table with outcome, owner, timing, entry criteria, exit criteria, and dependencies. Sequence alignment, preparation, execution, review, launch or handoff, and retrospective as relevant. 3. Tasks under each milestone, small enough to track. Show accountable owner, contributors, predecessor, estimated effort only where supported, and completion evidence. 4. A decision list showing who recommends, approves, executes, and is informed. 5. A risk register with trigger, likelihood, impact, mitigation, contingency, owner, and reassessment date. 6. First-week actions: meetings, decisions, and work needed to protect the critical path. Self-check: flag tasks without one owner, deadlines that precede dependencies, and success measures that cannot be observed. Separate deliverables from activities. End with the three assumptions most likely to change the plan.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [PROJECT NAME] | Enter the short project name. | Customer onboarding email refresh |
| [PROJECT GOAL] | Describe the problem, intended outcome, and relevant background. | Improve trial-to-paid conversion during the first 14 days. |
| [DELIVERABLES AND EXCLUSIONS] | List what the project must produce and what is outside scope. | Five emails, trigger map, copy, QA, and launch report; no product redesign. |
| [PEOPLE, ROLES, CAPACITY, AND APPROVER] | Name team members, their roles and availability, and the final decision maker. | Maya, lifecycle marketer, 12 hours weekly; Priya, designer; Jordan, engineering approver; VP Growth approves messaging. |
| [DEADLINE, BUDGET, FIXED DATES, RISKS] | Provide fixed constraints, important dates, budget limits, and known risks. | Launch by October 28; no external budget; analytics event tracking may be incomplete. |
| [REQUIREMENTS, DEPENDENCIES, RESEARCH, OPEN QUESTIONS] | Paste existing requirements, linked work, research, and unanswered questions. | July funnel analysis, current email exports, approved positioning, and analytics validation of activation events. |
How to use
- Replace every bracketed field with project facts and constraints.
- Paste existing requirements and name the actual approver.
- Check each task has a single owner and verifiable completion evidence.
- Then ask: “Turn this into a weekly status update with red, amber, and green rules.”
Variations
Kickoff agenda
Use this before the team’s first execution meeting.
Create a 60-minute kickoff agenda for [PROJECT] with [ATTENDEES], based on [GOAL AND SCOPE]. Include time-boxed sections for outcome, scope boundaries, roles, milestones, dependencies, risks, and decisions. For each section, state the decision or artifact we must leave with and its owner. Finish with a decision log and actions due in the next five business days. Ask up to 3 questions only if required information is missing; do not invent commitments.
Recovery plan
Use this when a project is late or blocked.
Build a recovery plan for [PROJECT], which is behind because [CURRENT PROBLEM]. The deadline is [DEADLINE], capacity is [TEAM AND CAPACITY], and remaining work is [STATUS AND WORK]. Show what is complete, blocked, descoped, resequenced, or needs escalation. Provide options with tradeoffs and a two-week action plan. Flag any deadline that cannot be met with the stated capacity; do not invent estimates.
Executive brief
Use this when leadership needs a concise decision-ready update.
Write a one-page executive brief for [PROJECT] aimed at [AUDIENCE]. Use [GOAL AND SCOPE], [TIMELINE], and [RISKS OR DECISIONS NEEDED]. Include objective, success measures, delivery timing, dependencies, top risks, and the exact support requested. Keep it under 500 words. Do not claim benefits, dates, or certainty absent from my notes. Flag unsupported statements.
Tips
- Define completion evidence before assigning a date; “draft approved by legal” is clearer than “legal review.”
- Assign one accountable person per task even where several people contribute.
- Treat approvals, data access, and feedback cycles as dated dependencies, not footnotes.
- Use relative timing until the start date is confirmed, then convert it to calendar dates.
FAQ
Can AI estimate a project timeline?
It can suggest sequencing and expose missing dependencies, but owners must validate estimates.
How detailed should the plan be?
Tasks should be small enough to assign, track, and verify without daily interpretation.
Do I need a separate risk register?
For meaningful uncertainty, yes. It keeps triggers, mitigations, and owners visible.