/cs:onboard — Founder Interview
/cs:onboard — Founder interview that populates ~/.claude/company-context.md using the canonical 7-dimension cs-onboard schema.
How to use it
Claude Code
- Run the line below. It pulls the whole folder into
~/.claude/skills/onboard. - Describe your job in plain words. Claude Code follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit alirezarezvani/claude-skills/c-level-agents/skills/onboard#main ~/.claude/skills/onboardFor one project only, change the path to .claude/skills/onboard.
Claude (web or desktop app)
- On this page open ⋯ → Download .md.
- Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
- Pick the file and Save. Claude shows the name and description and runs a security scan.
- Check the skill is switched on.
- Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
- ChatGPT: make a Project and paste it into Instructions.
- Neither? Paste it at the top of a new chat — it works for that chat.
Not working?
- Check which app you pasted it into — the steps above name the right one.
- Some skills need the paid tier of Claude or ChatGPT.
Paste into Claude, ChatGPT or Cursor.
Source of /cs:onboard — Founder Interview
Show the full text127 lines
| name | description |
|---|---|
| onboard | /cs:onboard — Founder interview that populates ~/.claude/company-context.md using the canonical 7-dimension cs-onboard schema. The first command to run when starting with c-level-agents. Use when setting up the virtual C-suite for a new company, or when advisors lack company context — e.g. before a first /cs:boardroom or after a fundraise changes the numbers. |
/cs:onboard — Founder Interview
Command: /cs:onboard
The first command to run when adopting c-level-agents. A structured founder interview that produces ~/.claude/company-context.md — the file every cs-* advisor reads before responding. Without this, the advisors are guessing.
What This Produces
~/.claude/company-context.md — a single file with the durable facts about the company. Read by:
cs-chief-of-staff(routing decisions)- Every cs-* advisor (context for any question)
/cs:brief(assumptions in any new decision)
The Interview (12 Questions)
Company Basics
- Company name and one-sentence pitch.
- Stage: pre-seed / seed / Series A / Series B / Series C+ / public
- Headcount: total, by function (eng / product / GTM / ops / G&A)
- Geographic distribution: HQ + remote split, key countries
Business Model
- Revenue model: SaaS subscription / usage / transaction / marketplace / hardware / services
- ICP: name one real customer and describe what they have in common with others
- ACV: median and range; deal count last 12 months
- Growth rate: ARR YoY; if pre-revenue, leading metric (users, MAU, etc.)
Financial Posture
- Runway: months of cash at current burn; bear-case months
- Last raise: amount, valuation, lead investor, date
Strategic Context
- Top 3 priorities for the current quarter (in plain language)
- Top 3 risks the founder loses sleep over (be specific)
Output Format
Canonical schema: ~/.claude/company-context.md is owned by the cs-onboard skill and follows its 7-dimension schema (../../../c-level-advisor/skills/cs-onboard/templates/company-context-template.md): Company Identity, Stage & Scale, Founder Profile, Team & Culture, Market & Competition, Current Challenges, Goals & Ambition. The 12 questions above are a faster structured intake that populates that same file — Identity/Business/Financial → Stage & Scale, Team → Team & Culture, Quarter priorities/risks → Current Challenges + Goals & Ambition. Write [not captured] for dimensions the quick intake doesn't reach (Founder Profile, Market & Competition); run the full cs-onboard interview to fill them. Never create a second context file or a divergent layout.
The intake summary captured by the 12 questions:
# Company Context
**Generated:** YYYY-MM-DD
**Last updated:** YYYY-MM-DD
## Identity
- **Company:** <name>
- **Pitch:** <one sentence>
- **Stage:** <stage>
- **HQ + remote:** <distribution>
## Business
- **Model:** <type>
- **ICP:** <description + named customer>
- **ACV:** $<median> (range $<low> - $<high>)
- **Deal count (LTM):** N
- **ARR growth (YoY):** X%
## Financial
- **Cash on hand:** $<amount>
- **Net burn (monthly):** $<amount>
- **Runway base:** N months
- **Runway bear:** N months
- **Last raise:** $<amount> at $<post> in <month YYYY>, led by <investor>
## Team
- **Total headcount:** N
- **Eng:** N | Product: N | GTM: N | Ops: N | G&A: N
## Quarter
- **Top priorities (Q<X> YYYY):**
1. <priority>
2. <priority>
3. <priority>
- **Top risks:**
1. <risk>
2. <risk>
3. <risk>
## Routing Hints
[Optional: any role the founder wants to use sparingly or rely on heavily]
Workflow
- Walk the founder through all 12 questions
- Quote founder's own words wherever possible (don't paraphrase the ICP)
- Save to
~/.claude/company-context.md - (Optional) If llm-wiki bridge is configured: symlink to vault
ln -sf ~/company-vault/00-meta/company-context.md ~/.claude/company-context.md - Confirm with founder: read the file back, ask "anything missing?"
When to Re-Run
- After a fundraise (numbers change)
- After a major pivot or product launch
- After 6+ months (most facts have drifted)
- After a major hire (team distribution changes)
- Always before a
/cs:boardroomfor a high-stakes decision
Persistence
By default, ~/.claude/company-context.md is local to the founder's machine. To make it persistent across machines / shareable:
- Markdown vault (recommended): see
../../references/llm-wiki-bridge.md - Encrypted dotfile sync: age + git
- Shared team: keep in a private repo, symlink from
~/.claude/
Related
- Skill:
cs-onboard— the underlying interview protocol - Skill:
context-engine— reads this file - Reference:
../../references/llm-wiki-bridge.md
Version: 1.0.0
| 1 | |
| 2 | name "onboard" |
| 3 | description "/cs:onboard — Founder interview that populates ~/.claude/company-context.md using the canonical 7-dimension cs-onboard schema. The first command to run when starting with c-level-agents. Use when setting up the virtual C-suite for a new company, or when advisors lack company context — e.g. before a first /cs:boardroom or after a fundraise changes the numbers." |
| 4 | |
| 5 | |
| 6 | # /cs:onboard — Founder Interview |
| 7 | |
| 8 | **Command:** `/cs:onboard` |
| 9 | |
| 10 | The first command to run when adopting c-level-agents. A structured founder interview that produces `~/.claude/company-context.md` — the file every cs-* advisor reads before responding. Without this, the advisors are guessing. |
| 11 | |
| 12 | ## What This Produces |
| 13 | |
| 14 | `~/.claude/company-context.md` — a single file with the durable facts about the company. Read by: |
| 15 | `cs-chief-of-staff` (routing decisions) |
| 16 | Every cs-* advisor (context for any question) |
| 17 | `/cs:brief` (assumptions in any new decision) |
| 18 | |
| 19 | ## The Interview (12 Questions) |
| 20 | |
| 21 | ### Company Basics |
| 22 | **Company name and one-sentence pitch.** |
| 23 | **Stage:** pre-seed / seed / Series A / Series B / Series C+ / public |
| 24 | **Headcount:** total, by function (eng / product / GTM / ops / G&A) |
| 25 | **Geographic distribution:** HQ + remote split, key countries |
| 26 | |
| 27 | ### Business Model |
| 28 | **Revenue model:** SaaS subscription / usage / transaction / marketplace / hardware / services |
| 29 | **ICP:** name one real customer and describe what they have in common with others |
| 30 | **ACV:** median and range; deal count last 12 months |
| 31 | **Growth rate:** ARR YoY; if pre-revenue, leading metric (users, MAU, etc.) |
| 32 | |
| 33 | ### Financial Posture |
| 34 | **Runway:** months of cash at current burn; bear-case months |
| 35 | **Last raise:** amount, valuation, lead investor, date |
| 36 | |
| 37 | ### Strategic Context |
| 38 | **Top 3 priorities for the current quarter** (in plain language) |
| 39 | **Top 3 risks the founder loses sleep over** (be specific) |
| 40 | |
| 41 | ## Output Format |
| 42 | |
| 43 | **Canonical schema:** `~/.claude/company-context.md` is owned by the [`cs-onboard`] skill and follows its 7-dimension schema (`../../../c-level-advisor/skills/cs-onboard/templates/company-context-template.md`): Company Identity, Stage & Scale, Founder Profile, Team & Culture, Market & Competition, Current Challenges, Goals & Ambition. The 12 questions above are a faster structured intake that populates that same file — Identity/Business/Financial → Stage & Scale, Team → Team & Culture, Quarter priorities/risks → Current Challenges + Goals & Ambition. Write `[not captured]` for dimensions the quick intake doesn't reach (Founder Profile, Market & Competition); run the full `cs-onboard` interview to fill them. Never create a second context file or a divergent layout. |
| 44 | |
| 45 | The intake summary captured by the 12 questions: |
| 46 | |
| 47 | |
| 48 | # Company Context |
| 49 | **Generated:** YYYY-MM-DD |
| 50 | **Last updated:** YYYY-MM-DD |
| 51 | |
| 52 | ## Identity |
| 53 | - **Company:** <name> |
| 54 | - **Pitch:** <one sentence> |
| 55 | - **Stage:** <stage> |
| 56 | - **HQ + remote:** <distribution> |
| 57 | |
| 58 | ## Business |
| 59 | - **Model:** <type> |
| 60 | - **ICP:** <description + named customer> |
| 61 | - **ACV:** $<median> (range $<low> - $<high>) |
| 62 | - **Deal count (LTM):** N |
| 63 | - **ARR growth (YoY):** X% |
| 64 | |
| 65 | ## Financial |
| 66 | - **Cash on hand:** $<amount> |
| 67 | - **Net burn (monthly):** $<amount> |
| 68 | - **Runway base:** N months |
| 69 | - **Runway bear:** N months |
| 70 | - **Last raise:** $<amount> at $<post> in <month YYYY>, led by <investor> |
| 71 | |
| 72 | ## Team |
| 73 | - **Total headcount:** N |
| 74 | - **Eng:** N | Product: N | GTM: N | Ops: N | G&A: N |
| 75 | |
| 76 | ## Quarter |
| 77 | - **Top priorities (Q<X> YYYY):** |
| 78 | 1. <priority> |
| 79 | 2. <priority> |
| 80 | 3. <priority> |
| 81 | |
| 82 | - **Top risks:** |
| 83 | 1. <risk> |
| 84 | 2. <risk> |
| 85 | 3. <risk> |
| 86 | |
| 87 | ## Routing Hints |
| 88 | [Optional: any role the founder wants to use sparingly or rely on heavily] |
| 89 | |
| 90 | |
| 91 | ## Workflow |
| 92 | |
| 93 | Walk the founder through all 12 questions |
| 94 | Quote founder's own words wherever possible (don't paraphrase the ICP) |
| 95 | Save to `~/.claude/company-context.md` |
| 96 | (Optional) If llm-wiki bridge is configured: symlink to vault |
| 97 | |
| 98 | ln -sf ~/company-vault/00-meta/company-context.md ~/.claude/company-context.md |
| 99 | |
| 100 | Confirm with founder: read the file back, ask "anything missing?" |
| 101 | |
| 102 | ## When to Re-Run |
| 103 | |
| 104 | After a fundraise (numbers change) |
| 105 | After a major pivot or product launch |
| 106 | After 6+ months (most facts have drifted) |
| 107 | After a major hire (team distribution changes) |
| 108 | Always before a `/cs:boardroom` for a high-stakes decision |
| 109 | |
| 110 | ## Persistence |
| 111 | |
| 112 | By default, `~/.claude/company-context.md` is local to the founder's machine. To make it persistent across machines / shareable: |
| 113 | |
| 114 | **Markdown vault (recommended):** see [`../../references/llm-wiki-bridge.md`] |
| 115 | **Encrypted dotfile sync:** age + git |
| 116 | **Shared team:** keep in a private repo, symlink from `~/.claude/` |
| 117 | |
| 118 | ## Related |
| 119 | |
| 120 | Skill: [`cs-onboard`] — the underlying interview protocol |
| 121 | Skill: [`context-engine`] — reads this file |
| 122 | Reference: [`../../references/llm-wiki-bridge.md`] |
| 123 | |
| 124 | |
| 125 | |
| 126 | **Version:** 1.0.0 |
| 127 |
Discussion
To questionnaireTell us who you need answers from and what you're missing; get back a clean form you send them to fill in.360-Degree Feedback Template SkillDesign a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.Persona & ScriptStart of the UGC pipeline for persona research, creator profiles, format selection, and scriptwriting. Use when the user is clearly asking for messaging work rather than broad full-pipeline orchestration.Interview meExtracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invokes ("interview me", "grill me", "are we sure?", "stress-test my thinking"), or when you catch yourself silently filling in ambiguous requirements before any plan, spec, or code exists.
Browse more free Claude skills or everything in Product.