Product-org-os onboarding-playbook

'Create customer onboarding playbook with milestones, success metrics, and engagement sequences. Activate when: "onboarding playbook", "customer onboarding", "first-run experience", onboarding

install
source · Clone the upstream repo
git clone https://github.com/yohayetsion/product-org-os
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/yohayetsion/product-org-os "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/onboarding-playbook" ~/.claude/skills/yohayetsion-product-org-os-onboarding-playbook && rm -rf "$T"
manifest: skills/onboarding-playbook/SKILL.md
source content

Document Intelligence

This skill supports three modes: Create, Update, and Find.

Mode Detection

SignalModeConfidence
"update", "revise", "improve" in inputUPDATE100%
File path providedUPDATE100%
"create", "new", "build" in inputCREATE100%
"find", "search", "list"FIND100%
"the playbook", "onboarding playbook"UPDATE85%
Just product/segmentCREATE60%

Threshold: ≥85% auto-proceed | 70-84% state assumption | <70% ask user

Mode Behaviors

CREATE: Generate complete new playbook using template below.

UPDATE:

  1. Check document registry first, then search user's structure
  2. Preserve journey map structure
  3. Update milestones, blockers, or success criteria
  4. Show diff summary

FIND: Check registry, then search user's folders for playbooks.


Create a Customer Onboarding Playbook for the specified product or customer segment.

Vision to Value Phase

Phase 5: Business & Customer Outcomes - This skill ensures customers realize value.

Output Structure

1. Onboarding Overview

  • Target customer segment
  • Onboarding duration
  • Key milestones
  • Success definition

2. Onboarding Journey Map

StageDurationCustomer GoalOur ActivitiesSuccess Criteria
KickoffDay 1-3[Goal][Activities][Criteria]
SetupWeek 1[Goal][Activities][Criteria]
TrainingWeek 2[Goal][Activities][Criteria]
AdoptionWeek 3-4[Goal][Activities][Criteria]
ValueWeek 4+[Goal][Activities][Criteria]

3. Key Milestones

MilestoneTarget TimingDefinition of DoneOwner
Account activatedDay 1[Definition][Owner]
First use case completedWeek 1[Definition][Owner]
Team trainedWeek 2[Definition][Owner]
Value milestone hitWeek 4[Definition][Owner]

4. Success Criteria

MetricTargetTimeframe
Time to first valueX daysDay 1-7
Feature adoptionX%Week 1-4
User activationX%Week 2-4
Satisfaction scoreXWeek 4

5. Common Blockers & Solutions

BlockerSymptomsSolutionOwner
Technical integration issues[Symptoms][Solution][Owner]
Low user adoption[Symptoms][Solution][Owner]
Unclear success criteria[Symptoms][Solution][Owner]
Champion turnover[Symptoms][Solution][Owner]

6. Escalation Paths

Issue TypeFirst ContactEscalation 1Escalation 2
Technical[Contact][Contact][Contact]
Business[Contact][Contact][Contact]
Relationship[Contact][Contact][Contact]

7. Time-to-Value Targets

SegmentFirst ValueFull ValueAt-Risk Threshold
EnterpriseX daysX weeksX weeks
Mid-marketX daysX weeksX weeks
SMBX daysX weeksX weeks

8. Health Indicators

Green (On Track):

  • [Indicator 1]
  • [Indicator 2]

Yellow (At Risk):

  • [Indicator 1]
  • [Indicator 2]

Red (Intervention Needed):

  • [Indicator 1]
  • [Indicator 2]

9. Handoff Procedures

  • Handoff from sales to CS
  • Handoff from implementation to ongoing support
  • Documentation requirements
  • Communication templates

10. Resources

  • Onboarding materials
  • Training content
  • Templates
  • FAQs

Instructions

  1. Ask about customer segment if not specified
  2. Reference any product or CS documents provided via @file syntax
  3. Include specific, measurable milestones
  4. Address common blockers proactively
  5. Save as markdown file
  6. Offer to create presentation version using /present