Founder onboarding interview that captures company context

C-Suite Onboarding

by alirezarezvani · MIT license · ★ 26,349 on GitHub · updated Aug 30

Founder onboarding interview that captures company context across 7 dimensions. Invoke with /cs:setup for initial interview or /cs:update for quarterly refresh.

---
name: "cs-onboard"
description: "Founder onboarding interview that captures company context across 7 dimensions. Invoke with /cs:setup for initial interview or /cs:update for quarterly refresh. Generates ~/.claude/company-context.md used by all C-suite advisor skills. Use when setting up the C-suite advisors for the first time, or when company context is missing or more than 90 days old — e.g. after a fundraise or pivot."
license: MIT
metadata:
  version: 1.0.0
  author: Alireza Rezvani
  category: c-level
  domain: orchestration
  updated: 2026-03-05
  frameworks: founder-interview, context-capture, quarterly-refresh
---

# C-Suite Onboarding

Structured founder interview that builds the company context file powering every C-suite advisor. One 45-minute conversation. Persistent context across all roles.

## Commands

Overview

Structured founder interview that builds the company context file powering every C-suite advisor. One 45-minute conversation. Persistent context across all roles.

Manual install (npx, ZIP)

Claude Codenpx skills add alirezarezvani/claude-skills --skill cs-onboard -g -a claude-code

Claude Code (manual)

mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/alirezarezvani/claude-skills/tar.gz/19392f7a0826 \
  | tar -xz -C ~/.claude/skills --strip-components=3 claude-skills-19392f7a0826/c-level-advisor/skills/cs-onboard

Windows (PowerShell)

New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/8f6c6c275c79f81a8b81/cs-onboard.zip" -OutFile "$env:TEMP\cs-onboard.zip"; Expand-Archive "$env:TEMP\cs-onboard.zip" -DestinationPath "$HOME\.claude\skills" -Force

Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md4.7 KB
references/1 file · 7.6 KB
templates/1 file · 3.0 KB

Read the files here

alirezarezvani/19392f73 files

SKILL.md4.7 KB

SKILL.md

Show the full text109 lines

cs-onboard/SKILL.md109 lines · 4.7 KB

PreviewCode

Outline

RawView on GitHub

C-Suite Onboarding

Structured founder interview that builds the company context file powering every C-suite advisor. One 45-minute conversation. Persistent context across all roles.

Commands

/cs:setup — Full onboarding interview (~45 min, 7 dimensions)
/cs:update — Quarterly refresh (~15 min, "what changed?")

Keywords

cs:setup, cs:update, company context, founder interview, onboarding, company profile, c-suite setup, advisor setup

Conversation Principles

Be a conversation, not an interrogation. Ask one question at a time. Follow threads. Reflect back: "So the real issue sounds like X — is that right?" Watch for what they skip — that's where the real story lives. Never read a list of questions.

Open with: "Tell me about the company in your own words — what are you building and why does it matter?"

7 Interview Dimensions

1. Company Identity

Capture: what they do, who it's for, the real founding "why," one-sentence pitch, non-negotiable values. Key probe: "What's a value you'd fire someone over violating?" Red flag: Values that sound like marketing copy.

2. Stage & Scale

Capture: headcount (FT vs contractors), revenue range, runway, stage (pre-PMF / scaling / optimizing), what broke in last 90 days. Key probe: "If you had to label your stage — still finding PMF, scaling what works, or optimizing?"

3. Founder Profile

Capture: self-identified superpower, acknowledged blind spots, archetype (product/sales/technical/operator), what actually keeps them up at night. Key probe: "What would your co-founder say you should stop doing?" Red flag: No blind spots, or weakness framed as a strength.

4. Team & Culture

Capture: team in 3 words, last real conflict and resolution, which values are real vs aspirational, strongest and weakest leader. Key probe: "Which of your stated values is most real? Which is a poster on the wall?" Red flag: "We have no conflict."

5. Market & Competition

Capture: who's winning and why (honest version), real unfair advantage, the one competitive move that could hurt them. Key probe: "What's your real unfair advantage — not the investor version?" Red flag: "We have no real competition."

6. Current Challenges

Capture: priority stack-rank across product/growth/people/money/operations, the decision they've been avoiding, the "one extra day" answer. Key probe: "What's the decision you've been putting off for weeks?" Note: The "extra day" answer reveals true priorities.

7. Goals & Ambition

Capture: 12-month target (specific), 36-month target (directional), exit vs build-forever orientation, personal success definition. Key probe: "What does success look like for you personally — separate from the company?"

Output: company-context.md

After the interview, generate ~/.claude/company-context.md using templates/company-context-template.md.

Fill every section. Write [not captured] for unknowns — never leave blank. Add timestamp, mark as fresh.

Tell the founder: "I've captured everything in your company context. Every advisor will use this to give specific, relevant advice. Run /cs:update in 90 days to keep it current."

/cs:update — Quarterly Refresh

Trigger: Every 90 days or after a major change. Duration: ~15 minutes.

Open with: "It's been [X time] since we did your company context. What's changed?"

Walk each dimension with one "what changed?" question:

Identity: same mission or shifted?
Scale: team, revenue, runway now?
Founder: role or what's stretching you?
Team: any leadership changes?
Market: any competitive surprises?
Challenges: #1 problem now vs 90 days ago?
Goals: still on track for 12-month target?

Update the context file, refresh timestamp, reset to fresh.

Context File Location

~/.claude/company-context.md — single source of truth for all C-suite skills. Do not move it. Do not create duplicates.

References

templates/company-context-template.md — blank template for output
references/interview-guide.md — deep interview craft: probes, red flags, handling reluctant founders

1	---
2	name: "cs-onboard"
3	description: "Founder onboarding interview that captures company context across 7 dimensions. Invoke with /cs:setup for initial interview or /cs:update for quarterly refresh. Generates ~/.claude/company-context.md used by all C-suite advisor skills. Use when setting up the C-suite advisors for the first time, or when company context is missing or more than 90 days old — e.g. after a fundraise or pivot."
4	license: MIT
5	metadata:
6	version: 1.0.0
7	author: Alireza Rezvani
8	category: c-level
9	domain: orchestration
10	updated: 2026-03-05
11	frameworks: founder-interview, context-capture, quarterly-refresh
12	---
13
14	# C-Suite Onboarding
15
16	Structured founder interview that builds the company context file powering every C-suite advisor. One 45-minute conversation. Persistent context across all roles.
17
18	## Commands
19
20	- `/cs:setup` — Full onboarding interview (~45 min, 7 dimensions)
21	- `/cs:update` — Quarterly refresh (~15 min, "what changed?")
22
23	## Keywords
24	cs:setup, cs:update, company context, founder interview, onboarding, company profile, c-suite setup, advisor setup
25
26	---
27
28	## Conversation Principles
29
30	Be a conversation, not an interrogation. Ask one question at a time. Follow threads. Reflect back: "So the real issue sounds like X — is that right?" Watch for what they skip — that's where the real story lives. Never read a list of questions.
31
32	Open with: "Tell me about the company in your own words — what are you building and why does it matter?"
33
34	---
35
36	## 7 Interview Dimensions
37
38	### 1. Company Identity
39	Capture: what they do, who it's for, the real founding "why," one-sentence pitch, non-negotiable values.
40	Key probe: "What's a value you'd fire someone over violating?"
41	Red flag: Values that sound like marketing copy.
42
43	### 2. Stage & Scale
44	Capture: headcount (FT vs contractors), revenue range, runway, stage (pre-PMF / scaling / optimizing), what broke in last 90 days.
45	Key probe: "If you had to label your stage — still finding PMF, scaling what works, or optimizing?"
46
47	### 3. Founder Profile
48	Capture: self-identified superpower, acknowledged blind spots, archetype (product/sales/technical/operator), what actually keeps them up at night.
49	Key probe: "What would your co-founder say you should stop doing?"
50	Red flag: No blind spots, or weakness framed as a strength.
51
52	### 4. Team & Culture
53	Capture: team in 3 words, last real conflict and resolution, which values are real vs aspirational, strongest and weakest leader.
54	Key probe: "Which of your stated values is most real? Which is a poster on the wall?"
55	Red flag: "We have no conflict."
56
57	### 5. Market & Competition
58	Capture: who's winning and why (honest version), real unfair advantage, the one competitive move that could hurt them.
59	Key probe: "What's your real unfair advantage — not the investor version?"
60	Red flag: "We have no real competition."
61
62	### 6. Current Challenges
63	Capture: priority stack-rank across product/growth/people/money/operations, the decision they've been avoiding, the "one extra day" answer.
64	Key probe: "What's the decision you've been putting off for weeks?"
65	Note: The "extra day" answer reveals true priorities.
66
67	### 7. Goals & Ambition
68	Capture: 12-month target (specific), 36-month target (directional), exit vs build-forever orientation, personal success definition.
69	Key probe: "What does success look like for you personally — separate from the company?"
70
71	---
72
73	## Output: company-context.md
74
75	After the interview, generate `~/.claude/company-context.md` using `templates/company-context-template.md`.
76
77	Fill every section. Write `[not captured]` for unknowns — never leave blank. Add timestamp, mark as `fresh`.
78
79	Tell the founder: "I've captured everything in your company context. Every advisor will use this to give specific, relevant advice. Run /cs:update in 90 days to keep it current."
80
81	---
82
83	## /cs:update — Quarterly Refresh
84
85	Trigger: Every 90 days or after a major change. Duration: ~15 minutes.
86
87	Open with: "It's been [X time] since we did your company context. What's changed?"
88
89	Walk each dimension with one "what changed?" question:
90	1. Identity: same mission or shifted?
91	2. Scale: team, revenue, runway now?
92	3. Founder: role or what's stretching you?
93	4. Team: any leadership changes?
94	5. Market: any competitive surprises?
95	6. Challenges: #1 problem now vs 90 days ago?
96	7. Goals: still on track for 12-month target?
97
98	Update the context file, refresh timestamp, reset to `fresh`.
99
100	---
101
102	## Context File Location
103
104	`~/.claude/company-context.md` — single source of truth for all C-suite skills. Do not move it. Do not create duplicates.
105
106	## References
107	- `templates/company-context-template.md` — blank template for output
108	- `references/interview-guide.md` — deep interview craft: probes, red flags, handling reluctant founders
109