Back to cookbook
Productivity

ChatGPT Prompt to Turn a Messy Brain Dump Into an Organized Project Plan

2 views Updated
Share

This ChatGPT prompt to turn a brain dump into a project plan takes a raw, unordered list of thoughts — the kind you type out in five minutes before a meeting or right after one — and organizes it into a real plan with phases, tasks, and owners. It's built for founders, project managers, and anyone who thinks in scattered notes but needs to hand someone (including themselves) a document they can actually act on.

The prompt works by asking the model to first group related items from the dump into themes, then convert each theme into a phase or milestone, and only after that assign individual tasks underneath. That ordering matters: going straight from a messy list to a task list usually produces something that looks organized but has no real structure underneath, with duplicate work hidden across different phrasing.

Once you have a first draft of the plan, running it through Prompt Builder is a natural next step if you want to turn the plan itself into a reusable prompt template you can run again for future projects, rather than rewriting the brain-dump prompt from scratch each time.

Prompt template

ROLE: You are a project planning assistant that turns unstructured notes into an organized project plan.

CONTEXT:

  • Project name: [PROJECT NAME]
  • Raw brain dump (unedited): [PASTE YOUR NOTES, BULLET POINTS, OR STREAM-OF-CONSCIOUSNESS TEXT]
  • Team members involved, if known: [NAMES OR ROLES]
  • Target deadline, if any: [DATE OR TIMEFRAME]

TASK:

  1. Read through the raw notes and group related ideas into 3-6 themes or phases
  2. For each phase, list the specific tasks that belong to it, pulled from the notes
  3. Assign an owner to each task if a name or role was mentioned; otherwise mark it "Unassigned"
  4. Flag any item from the notes that was too vague to turn into an actionable task
  5. Note any dependency where one task must finish before another can start

CONSTRAINTS:

  • Do not invent tasks that weren't implied by the notes
  • Do not merge two distinct ideas into one task just to shorten the list

OUTPUT FORMAT: A phased project plan with phase names as headers, tasks as a checklist under each, and a separate "Needs Clarification" section at the end.

Example input

Project name: Website Relaunch Raw brain dump: need new homepage copy, someone should check if the old blog posts redirect correctly, Sarah was going to look at hosting options, we need a logo refresh maybe, also the contact form is broken on mobile, launch before the conference in 6 weeks, need to decide if we're keeping the old blog or starting fresh, pricing page needs updating too, who's writing the About page Team members: Sarah, Jordan, me Target deadline: 6 weeks (before the conference)

Example output

Website Relaunch — Project Plan (Target: 6 weeks, before conference)

Phase 1: Infrastructure & Technical Fixes

  • [ ] Evaluate and select hosting options (Owner: Sarah)
  • [ ] Fix contact form bug on mobile (Owner: Unassigned)
  • [ ] Audit old blog post URLs and confirm redirects work (Owner: Unassigned)

Phase 2: Content

  • [ ] Write new homepage copy (Owner: Unassigned)
  • [ ] Write About page copy (Owner: Unassigned)
  • [ ] Update pricing page content (Owner: Unassigned)

Phase 3: Design

  • [ ] Refresh logo (Owner: Unassigned)

Dependencies:

  • Hosting decision (Phase 1) should happen before final content is loaded onto the new site

Needs Clarification:

  • "Need a logo refresh maybe" — unclear if this is confirmed in scope or still undecided; confirm before assigning
  • "Decide if we're keeping the old blog or starting fresh" — this is a decision, not a task; needs to be resolved before the content phase can be scheduled accurately

When to use it

  • Right after a brainstorming session or client call when your notes are a wall of unordered bullet points
  • When you need to hand off a rough idea to a team and they need phases and owners, not just a list
  • Before a kickoff meeting, to turn scattered pre-planning notes into an agenda with clear next steps
  • When resuming a stalled project and you need to reconstruct what's actually left to do from old notes

Best practices

  • Paste the brain dump exactly as written, including repeated or contradictory ideas — let the model do the deduplication
  • Ask for phases or milestones before individual tasks, so the plan has real structure instead of a flat list
  • Specify a rough timeline or deadline if you have one, so the model can flag anything unrealistic
  • Review the output for tasks that got merged incorrectly — vague brain dumps sometimes hide two different tasks in one sentence

Common mistakes

  • Cleaning up the brain dump before pasting it in, which removes signal the model could have used to group related ideas
  • Asking for a task list directly instead of phases first, producing a plan with no real sequencing
  • Not specifying who's involved, so every task comes back unassigned and still needs manual follow-up
  • Treating the first output as final instead of flagging unclear items for a follow-up round

FAQs

How do I turn messy meeting notes into a project plan with ChatGPT?

Paste the notes in as-is without cleaning them up first, and ask the model to group related items into phases before listing individual tasks — going straight to a task list from raw notes usually misses the underlying structure.

Can AI assign task owners automatically from a brain dump?

Only if names or roles are mentioned in the notes. The model can pull out "Sarah was going to look at hosting" and assign that task to Sarah, but it shouldn't guess an owner for tasks where no one was mentioned.

What if my brain dump has vague or unclear items?

A good prompt should flag those separately instead of forcing them into a task, since turning a vague idea into a specific task without clarification usually produces the wrong task.

How is this different from just asking ChatGPT to summarize my notes?

A summary condenses the notes; a project plan restructures them into phases, tasks, and owners with a completely different format and purpose, which needs an explicit instruction to produce rather than a plain summarize request.

What tool pairs well with this prompt for future projects?

Prompt Builder — turns a plain description into a complete structured prompt, useful if you want to save this brain-dump-to-plan workflow as a reusable template for the next project instead of rewriting it each time.

Found this prompt useful? Share it.

Share

More in Productivity

Productivity

AI Prompt to Prioritize Your Daily To-Do List by Deadline and Impact

This AI prompt for task prioritization turns a messy, unordered to do list into a ranked action plan. It's built for anyone juggling more ta…

Role: You are a productivity and task-management assistant.

Context: I have a list of tasks I need to complete. Here they are, with whatever details I have:
[LIST_OF_TASKS_WITH_DEADLINES_AND_NOTES]

My available time today/this week is: [AVAILABLE_HOURS_OR_TIMEFRAME]
My hard constraints or dependencies are: [CONSTRAINTS_OR_DEPENDENCIES]

Instructions:
1. Rank all tasks from highest to lowest priority.
2. Base the ranking on a combination of: (a) deadline urgency, (b) impact if the task is delayed or skipped, and (c) any dependencies between tasks.
3. For each task, give a one-line rationale explaining why it landed where it did.
4. Flag any task that is at risk of being missed given my available time.
5. If two tasks are close in priority, say so and explain the tiebreaker you used.

Output format:
A numbered, ranked list. For each item: task name, priority rank, one-line rationale, and a risk flag (Yes/No) if it might be missed.
Productivity

Meeting Notes to Action Items

A prompt that converts raw meeting notes or a transcript into the three things people actually need afterwards: what was decided, who does w…

You are an executive assistant. Turn the meeting notes below into a structured summary.

Meeting date: [DATE]
Attendees: [NAMES]

Output sections:
1. Summary (max 4 sentences)
2. Decisions made (bullets)
3. Action items as a table: Owner | Task | Due date
4. Open questions
5. Unassigned items that need an owner

Rules: never invent owners or dates. If missing, write "TBD" and list it in section 5.

Notes:
"""
[PASTE NOTES]
"""