The prompt
Score 10 of 10, Excellent
Use it when You need the kickoff agenda, roles, ground rules and first actions for a new project.
- {{project_summary}}
- {{attendees}}
- {{meeting_length}}
- {{meeting_format}}
- {{kickoff_goals}}
- {{concerns}}
Full prompt and why it works
Prompt
Project summary or charter: """ {{project_summary}} """ Who will attend, with their roles: {{attendees}} Meeting length: {{meeting_length}} In person or remote: {{meeting_format}} What I most need from this meeting: {{kickoff_goals}} Known concerns or tensions: {{concerns}} Task: Plan a kickoff meeting for this project. The purpose is to leave with a shared understanding of the goal, the scope and who does what, with concerns raised early and first actions agreed. It is a working session for the people who will do the work, not a presentation. Format: 1. Desired outcomes: three to five things that will be true at the end of the meeting. 2. Before the meeting: what to send, when, and any short pre-work. 3. Agenda: a table with the columns Time, Item, Lead, Purpose, with time boxes that add up to {{meeting_length}}. Cover why the project matters, goals and success measures, scope and what is out, roles and decision rights, the plan and milestones, risks and concerns, how we will work together (meetings, tools, how to raise problems) and first actions. 4. Facilitator notes: one open question for each discussion item, for example "What would make this project fail?" or "What do you need from the other teams to do your part?" 5. Ground rules: five or fewer, specific to this group. 6. First actions: a table with the columns Action, Owner, Due date. 7. Follow-up email to send after the meeting, under 150 words, recording decisions and actions. Requirements: - Give at least a third of the time to discussion rather than presenting, because people commit to plans they have helped shape. - Address the known concerns in the agenda rather than avoiding them, and say where and how. - Use only names, roles and dates from my material. Where roles or dates are not settled, write "to agree in the meeting" and make agreeing them an agenda item, rather than deciding them yourself. - For a remote meeting, add how to get input from everyone, such as a shared document or a round where each person speaks. The plan should fit on two pages. If my material does not say what the project is meant to achieve, flag it at the top, because a kickoff without a clear goal turns into a debate about the goal.
Variables
- {{project_summary}}
- The charter, or a summary of the goal, scope, timeline and team.
- {{attendees}}
- Who will be there and their roles, for example "sponsor, project manager, two developers, finance analyst".
- {{meeting_length}}
- For example 90 minutes.
- {{meeting_format}}
- In person, remote or mixed.
- {{kickoff_goals}}
- For example "agreement on scope and the first month's priorities".
- {{concerns}}
- Anything sensitive, for example two teams with competing priorities. Write "none" if there are none.
Why it works
- Who it's for. Treating the kickoff as a working session, with outcomes stated up front, keeps it from becoming an hour of slides nobody remembers.
- Format. A timed agenda, facilitator questions, an actions table and a ready follow-up email cover the meeting from the invitation to the day after.
- If unsure. Unsettled roles and dates become agenda items for the group to agree, instead of being assigned by the model.