kickoff-prep

name	kickoff-prep
description	This skill should be used when the Implementation team is preparing for the customer kickoff call — the first formal Implementation-led meeting after a customer signs. Triggers on: "kickoff prep for [customer]", "prep me for the [customer] kickoff", "build kickoff prep doc", "I have a kickoff call with [customer] tomorrow", "pre-call prep for [customer] kickoff", "AM prep for [customer]". Produces a structured pre-call .docx covering agenda, decisions to lock during the call, expected Q&A, exit criteria, and post-call action items. Reads from the onboarding profile produced by handoff-intake, the Customer Kick-Off SOP, and the shared pre-sales call-transcripts folder.
version	0.2.0

Kickoff Prep

Produce an internal pre-call prep doc for the customer kickoff. The AM walks into the call knowing exactly what decisions to lock and what questions to expect.

When this fires

A kickoff call is on the calendar. The handoff intake is done (or close enough). The AM has 20–60 minutes before the call and wants a single doc to review.

If handoff-intake hasn't run yet, run it first — don't build kickoff prep from scratch. Tell the user: "I don't see an onboarding profile for this customer. Want me to run handoff-intake first?"

Inputs to gather

• Onboarding profile — read <customer-slug>-onboarding-profile.md from the workspace. This is your primary source.
• Customer Kick-Off SOP — find the SOP in Confluence (search for "Customer Kick-Off SOP" or "kickoff SOP"). Read the latest version. Bake its required talking points into the agenda.
• Calendar event — the user has a kickoff event on their calendar. Pull it: attendees, duration, agenda already in the invite. Use this to size the agenda — don't write a 90-minute agenda for a 30-minute meeting.
• Salesforce — re-check the Account for any updates since intake (new contacts, contract amendments, last-minute scope changes).
• Recent Slack mentions — search the customer name in the last 14 days. Surface anything the AE or SE said about the customer between handoff and now.
• Pre-sales call transcripts (Google Drive)
  • Same folder as handoff-intake: 1QEycvwoKScvJ0zv-d8WbQql_X-Ujjpep.
  • Re-scan with the customer name/slug — new calls may have happened between intake and kickoff (e.g., a late SE technical deep-dive).
  • The onboarding profile already captured the headline quotes. Your goal here is freshness, not duplication. Pull quotable lines for:
    • Questions the customer asked — these become the "Expected Q&A" pre-fill.
    • Open items at end of last call — these become "Decisions to lock during this call".
    • Concerns voiced — these become "Risks & watch-outs" entries.
  • Cap at ~3 quotes per transcript. Keep the prep doc tight.
  • If no new transcripts since intake, say so and lean on the profile.

Output

A .docx file saved as <customer-slug>-kickoff-prep.docx. Use the docx skill to build it — that skill handles the heavy lifting of formatting and table styling.

Structure (in this order, with these headings):

1. At a glance — one-paragraph summary: customer, what they bought, who's attending, when, duration. Pull a single sentence from the onboarding profile.

2. Agenda — a time-boxed table matching the meeting duration. Columns: time slot, topic, owner, target outcome. Use the SOP's recommended structure as the skeleton.

3. Decisions to lock during this call — bullet list. Each bullet is something that MUST come out of the meeting with a yes/no or a name attached. Examples: "Confirm go-live target date", "Lock the partner list order", "Identify primary technical POC". Keep it tight — five items max. Promote any unresolved-at-end-of-last-call items from the transcripts into this list.

4. Expected Q&A — two-column table. Left column: question the customer is likely to ask. Right column: how to answer. The first two rows should be questions the customer actually asked on prior calls — quoted, with a source link to the transcript. Fill the remaining rows with the standard ones from the SOP (timeline, EDI vendor migration, testing process, billing) plus customer-specific ones inferred from the handoff doc.

5. Risks & watch-outs — pull from the onboarding profile's "Known risks" section. For each risk, add a one-line plan: how to handle it if it comes up. Where the risk maps to a direct customer quote, include the quote and transcript link.

6. Exit criteria — a checklist of what "kickoff successfully completed" looks like. The AM scans this at the end of the call to know if they need to schedule a follow-up.

7. Post-call action items — leave a placeholder section the AM fills in during/after the call. Include the standard internal next steps (Slack the AE on outcome, update SFDC, etc.).

Rules

• Stay internal. This doc is for the AM, not the customer. Be candid about risks, the AE's promises, and what to push back on.
• Don't pad. If the meeting is 30 minutes, the doc should be readable in 5. Tight bullets, short sentences. No filler.
• Anchor to the SOP. The Implementation team has a process — don't invent a new one. If the SOP says "always confirm comm channel preference in kickoff," that's an agenda item.
• Lead Expected Q&A with real questions. If transcripts exist, the first two rows of Expected Q&A should be questions the customer actually asked on a discovery or demo call — not generic ones. Quote and link.
• Flag missing info. If the onboarding profile said "partner list TBD," surface that as a top decision to lock. Don't quietly pretend the data exists.
• One link per source. Each major section should have a link to its source (handoff doc, SFDC account, Confluence SOP, transcript). The AM should be able to click through during the call.

After saving, output a 3-line summary in chat: customer + time, the single biggest thing to lock, and a link to the doc. Then suggest: "Next step — after the kickoff, run partner-list-intake once the customer sends their partner spreadsheet."