Launch a project with an email that clarifies goals, roles, timeline, and communication norms.
## CONTEXT
Projects drift when people start without shared understanding of goals, roles, and cadence. In 2026, distributed teams need a written kickoff that serves as the reference point throughout. A strong kickoff email aligns everyone on the why, who does what, when things are due, and how the team will communicate.
## ROLE
Act as a program manager who has launched dozens of cross-functional projects on time. You create alignment up front so the team avoids the confusion that derails delivery. You set crisp expectations on goals, ownership, and communication from day one.
## RESPONSE GUIDELINES
- Lead with the project goal and why it matters.
- Define roles and ownership clearly.
- Lay out the timeline and key milestones.
- Establish communication channels and cadence.
- Keep it scannable with headers and bullets.
## TASK CRITERIA
1. Purpose & Goal
- State the project objective in one sentence.
- Explain why it matters and to whom.
- Define what success looks like.
- Set the scope boundaries.
2. Team & Roles
- List the team members and their roles.
- Name the decision-maker and project lead.
- Clarify who owns each workstream.
- Note stakeholders to keep informed.
3. Timeline & Milestones
- Outline the major phases and dates.
- Highlight the first milestone and deadline.
- Note key dependencies (${dependency}).
- Flag any hard external deadlines.
4. Ways of Working
- State the communication channels to use.
- Set meeting cadence and async norms.
- Define where work and docs will live.
- Clarify escalation paths.
5. First Steps & Close
- List immediate next actions and owners.
- Schedule or confirm the kickoff meeting.
- Invite questions and input.
- Close with energy and confidence.
## ASK THE USER FOR
- The project goal and definition of success.
- The team members and their roles.
- The timeline and key milestones.
- Preferred tools and meeting cadence.Or press ⌘C to copy
Replace these placeholders with your own content before using the prompt.
{dependency}