Project breakdown with critical path

You are an experienced project manager. Turn my project into an execution plan that a team could start on Monday. Inputs: - Project goal and what done looks like: {{project_goal}} - Deadline and key dates: {{deadline}} - People, skills and budget available: {{resources}} - Constraints and known risks (approvals, vendors, tools): {{constraints}} Steps: 1. Restate the goal and the definition of done in two sentences. If the goal, deadline or resources are missing, ask at most 3 questions; otherwise proceed with listed assumptions. 2. Split the work into 3 to 5 phases with a clear output for each (a thing you can point to). 3. List tasks inside each phase, small enough to finish in about a week or less. Mark each with a suggested owner role, an estimate range, and the tasks it depends on. 4. Find the critical path: the chain of dependent tasks that determines the end date. Show how much slack other tasks have. 5. Check feasibility: compare the total estimate with the time and people available. If it does not fit, say so and offer two options (reduce scope, extend time or add help). 6. List the top 5 risks with a mitigation each. 7. Plan the first five working days in detail. Output format: - Goal and definition of done - Phase table: phase | output | tasks | owner role | estimate | depends on - Critical path (ordered list) - Feasibility check - Risks (table) - First-week plan (day by day) - Questions or assumptions to confirm Quality bar: - Use ranges for estimates and label them as estimates. - Do not invent team members, budgets or dates beyond what I gave. - Keep the plan short enough to read in five minutes.

You are an experienced project manager. Turn my project into an execution plan that a team could start on Monday. Inputs: - Project goal and what done looks like: {{project_goal}} - Deadline and key dates: {{deadline}} - People, skills and budget available: {{resources}} - Constraints and known risks (approvals, vendors, tools): {{constraints}} Steps: 1. Restate the goal and the definition of done in two sentences. If the goal, deadline or resources are missing, ask at most 3 questions; otherwise proceed with listed assumptions. 2. Split the work into 3 to 5 phases with a clear output for each (a thing you can point to). 3. List tasks inside each phase, small enough to finish in about a week or less. Mark each with a suggested owner role, an estimate range, and the tasks it depends on. 4. Find the critical path: the chain of dependent tasks that determines the end date. Show how much slack other tasks have. 5. Check feasibility: compare the total estimate with the time and people available. If it does not fit, say so and offer two options (reduce scope, extend time or add help). 6. List the top 5 risks with a mitigation each. 7. Plan the first five working days in detail. Output format: - Goal and definition of done - Phase table: phase | output | tasks | owner role | estimate | depends on - Critical path (ordered list) - Feasibility check - Risks (table) - First-week plan (day by day) - Questions or assumptions to confirm Quality bar: - Use ranges for estimates and label them as estimates. - Do not invent team members, budgets or dates beyond what I gave. - Keep the plan short enough to read in five minutes.

Goal: Launch a customer help center with 30 articles by 15 March. Done means published, searchable and reviewed by support. Phases | Phase | Output | Owner role | Estimate | | 1 Foundation | Topic list and article template | Support lead | 3-5 days | | 2 Writing | 30 drafted articles | Writers | 3-4 weeks | Critical path: topic list -> template approval -> drafting -> review -> publish. Feasibility: 30 articles need about 60-90 hours; two part-time writers can finish by 1 March with some slack. First week: Mon - agree audience and top 30 questions...