Client onboarding
Generate comprehensive onboarding materials for new client engagements. Creates access checklists, asset gathering lists, and kick-off meeting agendas tailored to the project scope.
Doctrine inherited (Step 7 — 0626 rollout, locked 2026-06-04)
Output complies with output-tenets.md, output-simplicity.md, doc-output-structure.md. Step 6 calibration: see [[feedback_execution_doctrine_refinements_step6]].
Refinements applied: R1 (onboarding pack is client-team review surface — cites in appendix), R2 (multi-asset onboarding pack ships as one doc with toggles per asset: access checklist + assets list + kick-off agenda), R3 (welcome framing operator-direct, never "thrilled to have you"), R6 (close → kickoff scheduling primary), R9 (verb-led section names).
Process at a glance
INPUT VALIDATION → ACCESS CHECKLIST → ASSETS GATHER → KICK-OFF AGENDA → REVIEW & CHAIN
Five steps:
- Generate access checklist (tools by category, owners, access level)
- Create asset gathering list (per deliverable, with rationale)
- Design kick-off agenda (60-min, scope-specific context areas)
- Scaffold client folder (
projects/consulting/active/{client}/ + CLAUDE.md template)
- Create brand hub if visual assets available (run
/brand-kit Quick mode), else schedule for Week 2
Full flowchart, step-by-step runbook, self-evaluation gate in the premium reference.
Claude Code triggers
Invoke this skill when user says:
- "Onboarding for [client]"
- "New client [name]"
- "Kick-off prep for [client]"
- "Starting with [client] tomorrow"
- "Onboarding checklist"
- "What do I need for the kick-off"
Do NOT invoke when:
- User wants discovery call prep → Use
client-discovery skill
- User wants to create a proposal → Use
client-proposals skill
- User wants to scaffold folder only → Use
new-client skill
Inputs
Required
| Input |
Description |
Source |
| Client name |
Company name |
User provides |
| Project scope |
Deliverables for first month/engagement |
User provides or proposal |
Optional (improve quality)
| Input |
How it helps |
| Client industry |
Tailors tool recommendations (FinTech needs compliance tools) |
| Known stakeholders |
Pre-populates kick-off attendee list |
| Competitors |
Adds competitor-specific assets to gather |
| Engagement length |
Adjusts scope of onboarding materials |
| Prior discovery notes |
Avoids re-asking known context |
If inputs are missing: Ask for project scope — what are you delivering in month 1?
Deliverable-to-asset mapping
Use this framework to identify what assets are needed for common deliverables:
| Deliverable |
Required assets |
Why needed |
| Win/loss analysis |
3-5 lost deal recordings, 3-5 won deal recordings, deal context spreadsheet, sales notes |
Pattern identification requires multiple calls; context helps cross-reference by segment |
| Competitor research |
Existing battlecards, lost deals to competitors, sales team POV, competitor pricing intel |
Avoid duplicating work; get ground-level intel beyond public info |
| ICP refinement |
Current ICP doc, top 10 best customers, top 10 churned, CRM segment data, customer interviews |
Pattern recognition requires both positive and negative examples |
| Positioning/messaging |
Current positioning doc, investor deck, founder story, testimonials, G2 reviews |
Build on existing work; use authentic voice and proof points |
| Website copy |
Current analytics, heatmaps, current site access, brand guidelines |
Baseline performance; design constraints |
| Brand hub |
Figma access, brand PDF/style guide, logo files (SVG/PNG), brand colors doc |
Visual identity for all downstream deliverables |
| Sales deck |
Current deck, demo scripts, objection handling doc, competitive intel |
Understand current narrative; address known objections |
| Battlecards |
Win/loss insights, competitor research, sales team input |
Evidence-based competitive positioning |
Anti-hallucination guardrails
- Base on scope. Only request assets needed for stated deliverables.
- Be specific. Not "marketing materials" but "current positioning doc."
- Include rationale. Every asset needs a "why you need it."
- Don't invent stakeholders. Ask client for attendee list.
- Don't assume tools. Ask what CRM, analytics, etc. they use.
Integration with other skills
| Skill |
Relationship |
| client-proposals |
Onboarding follows accepted proposal |
| client-discovery |
Discovery may precede onboarding |
| company-context |
Pre-research client before kick-off |
| win-loss-analysis |
Common first deliverable |
| competitor-research |
Common first deliverable |
| icp-behavioural |
Common first deliverable |
| brand-kit |
Create visual brand system from brand assets |
MCP data integration
Level: 3 — Content Execution (client-specific pulls)
Pulls fresh
| Source |
What to pull |
Tool |
When |
| Slack |
Client channel history, prior discussions |
slack_read_channel |
If client Slack channel exists |
| Granola |
Kick-off meeting notes, discovery calls |
search_meetings |
Always |
Fallback (no MCP)
- User-provided meeting notes
- Manual Slack history review
Final ship gate
Run /premortem --output before ship. See /premortem skill for the 5 execution domains (will-it-resonate / will-it-convert / will-it-stay-on-brand / will-stakeholder-push-back / will-it-degrade-over-time) and output template.
Trivial-case escape: ## Premortem\nNo failure modes — trivial change satisfies the contract for genuinely trivial outputs.
1---2name: client-onboarding3description: Client onboarding4---56# Client onboarding78Generate comprehensive onboarding materials for new client engagements. Creates access checklists, asset gathering lists, and kick-off meeting agendas tailored to the project scope.910---1112## Doctrine inherited (Step 7 — 0626 rollout, locked 2026-06-04)1314Output complies with [`output-tenets.md`](../../../../rules/output-tenets.md), [`output-simplicity.md`](../../../../rules/output-simplicity.md), [`doc-output-structure.md`](../../../../rules/doc-output-structure.md). Step 6 calibration: see [[feedback_execution_doctrine_refinements_step6]].1516**Refinements applied:** R1 (onboarding pack is client-team review surface — cites in appendix), R2 (multi-asset onboarding pack ships as one doc with toggles per asset: access checklist + assets list + kick-off agenda), R3 (welcome framing operator-direct, never "thrilled to have you"), R6 (close → kickoff scheduling primary), R9 (verb-led section names).1718---1920## Process at a glance2122```23INPUT VALIDATION → ACCESS CHECKLIST → ASSETS GATHER → KICK-OFF AGENDA → REVIEW & CHAIN24```2526Five steps:271. Generate access checklist (tools by category, owners, access level)282. Create asset gathering list (per deliverable, with rationale)293. Design kick-off agenda (60-min, scope-specific context areas)304. Scaffold client folder (`projects/consulting/active/{client}/` + CLAUDE.md template)315. Create brand hub if visual assets available (run `/brand-kit` Quick mode), else schedule for Week 23233Full flowchart, step-by-step runbook, self-evaluation gate in the premium reference.3435---3637## Claude Code triggers3839**Invoke this skill when user says:**40- "Onboarding for [client]"41- "New client [name]"42- "Kick-off prep for [client]"43- "Starting with [client] tomorrow"44- "Onboarding checklist"45- "What do I need for the kick-off"4647**Do NOT invoke when:**48- User wants discovery call prep → Use `client-discovery` skill49- User wants to create a proposal → Use `client-proposals` skill50- User wants to scaffold folder only → Use `new-client` skill5152---5354## Inputs5556### Required5758| Input | Description | Source |59|-------|-------------|--------|60| **Client name** | Company name | User provides |61| **Project scope** | Deliverables for first month/engagement | User provides or proposal |6263### Optional (improve quality)6465| Input | How it helps |66|-------|--------------|67| Client industry | Tailors tool recommendations (FinTech needs compliance tools) |68| Known stakeholders | Pre-populates kick-off attendee list |69| Competitors | Adds competitor-specific assets to gather |70| Engagement length | Adjusts scope of onboarding materials |71| Prior discovery notes | Avoids re-asking known context |7273**If inputs are missing:** Ask for project scope — what are you delivering in month 1?7475---7677## Deliverable-to-asset mapping7879Use this framework to identify what assets are needed for common deliverables:8081| Deliverable | Required assets | Why needed |82|-------------|-----------------|------------|83| **Win/loss analysis** | 3-5 lost deal recordings, 3-5 won deal recordings, deal context spreadsheet, sales notes | Pattern identification requires multiple calls; context helps cross-reference by segment |84| **Competitor research** | Existing battlecards, lost deals to competitors, sales team POV, competitor pricing intel | Avoid duplicating work; get ground-level intel beyond public info |85| **ICP refinement** | Current ICP doc, top 10 best customers, top 10 churned, CRM segment data, customer interviews | Pattern recognition requires both positive and negative examples |86| **Positioning/messaging** | Current positioning doc, investor deck, founder story, testimonials, G2 reviews | Build on existing work; use authentic voice and proof points |87| **Website copy** | Current analytics, heatmaps, current site access, brand guidelines | Baseline performance; design constraints |88| **Brand hub** | Figma access, brand PDF/style guide, logo files (SVG/PNG), brand colors doc | Visual identity for all downstream deliverables |89| **Sales deck** | Current deck, demo scripts, objection handling doc, competitive intel | Understand current narrative; address known objections |90| **Battlecards** | Win/loss insights, competitor research, sales team input | Evidence-based competitive positioning |9192---9394## Anti-hallucination guardrails95961. **Base on scope.** Only request assets needed for stated deliverables.972. **Be specific.** Not "marketing materials" but "current positioning doc."983. **Include rationale.** Every asset needs a "why you need it."994. **Don't invent stakeholders.** Ask client for attendee list.1005. **Don't assume tools.** Ask what CRM, analytics, etc. they use.101102---103104## Integration with other skills105106| Skill | Relationship |107|-------|--------------|108| **client-proposals** | Onboarding follows accepted proposal |109| **client-discovery** | Discovery may precede onboarding |110| **company-context** | Pre-research client before kick-off |111| **win-loss-analysis** | Common first deliverable |112| **competitor-research** | Common first deliverable |113| **icp-behavioural** | Common first deliverable |114| **brand-kit** | Create visual brand system from brand assets |115116---117118## MCP data integration119120**Level:** 3 — Content Execution (client-specific pulls)121122### Pulls fresh123124| Source | What to pull | Tool | When |125|--------|-------------|------|------|126| **Slack** | Client channel history, prior discussions | `slack_read_channel` | If client Slack channel exists |127| **Granola** | Kick-off meeting notes, discovery calls | `search_meetings` | Always |128129### Fallback (no MCP)130131- User-provided meeting notes132- Manual Slack history review133134---135136## Final ship gate137138Run `/premortem --output` before ship. See [`/premortem` skill](../../../meta/orchestration/premortem/SKILL.md) for the 5 execution domains (will-it-resonate / will-it-convert / will-it-stay-on-brand / will-stakeholder-push-back / will-it-degrade-over-time) and output template.139140Trivial-case escape: `## Premortem\nNo failure modes — trivial change` satisfies the contract for genuinely trivial outputs.141142---143
matteotitta