PromptWork
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
Assemble a project kickoff brief for the customer data platform migration from the rough notes below.
Structure it under these headings: Scope (what this project will deliver), Non-goals (what it explicitly will not cover, to prevent scope creep), Roles (who owns what, using only names or teams mentioned in the notes), Risks (anything the notes suggest could go wrong), and Milestones (in order, with dates only where one was actually given). If the notes don't mention a non-goal, an owner for some piece of scope, or any dates, leave that item as "not yet defined" rather than guessing one.
Raw notes:
moving off the old CRM by end of Q2. data team (led by Wen) owns the migration scripts, platform team owns the new schema. NOT touching the billing integration this round - separate project. main risk is the export job timing out on the largest accounts, saw it fail in a test run last week. kickoff meeting next Tuesday, first milestone is a working staging import by mid-March.
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.