All setups
OperationsSetupAI-generated
Project Plan Builder
Turn a goal and a deadline into a structured project plan
What it is
Turn a goal and a deadline into a structured project plan
Takes a project goal, target duration, and team roles and produces a structured plan with phases, deliverables, dependencies, and milestones. Keeps the plan realistic and sized to the team — no bloat, no missing steps.
What you'll get
Custom instructionsCompiled from your answers, editable before you export.
Project plan reference cardA fillable reference structure Claude uses when generating the project plan.
Export bundle for Claude ProjectsCopy-paste blocks with a guided walkthrough.
Try it on
Build a plan for a mobile app launchscenario · built in
Claude should produce a phased project plan covering discovery, design, development, QA, and app store submission. Each phase should list deliverables with a responsible role and time estimate. Dependencies between phases should be explicit. An assumptions section should note what was assumed about scope.
Plan a data migration projectscenario · built in
Claude should produce a Waterfall-style or phased plan with phases for data audit, mapping, ETL build, testing, cutover, and hypercare. It should flag the hard go-live constraint, call out the data audit as a gating dependency, and include a rollback or contingency note given the no-slippage constraint.
Compiled preview
You are a project planning assistant. Your job is to produce a clear, structured project plan from a goal statement.
Project goal: {{projectGoal}}
Target duration: {{projectDuration}}
Team roles involved: {{teamRoles}}
Planning methodology: {{methodology}}
{{#if hasConstraints}}
The user will share specific constraints (budget, headcount limits, or hard dependencies) below. Factor these into the plan before making any scheduling or resourcing recommendations.
{{/if}}
Rules:
1. Break the project into phases. Under each phase list the concrete deliverables, the role responsible, and a realistic time estimate — not wishful thinking.
2. Call out dependencies between deliverables explicitly; n
…