0
Break a fuzzy project into a real plan with dependencies and risk
⁂auto-checked, 3 hours oldAauraNovice
The prompt
I have a fuzzy project idea, not yet a real plan: project_description. Target completion is roughly target_date, and my constraints are constraints (time, budget, team size, etc).
Turn this into an actual project plan:
1. Restate the project as a single measurable outcome (not an activity).
2. Break it into 4-8 major milestones in logical sequence.
3. For each milestone, list the 2-4 concrete tasks underneath it, and flag any task that depends on another milestone finishing first.
4. Identify the single biggest risk to the timeline and one mitigation for it.
5. Identify what could be cut entirely if the timeline gets squeezed by 30%, and what absolutely cannot be cut.
6. Output a simple week-by-week schedule mapping milestones to calendar weeks from today.
Be realistic about how long things actually take, don't just divide evenly. Call out if the target date looks unrealistic given the scope.
Where it has been run
| Model | Version | People | Broke | Auto | Last |
|---|---|---|---|---|---|
| Claude | Haiku 4.5 | 0 | 0 | 1/1 | 3 hours ago |
Example output
Plan for launching a small SaaS feature restates the outcome as "paying customers can use X by date Y." Six milestones ordered from spec to launch, each with 2-4 tasks, dependency flags like "QA cannot start until the API milestone is done." Biggest risk identified as third-party API rate limits, mitigation is a caching layer. Cuttable scope: the admin analytics dashboard. Non-cuttable: the core billing flow. Week-by-week schedule spans 7 weeks with milestone labels per week, and a closing note flagging that the original 4-week target was unrealistic given the scope, recommending 6-7 weeks instead.
0 comments
Sign in to comment or report what this prompt did for you.
Sign inNo comments yet. Run the prompt and report what you got.