Official skill · Operations and admin
Project kickoff brief
Writes a one-page kickoff brief: goal, one success measure, scope in and out, milestones, a RACI-lite table, top risks with owners, and how the team talks. Use it when A project, launch, or client engagement is starting and needs one shared page.
AI skill
Have your AI write the one-page brief that starts a project
14 days free · No card needed
Works in Claude, ChatGPT, and coding agents. On Team and Business, the official skill in your pod updates itself when we improve it.
When to use it
- A project, launch, or client engagement is starting and needs one shared page
- People disagree about scope or who decides on a running project
What you give it
- Goal and why it matters now
- Target date
- People and roles
- Known constraints and decisions (optional)
What you get
A one-page Markdown brief with goal, success measure, scope table, milestones, RACI-lite roles, risks, and communication plan.
How it works
- Write the goal in 1 or 2 sentences
- Pick one success measure
- Split scope into in and out
- Set 3 to 6 milestones
- Fill the RACI-lite table
- List the top 3 to 5 risks
- Say how the team communicates
- List open questions and decided items
Example
What you give it
We're moving our 120 active customers from the old billing tool (Billwise) to Stripe. Kickoff is 7 April; Billwise gets cancelled on 30 June. Dana runs it, Marco does the integration, Aisha handles customer emails, finance (Lena) needs to sign off on the new invoice template by 2 May. CEO Tom wants it done before the price change on 1 July. Marco's plan: 5 internal test accounts billing correctly in Stripe test mode by 25 April, all customers live by 13 June. Aisha sends the notice by 16 May, then a reminder 1 week before each customer moves, and phones the top 20 accounts. Not doing: cancelled customers' history, a self-serve billing portal, accounting system changes. Worries: saved cards might not transfer; someone billed twice in the switch month. Failed payments must not go up. We talk in #billing-migration, Dana writes a Friday update, we meet 20 minutes on Tuesdays, decisions go in the project doc. We already decided no price changes during the migration. Lena wants to know if we keep Billwise read-only for a month after cancelling.
What you get back (the start of it)
Billing migration to Stripe — kickoff brief
Accountable owner: Dana · Start: 7 April · Target date: 30 June
Goal
Move all customers from Billwise to Stripe before the price change on 1 July, so the new prices go live on one system and Billwise can be cancelled.
Success measure
- Primary: 120 of 120 active customers billed through Stripe by 30 June.
- Guardrails: No customer is charged twice or missed in any month; failed payments stay at or below the current monthly level.
The rest of this output, the full steps and the checks the AI runs before it answers are in your pod once you add the skill.
Use this skill in your AIShare it with your team
Add it to an AI Skill Pod and everyone on the team, contractors included, uses the same version from their own AI. Read the best ways to share AI skills with a team
Changelog
- v1.0.1 · · Example: the roles table is marked [draft, confirm at kickoff], since the input names people but not who is consulted or informed; the two risk actions the input doesn't give are marked Proposed.
- v1.0.0 · · First release.
Sources
- Project kickoff meeting: 10-step guide for success (Asana) (read 2026-11-04)
- Planning project kickoff meetings: steps and example agenda (Atlassian Team Playbook) (read 2026-11-04)
- RACI charts: the ultimate guide, with examples (Asana) (read 2026-11-04)
- How to run pre-mortem exercises (Atlassian Team Playbook) (read 2026-11-04)