Create a project plan with a work breakdown and schedule
WBS, milestones, dependencies, resources, and a realistic timeline.
The prompt
Role: Act as a project manager building the WBS and schedule.
Context: Scope and deliverables: [SCOPE_DELIVERABLES]. Known constraints (fixed dates, resource availability, external dependencies): [CONSTRAINTS]. Team and skills available: [TEAM]. Estimating basis / any historical data: [ESTIMATING_BASIS]. Methodology (predictive / agile / hybrid): [METHODOLOGY]. Risk areas: [RISK_AREAS].
Task: Produce: (1) a WBS decomposing each deliverable to work-package level with a one-line definition of done for each; (2) rough effort and duration per work package with the estimating assumption; (3) the dependency map and the resulting phased schedule with milestones; (4) the critical path and the work packages with the least float; (5) where the schedule is most fragile and the buffer or fast-track options.
Format: Sections: WBS (indented, with DoD) | Estimates (table) | Dependencies & schedule (phases + milestones) | Critical path & low-float items | Schedule risks & options. ~550 words.
Verification: Flag every estimate that lacks a basis and every dependency without a confirmed date; note where the WBS may be incomplete.
Validation: Pressure-test the critical path: if the two riskiest work packages slip by 20%, what is the end-date impact and the earliest mitigation? State it.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- SCOPE_DELIVERABLES
- CONSTRAINTS
- TEAM
- ESTIMATING_BASIS
- METHODOLOGY
- RISK_AREAS
How this prompt is built
This prompt follows the RCTFVV structure (Role, Context, Task, Format, Verification, Validation). RCTFVV extends RCTF with two checking steps. Verification asks the model to review its own draft against your requirements; Validation asks it to flag assumptions and gaps you should confirm.
Related prompts
- Write a project charterDefines a project's purpose, scope, objectives, stakeholders, and success criteria.
- Build a RAID log (risks, assumptions, issues, dependencies)Captures and tracks the risks, assumptions, issues, and dependencies on a project.
- Create a risk register with mitigationsIdentifies, scores, and plans responses to project or business risks.
- Assess the impact of a change requestEvaluates a scope change's impact on time, cost, quality, and risk.