Assemble a project kickoff brief from rough notes
Turn messy planning notes into a structured kickoff brief — scope, non-goals, roles, risks and milestones — ready to send before the first meeting.
Last updated
Fill in the blanks
Assembled in your browser — nothing you type is stored or sent anywhere.
Your prompt
Model-agnostic — works in Claude, ChatGPT, Gemini or any AI chat.
Why this prompt works
- →Naming five fixed headings, including Non-goals, forces the model to surface scope boundaries explicitly — the section most kickoff docs skip and the one that later prevents the most scope-creep arguments.
- →Restricting Roles to names or teams that actually appear in the notes stops the model from inventing an owner for scope that the notes never assigned to anyone.
- →The "not yet defined" fallback for missing owners and dates turns silent gaps in the notes into visible gaps in the brief, which is what lets the reader catch them before the kickoff meeting instead of after.
Part by part
- Non-goals (what it explicitly will not cover, to prevent scope creep)
- The most valuable heading and the one nobody writes unprompted. Scope creep enters through things that were never ruled out rather than through things that were.
- using only names or teams mentioned in the notes
- Stops the model assigning owners. An invented owner in a kickoff brief is read as a decision, and the named person finds out later.
- with dates only where one was actually given
- Same problem for the timeline. A plausible date in a brief becomes a commitment the moment it is circulated.
- not yet defined
- An explicit placeholder, so gaps are visible rather than filled. A brief with three of these is more honest and more useful than one that reads complete.
Common mistakes
Write a project kickoff brief for this project.Every section gets filled, including owners and dates nobody supplied. The document then circulates as though those were agreed, which is how a brief creates commitments rather than recording them.
Turn these notes into a project plan.A plan implies sequencing and dependencies that the notes rarely support. A kickoff brief records what is known and what is not, which is a smaller and more honest claim.
Write a kickoff brief and fill in reasonable defaults.Reasonable defaults are indistinguishable from decisions once the document is shared. The value of the placeholder is that it prompts the conversation the default would have skipped.
Questions
Why are non-goals so important?
Because scope creep arrives as reasonable additions. A written non-goal turns "could we also" into a change of scope requiring a decision, rather than a small favour absorbed silently.
What if I do not know who owns something yet?
Leave it as not yet defined. An unassigned piece of scope is a visible risk; a wrongly assigned one is invisible until the person who did not know they owned it fails to deliver it.
How detailed should milestones be?
Enough to tell whether the project is on track, which usually means three to six. Weekly milestones become a status report nobody updates, and two milestones cannot detect drift until it is too late.
Does this replace a proper planning session?
No, it prepares for one. Arriving with a draft where the gaps are marked makes the meeting about the gaps, which is a much better use of everyone's time than assembling structure in the room.