Prompt library

Work · AI Prompt

Create a Project Plan From a Goal

Turn a goal into phases, deliverables, dependencies, milestones, risks, questions, and a first-action checklist.

Goal + constraints → project-plan prompt → explicit AI handoff

Runs in this browser. No upload by this page. Copy/download/export locally. External AI handoff is explicit. Review before sharing.

Prompt workbenchConfigure → review → use
01

Set project goal

Setup
Describe the outcome you want, known deadlines or resources, and any constraints or assumptions the plan must respect.
Prompt style
Try an example goal

What you’ll need

    What you’ll get

      02

      Prompt preview

      Editable

      Review or edit the generated prompt before you copy it or explicitly open an AI chat.

      Export

      ChatGPT opens with the current prompt prepared. Gemini copies the current prompt to your clipboard, then opens Gemini so you can paste it into the chat. Do not place secrets or sensitive information in URL-carried prompts. Provide the goal and constraints to the AI service only after you choose where to use the prompt.

      About this AI promptHow it works, what to include, examples, limits, and related prompts.

      What this AI prompt does

      This builder turns a stated goal into a planning prompt that asks an AI assistant to organize the work into phases, deliverables, milestones, dependencies, risks, open questions, and an actionable starting sequence.

      The useful output is not a pretend project schedule. It is a structured planning draft that makes assumptions visible, distinguishes known constraints from unresolved decisions, and gives you a concrete basis for assigning owners and dates.

      When to use it

      • Translate a broad outcome such as launching a site, producing a campaign, migrating a system, or organizing an event into manageable work.
      • Create a first planning draft before a kickoff meeting so the team can challenge scope, sequence, and dependencies.
      • Recover structure when a project has a goal but no clear milestones, deliverables, or first-week actions.
      • Compare a proposed plan against real staffing, approval, budget, or timing constraints before committing to a schedule.

      What to include for better results

      A project plan becomes more realistic when the prompt receives constraints instead of only a desired outcome. Include what is already known and explicitly label what is still unknown.

      • State the goal in observable terms: what should exist or be true when the project is complete.
      • Add the deadline, available people, budget, tools, approvals, and non-negotiable constraints when they are known.
      • Identify dependencies or external parties that can block progress, even if ownership is not resolved yet.
      • Tell the AI whether you need a lightweight execution plan, a detailed work breakdown, or a decision-ready planning brief.

      Worked example

      Goal: Launch a new help center in six weeks using existing documentation, one editor, subject-matter reviewers, and a fixed launch date.

      Planning need: Protect the deadline, expose dependencies, and make the first week of work obvious without inventing owners or approvals.

      Expected result: Assumptions, phases, deliverables, milestone sequence, dependencies, risks, open ownership questions, and a first-week checklist.

      How the prompt stays grounded

      The generated prompt should treat dates, resources, budgets, approvals, and owners as facts only when you supply them. Unknowns should remain questions or assumptions rather than being filled with plausible-sounding project details.

      A sequence can be logically useful without being operationally possible. Before execution, check capacity, lead times, legal or procurement gates, technical dependencies, and stakeholder availability against the real environment.

      Limitations

      • An AI-generated plan cannot know hidden dependencies, team capacity, organizational politics, procurement lead times, or approval requirements that were not provided.
      • Estimated effort and dates are planning hypotheses unless they are grounded in real historical data or team estimates.
      • A neat phase structure can hide uncertainty. Preserve unresolved questions instead of forcing every item into a confident schedule.

      Common questions

      Can this create a full project schedule?

      It can draft a schedule structure, but dates and effort should be treated as provisional unless you provide real constraints and estimates. Validate timing with the people doing the work.

      What if I do not know the owners yet?

      Leave ownership unresolved. Ask the AI to flag roles or decisions that need an owner rather than assigning a person who was never specified.

      Should I use this for a small project?

      Yes. For a small project, choose a concise output and ask for phases, dependencies, risks, and immediate next actions instead of a large work breakdown.

      Can the plan change after kickoff?

      It should. A useful plan is a working model. Update it when scope, evidence, capacity, dependencies, or decisions change.

      Use a neighboring Builder when the job changes materially rather than stretching this prompt beyond its intended task.

      Plan Project Risks and MitigationsTurn Instructions Into a ChecklistRun a Post-Project ReviewCreate a Project Status Update

      Privacy and handoff

      This page builds the planning prompt locally in your browser. It does not send your project notes, constraints, or plans to Mycelgrid servers or an AI model automatically.

      If the project contains confidential client, employee, security, financial, or roadmap information, review the prompt before using an external AI service and share only what that service is authorized to receive.