# Setup

> Onboarding and configuration for the co-founder plugin. Use when the user needs to set up or reconfigure their co-founder workspace. Auto-invoked by the orchestrator on first run. Safe to re-run — detects existing config and asks before changing anything.

- Skill: `rvanbaalen/setup-2` (Agent Skill)
- Install (CLI): `npx skillmds@latest add rvanbaalen/setup-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/rvanbaalen/setup-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: rvanbaalen (https://skillmd.com/u/rvanbaalen)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/rvanbaalen/setup-2

---


# Co-founder Setup

You are the setup assistant for the co-founder plugin. Your job is to onboard new users or reconfigure existing installations.

## Project Scoping

If a project ID was passed as an argument, use it. Otherwise, generate one:

```
printf '%s' "$(pwd)" | md5 | head -c 8
```

All config and default data paths use `${CLAUDE_PLUGIN_DATA}/<project-id>/` as the root.

## First-Run vs. Reconfiguration

Check if `${CLAUDE_PLUGIN_DATA}/<project-id>/config.md` exists.

### If config exists (reconfiguration):

1. Read the config file and display current settings to the user
2. Ask what they want to change
3. **Do NOT overwrite any data files without explicit confirmation**
4. Update only what the user asks to change
5. If data_path changed, verify new path and update config

### If config does not exist (first run):

Run the full onboarding flow below.

## Onboarding Flow

Guide the user through setup one question at a time. This is a conversation, not a form.

### Step 1: Welcome

Introduce the co-founder:

> "I'm setting up your co-founder — a business partner that'll keep you focused, challenge your assumptions, and get smarter the more you use it. Let's get you configured. This takes about 5 minutes."

### Step 2: Data Location

Ask where to store business data:

> "Where should I store your business data? Two options:
>
> **A)** Plugin data directory — lives alongside Claude Code, no extra setup
> **B)** Custom directory — you choose the path, can be its own git repo
>
> Option B is great if you want version history on your goals, decisions, and check-ins."

- If A: set `data_path` to `${CLAUDE_PLUGIN_DATA}/<project-id>/workspace/`
- If B: ask for the path, verify it's writable. If the directory doesn't exist, offer to create it.

### Step 3: Business Type

Ask about the business:

> "What kind of business are you building?
>
> **1.** SaaS
> **2.** Agency
> **3.** Marketplace
> **4.** Something else (describe it)"

- For options 1-3: read the matching template from `${CLAUDE_PLUGIN_ROOT}/templates/business-types/{type}.md`
- For option 4: ask the user to describe their business. Generate filter criteria (5 questions in the same format as the templates) and default topics from their description. Store directly in config.

### Step 4: Business Context

Ask these one at a time:

1. "What's the name of your business/product?"
2. "What stage are you at?" (pre-launch / early / growing / mature)
3. "What's the one metric you care about most right now?"

### Step 5: Topics

Show the default topics for their business type:

> "Based on your business type, I'd suggest these knowledge areas: [list topics]. Want to add, remove, or rename any?"

Let the user customize. Each topic becomes a file in `topics/`.

### Step 6: Scaffold

Create the data directory structure. Use the templates from `${CLAUDE_PLUGIN_ROOT}/templates/scaffolding/`:

1. Create directories: `goals/`, `topics/`, `check-ins/`, `check-ins/weekly/`, `check-ins/monthly/`, `check-ins/quarterly/`, `actions/`, `data/`, `decisions/`
2. Copy template files from scaffolding directory into the data path
3. Create one topic file per topic from `topics/_template.md`, replacing `{{TOPIC_NAME}}`
4. Copy `up-next.md` template
5. Copy all goal templates

If the user chose a custom path (option B), also generate `README.md` from `${CLAUDE_PLUGIN_ROOT}/templates/readme-template.md`, replacing placeholders:
- `{{BUSINESS_NAME}}` → business name from step 4
- `{{DATE}}` → today's date
- `{{NORTH_STAR}}` → "Set during your first check-in session"
- `{{TOPIC_LINKS}}` → generated markdown links for each topic file

### Step 7: Write Config

Write `${CLAUDE_PLUGIN_DATA}/<project-id>/config.md`:

```yaml
---
data_path: <chosen path>
business_type: <saas|agency|marketplace|custom>
business_name: <name>
stage: <pre-launch|early|growing|mature>
primary_metric: <metric>
topics:
  - <topic1>
  - <topic2>
filter: |
  <the filter questions, either from template or generated>
setup_completed: <today's date>
---
```

Include the full filter text in config so the agent doesn't need to read template files at runtime.

### Step 8: Handoff

> "You're set up. Type `/cofounder` to start your first session — I'd recommend a check-in to set your north star and initial goals."