| name | onboard |
| description | Interactive setup wizard for Chairman. Configures your organization, creates departments, initializes knowledge bases and state. Run this first. |
| user-invocable | true |
| argument-hint | |
/onboard: Chairman Setup Wizard
You are setting up a new Chairman organization. Walk the user through this process conversationally, one step at a time.
Step 1: Understand the Business
Ask the user:
- What is your business? (one sentence)
- What do you sell or deliver?
- How many people work with you? (including just "me")
- What is your most acute operational pain right now?
Step 2: Design the Departments
Based on their answers, recommend 3-5 departments from this menu:
| Department | Best For |
|---|
| commercial | Sales pipeline, lead management, proposals, customer relationships |
| marketing | Content, campaigns, social media, brand, competitive intelligence |
| operations | Inventory, supply chain, logistics, process optimization |
| finance | Budgets, invoicing, pricing, financial reporting, compliance |
| after-sales | Service, support, customer retention, knowledge base |
| product | Product development, roadmap, specifications, user research |
| hr | Hiring, onboarding, culture, team development |
Let the user adjust. They know their business better than you.
Step 3: Create the Configuration
Write .chairman/config.json:
{
"name": "Company Name",
"description": "What they do",
"industry": "Their industry",
"departments": ["commercial", "marketing", "operations"],
"created": "YYYY-MM-DD",
"chairman": "User's name",
"trust_level": "new",
"model_tier": {
"strategic": "opus",
"execution": "sonnet",
"triage": "haiku"
}
}
Step 4: Create Department Directories
For each department, create:
departments/{name}/
knowledge/
overview.md # Department scope, responsibilities, boundaries
contacts.md # Key contacts, vendors, partners (user fills in)
processes.md # Current processes (user fills in)
Write the overview.md for each department based on what you learned about the business. Include:
- Department mission (one sentence)
- Key responsibilities (bullet list)
- Boundaries (what this department does NOT do)
- Common sub-agent tasks
Step 5: Initialize State
Write .chairman/state.json:
{
"status": "operational",
"departments_active": ["list"],
"last_session": "YYYY-MM-DD",
"pending_escalations": 0,
"active_assignments": 0
}
Step 6: First Operation
Ask the user: "What should we tackle first?" Then run the appropriate skill:
- Lead problems? Suggest
/leads
- Content gaps? Suggest
/content
- No visibility? Suggest
/briefing
- Proposals taking too long? Suggest
/proposal
Tone
Be direct and efficient. This is a setup wizard, not a sales pitch. Ask only what you need. Configure based on answers. Get them operational fast.