Back to Discover

#raci

1 prompt found

Project Plan Prompt: Scope, WBS, Timeline, RACI, and Risks
⚡ Productivity

Project Plan Prompt: Scope, WBS, Timeline, RACI, and Risks

Ppromptstudio·Oct 10, 2026
No rating

Turn a short project brief into a full project plan: scope and out of scope, a work breakdown, a dated timeline with dependencies, a RACI chart, and a risk log.

Act as an experienced project manager who turns a short project brief into a plan a small team can start on Monday, using only the dates, people, and budget in the brief. Inputs: - What the project must achieve and how we will know it is done: [ProjectGoal] - The deliverables the sponsor expects: [Deliverables] - Start date, hard deadline, and any blackout dates: [KeyDates] - Team members, their roles, and how much time each can give: [Team] - Budget and what it must cover: [Budget] - Outside vendors, approvals, or dependencies we already know about: [Dependencies] - Stakeholders who need updates and how often: [Stakeholders] - Anything out of scope or already decided: [ScopeLimits] Generate: 1. A project charter block: goal, success criteria, sponsor, in scope, and out of scope from ScopeLimits. 2. A work breakdown structure: phases, then work packages under each phase, then tasks, numbered 1.1, 1.2, and so on, every task with an owner from Team. 3. A dated timeline table: task, owner, start, finish, duration, and the task it depends on. Work backward from the deadline in KeyDates and show the critical path. 4. A milestone list with a clear done test for each milestone. 5. A RACI chart for the main work packages, with exactly one Accountable per row. 6. A risk log of 6 to 8 risks: cause, impact, likelihood (low, medium, high), owner, and the response, including Dependencies. 7. A budget check: list each cost the plan needs against Budget, marking unknown amounts as [GET QUOTE]. 8. A communication plan for Stakeholders: who gets what update, how, and how often. 9. A schedule warning list: any task where an owner is booked beyond the time given in Team, or where the deadline leaves no buffer. Rules: - Do not invent team members, vendors, prices, or dates. - Leave at least one week of buffer before the deadline and say where it sits.