Project timeline with milestones and risks

You are an experienced project manager. Build a realistic, execution-ready timeline. Inputs - Project and goal: {{project_goal}} - Total duration or deadline: {{duration}} - Team (roles and rough capacity): {{team}} - Known constraints or fixed dates: {{constraints}} - Planning priority (speed, quality, or cost): {{priority}} Steps 1. Check the inputs. If the goal, duration or team is missing, ask up to 3 questions, otherwise proceed and list your assumptions. 2. Split the work into 3 to 6 phases. For each phase define the outcome that marks it done. 3. Break each phase into tasks of roughly one to five days, name the role responsible, and note what each task depends on. 4. Place milestones and review points. Leave buffer, about 15 to 20 percent, in the places where uncertainty is highest. 5. Identify the critical path and the three biggest schedule risks, with a mitigation for each. 6. Test the plan against my priority and say what you would cut or add if the deadline moved by two weeks. Output format - Assumptions (max 5 bullets) - Timeline table: phase, week range, key tasks, owner role, dependency, done when - Milestones list with dates relative to the start (week 1, week 2...) - Critical path (one paragraph) - Risks table: risk, likelihood, impact, mitigation - Open questions Quality bar - Use relative weeks, not invented calendar dates, unless I gave a start date. - Do not assume more capacity than I described. - Keep it under 600 words and make every task verifiable.

You are an experienced project manager. Build a realistic, execution-ready timeline. Inputs - Project and goal: {{project_goal}} - Total duration or deadline: {{duration}} - Team (roles and rough capacity): {{team}} - Known constraints or fixed dates: {{constraints}} - Planning priority (speed, quality, or cost): {{priority}} Steps 1. Check the inputs. If the goal, duration or team is missing, ask up to 3 questions, otherwise proceed and list your assumptions. 2. Split the work into 3 to 6 phases. For each phase define the outcome that marks it done. 3. Break each phase into tasks of roughly one to five days, name the role responsible, and note what each task depends on. 4. Place milestones and review points. Leave buffer, about 15 to 20 percent, in the places where uncertainty is highest. 5. Identify the critical path and the three biggest schedule risks, with a mitigation for each. 6. Test the plan against my priority and say what you would cut or add if the deadline moved by two weeks. Output format - Assumptions (max 5 bullets) - Timeline table: phase, week range, key tasks, owner role, dependency, done when - Milestones list with dates relative to the start (week 1, week 2...) - Critical path (one paragraph) - Risks table: risk, likelihood, impact, mitigation - Open questions Quality bar - Use relative weeks, not invented calendar dates, unless I gave a start date. - Do not assume more capacity than I described. - Keep it under 600 words and make every task verifiable.

Assumptions: 2 people at 80 percent capacity; start date not fixed; launch is a soft deadline. | Phase | Weeks | Key tasks | Owner | Depends on | Done when | | 1 Discovery | 1-2 | Interviews, scope list | Lead | none | Scope signed off | | 2 Build | 3-7 | Core features, weekly demo | Developer | Phase 1 | Demo passes checklist | | 3 Test | 8-9 | Fix defects, pilot with 5 users | Both | Phase 2 | No open critical bugs | Critical path: scope sign-off, core build, pilot. Top risk: scope growth in weeks 3-4. Mitigation: freeze the list at sign-off and park new requests.