AI prompts for project planning: 8 you can copy

The difference between an AI assistant that wastes your time and one that keeps your plan honest is usually the prompt. "Make me a project plan" gets you a generic list. A prompt that names the project, the start date, the constraints and the output you expect gets you something you can actually use. This guide gives you eight AI prompts for project planning that you can copy and adapt, plus a simple recipe for writing your own.

The examples assume your assistant is connected to your Gantt chart through MCP, so it can read and edit the real plan instead of just writing text in a chat. If you have not connected it yet, the connector docs cover Claude, ChatGPT, Codex, Cursor, VS Code and other clients. The principles work in any chat, though.

What makes a planning prompt work

A good prompt answers four questions before the assistant has to guess.

• What is the project? Name it, and say where it lives. "In my Website relaunch project" is better than "in my plan".
• What exactly should change? One clear action: create, move, mark, assign, report.
• What are the constraints? A start date, a deadline, a team size, tasks that cannot overlap.
• What do you want back? A changed plan, a short summary, a list of risks, or a proposal to approve first.

Two habits save the most trouble. First, always give an explicit start date when you ask for a new plan. Tasks created through the ProGantt connector without one start today, which may not be what you meant. Second, ask for a proposal before any change you would be unhappy to undo. The assistant can show you what it intends to do, and you say yes or no.

Prompts for building a plan

1. Draft a plan from a short description

Create a ProGantt project called "Podcast launch" and draft the plan. Phases: concept, recording, editing, publishing. Start on Monday 16 November. One person does all the work, so avoid parallel tasks. Add realistic durations and dependencies, and a milestone called "First episode live".

This works because it gives the assistant a structure (four phases), a constraint (one person) and a deliverable (a milestone). The result is a first draft: phases become task groups, the work inside them becomes subtasks, and the order of work becomes dependencies. If you want the theory behind that structure, see subtasks and task groups.

2. Turn a messy list into a schedule

Here is my to-do list for the office move: book movers, notify the landlord, order new desks, pack the kitchen, set up internet at the new office, update our address with clients. Put them in a new ProGantt project, group them sensibly, estimate durations and link the ones that depend on each other. Ask me before you assume anything unusual.

Pasting a rough list is often the fastest way to start. The last sentence matters: it invites questions instead of silent guesses.

3. Check a plan you already wrote

Read my "Office move" project and review it. Are any dependencies missing, any tasks without a duration that looks realistic, or any milestones with no work leading to them? List problems only; do not change anything yet.

Asking for a review without edits is a safe way to use an assistant on a plan you care about. For a manual version of the same check, see how to create a project schedule.

Prompts for keeping the plan current

4. Absorb a delay

In "Podcast launch", editing is running five days late. Move it and everything that depends on it back by 5 days, then tell me the new date of "First episode live" and whether it still meets my 4 December target.

This is where an assistant earns its keep. It follows the dependency links instead of guessing which tasks feel related, and it answers the question you actually care about: does the deadline survive? For a human approach to the same problem, read how to handle project delays.

5. Update progress in plain language

Mark "Record episode 1" as complete, set "Edit episode 1" to 30% done, and add a note to it saying the intro music is still pending.

You describe what happened, the assistant makes the edits. Several changes to one task can be applied together, so you do not need to spell out every click.

6. Prepare a status update

Look at "Podcast launch" and write a five-line status update for my co-host: what is done, what is in progress, what is late, what is next, and one risk. Use only what is in the plan.

"Use only what is in the plan" keeps the summary grounded in the chart rather than in the assistant's imagination. You can read more about this routine in writing a project status update from a Gantt chart.

Prompts for questions and workload

7. Ask what blocks a milestone

What still has to finish before "First episode live" can happen? Show the chain in order.

Reading a plan and explaining it is often more useful than editing it. You get the answer in seconds instead of tracing arrows across the chart. If the answer surprises you, it is worth looking at the critical path.

8. Check who is overloaded

Over the next two weeks, who has the most work in the "Office move" project? Suggest a rebalancing, but wait for my approval before changing any assignments.

For this to work, tasks need people assigned to them. The assistant can report the number of tasks and person-days per person in a date window, then propose reassignments. Whether the proposal is sensible is your call: you know who is on holiday, who is learning something new, and who works best alone.

Writing your own prompts

When you need a prompt that is not on this list, use a simple template:

1. Context: which project, and which tasks if you know them.
2. Action: one verb, such as create, move, mark, assign, list.
3. Constraint: dates, people, order.
4. Output: change it now, or propose first.

For example: "In [project], move [task] to start on [date]. Keep the dependencies intact and tell me what else shifts. Propose first."

Short, specific and boring beats long and clever. If a prompt does not give the result you wanted, change one part of it and try again, rather than rewriting everything.

What not to hand over

Prompts make an assistant fast, not wise. Keep these decisions for yourself:

• The commitment to a date. The assistant can estimate durations; you are the one promising them to a client. Review estimates against what you know of your team. Our guide to estimating task duration helps.
• Scope and priority. Deciding what to cut when time runs out is a business decision.
• Deletions. Deleting tasks, milestones, people and tags cannot be undone. Read what is about to go before you approve it.
• Conversations with people. The plan can say someone is overloaded; only you can talk to them.

Access follows your roles. If you are only a viewer on a shared project, the assistant can read it but cannot change it, which is a useful safety net when you share a plan with a client.

Try it on a small plan first

Pick a project you already know well, open it in the ProGantt editor, and run prompt 7 or 8 first. They only read your plan, so there is nothing to undo. Once you trust how the assistant reads the chart, move on to updates and drafting. For a fuller walkthrough of the setup and the division of labour, see how to manage a project plan with Claude.