expansion-onboarding

Classify expansion scenarios and scaffold success plans with M1–M5 milestones.

58|21|Updated May 15, 2026
One-click install
npx skills add https://github.com/t0ddc3by/claude-for-customer-success --skill expansion-onboarding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expansion-onboarding
Source: https://github.com/t0ddc3by/claude-for-customer-success/tree/main/csm/skills/expansion-onboarding
Command: npx skills add https://github.com/t0ddc3by/claude-for-customer-success --skill expansion-onboarding

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Expansion onboarding for Customer Success can stall when CSQL details, success criteria, and a milestone-driven kickoff plan are not assembled into a consistent set of execution-ready artifacts.

Core Features & Use Cases

  • Builds a 5-phase expansion kickoff package that classifies the expansion source, scaffolds a success plan, logs OCV entry details, sets M1–M5 milestones, and produces a kickoff agenda.
  • Creates and safely updates account context artifacts by writing expansion success-plan, OCV log, and milestone files into the context/ directory with explicit human confirmation for each write.
  • Supports two starting modes: csql-driven expansion (requires a confirmed CSQL close and CSQL ID) and csm-led expansion (no CSQL ID needed).
  • Example use case: when an expansion deal is marked won, generate the success plan scaffold, an OCV entry for the expansion opportunity, and a 90-day milestone set plus a kickoff agenda for the CSM to run.

Quick Start

Run expansion onboarding for Acme Corp — adding Analytics Pro, using csql mode with csql_id provided.

Frequently Asked Questions about expansion-onboarding

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an expansion kickoff plan with milestones for customer success?

To create an expansion kickoff plan, this workflow scaffolds a success plan, logs OCV entry details, sets M1–M5 milestone targets, and generates a kickoff agenda for Customer Success Managers to execute.

What is expansion onboarding for customer success and when do I need it?

Expansion onboarding is the process of assembling execution-ready artifacts after an expansion deal closes, needed when CSQL details, success criteria, and milestone-driven kickoff plans must be consolidated for Stage 4 lifecycle onboarding.

Can I run customer success expansion onboarding without a CSQL ID?

Yes, you can run expansion onboarding without a CSQL ID by using the csm-led expansion mode, which bypasses the requirement for a confirmed CSQL close needed in csql-driven expansion mode.

What's the best way to safely log OCV entry details during deal-to-execution onboarding?

The best way to log OCV entries safely is by validating the OCV file structure before appends, sanitizing inputs, scanning for injections, and requiring G9 confirmation for all context or filesystem write operations.

Do I need account context and expansion deal inputs available for customer success onboarding?

Yes, you need account context and expansion deal inputs available, as the workflow requires these inputs to classify the expansion scenario and scaffold the success plan and milestone targets during Stage 4 lifecycle onboarding.