init

Prompt file imported from cloudrepo-io/founder-os (.claude/commands/init.md). Fill in {{PLACEHOLDER}} before use. Copyright stays with the author.

Initialize founder-os

Welcome to founder-os! This wizard will set up your AI team in a few simple steps.

Phase 1: Company Basics

Ask the user:

Question 1: "What is your company name?" Record as COMPANY_NAME.

Question 2: "What is your product name?" Record as PRODUCT_NAME.

Question 3: "Describe your product in one sentence." Record as PRODUCT_DESCRIPTION.

Phase 2: Company Type

Use AskUserQuestion:

• Question: "What type of company are you building?"
• Options:
  • "SaaS" - Software as a Service product
  • "Agency" - Development or consulting agency
  • "Marketplace" - Two-sided marketplace
  • "Content" - Content or media business
  • "Consulting" - Professional services

Record answer as COMPANY_TYPE.

Phase 3: Tech Stack

Use AskUserQuestion for each:

3.1 Primary Language

• Question: "What is your primary programming language?"
• Options:
  • "TypeScript (Recommended)" - Modern, type-safe JavaScript
  • "Python" - Great for ML, scripting, backends
  • "Go" - Fast, simple, great for infrastructure
  • "Rust" - Performance-critical systems
  • "Java" - Enterprise applications
  • "Ruby" - Rapid development

Record as PRIMARY_LANGUAGE.

3.2 Frontend Framework

• Question: "What frontend framework do you use?"
• Options:
  • "React (Recommended)" - Most popular, large ecosystem
  • "Vue" - Progressive, approachable
  • "Angular" - Enterprise-ready, batteries included
  • "Svelte" - Compile-time, minimal runtime
  • "None" - No frontend / API only

Record as FRONTEND_FRAMEWORK.

3.3 Backend Framework

• Question: "What backend framework do you use?"
• Options:
  • "Node.js (Recommended)" - JavaScript runtime
  • "Django" - Python, batteries included
  • "FastAPI" - Python, modern async
  • "Go (stdlib)" - Go standard library
  • "Rails" - Ruby, rapid development
  • "Spring" - Java, enterprise

Record as BACKEND_FRAMEWORK.

3.4 Database

• Question: "What is your primary database?"
• Options:
  • "PostgreSQL (Recommended)" - Reliable, feature-rich relational
  • "MySQL" - Popular relational database
  • "MongoDB" - Document database
  • "DynamoDB" - AWS managed NoSQL
  • "Supabase" - Postgres with extras
  • "SQLite" - Simple, embedded

Record as DATABASE.

3.5 Cloud Provider

• Question: "What cloud provider do you use?"
• Options:
  • "AWS (Recommended)" - Most comprehensive
  • "GCP" - Google Cloud Platform
  • "Azure" - Microsoft cloud
  • "Cloudflare" - Edge-first
  • "Vercel" - Frontend-focused
  • "Self-hosted" - Own infrastructure

Record as CLOUD_PROVIDER.

Phase 4: Team Selection

Use AskUserQuestion with multiSelect:

• Question: "Which AI team members do you want to start with? (You can add more later with /team:add)"
• Options:
  • "Software Architect (Recommended)" - System design and technical decisions
  • "Product Manager (Recommended)" - Product strategy and prioritization
  • "Engineer" - Implementation across any stack
  • "GTM Director" - Go-to-market strategy
  • "Content Strategist" - Content creation and copywriting
  • "Technical Writer" - Documentation
  • "Sales Advisor" - Sales strategy and coaching
  • "API Tester" - API testing and automation
  • "Security Engineer" - Security testing and vulnerability discovery

Map selections to agent types:

• "Software Architect" → staff-software-architect
• "Product Manager" → staff-product-manager
• "Engineer" → staff-engineer
• "GTM Director" → staff-gtm-director
• "Content Strategist" → staff-content-strategist
• "Technical Writer" → staff-technical-writer
• "Sales Advisor" → staff-sales-advisor
• "API Tester" → staff-api-tester
• "Security Engineer" → staff-security-engineer

Record as SELECTED_AGENTS.

Phase 5: Market Context

Ask the user:

Question 1: "Who are your main competitors? (comma-separated, or 'none' if greenfield)" Record as COMPETITORS.

Question 2: "What are your 1-3 key differentiators? (what makes you special)" Record as DIFFERENTIATORS.

Question 3: "Who is your target customer? (describe in 1-2 sentences)" Record as TARGET_CUSTOMERS.

Phase 6: Generate Configuration

1. Write company.yaml with all collected values:

company:
  name: "{COMPANY_NAME}"
  product: "{PRODUCT_NAME}"
  description: "{PRODUCT_DESCRIPTION}"
  type: "{COMPANY_TYPE}"

tech:
  primary_language: "{PRIMARY_LANGUAGE}"
  frontend: "{FRONTEND_FRAMEWORK}"
  backend: "{BACKEND_FRAMEWORK}"
  database: "{DATABASE}"
  cloud: "{CLOUD_PROVIDER}"

market:
  target_customers:
    - "{TARGET_CUSTOMERS}"
  competitors:
    # (parse COMPETITORS into list)
  differentiators:
    # (parse DIFFERENTIATORS into list)

team:
  enabled_agents: []  # Will be populated by /team:add

2. Initialize empty queue files (if not already present):

   • .claude/queue/active.json with {"items": []}
   • .claude/queue/backlog.json with {"items": []}
   • Ensure .claude/queue/plans/ directory exists (create .gitkeep if needed)

3. Initialize team.json (if not already present):

   • .claude/team.json with {"version": "1.0", "agents": []}

4. For each selected agent, run the /team:add logic internally:

   • Read template from .claude/agents/_templates/{agent-type}.md
   • Replace all {{PLACEHOLDER}} values with company context
   • Write instantiated agent to .claude/agents/{agent-type}.md
   • Add agent to .claude/team.json
   • Add to team.enabled_agents in company.yaml

5. Generate root CLAUDE.md from template:

   • Replace company/product placeholders
   • List enabled agents in team section
   • Include tech stack in architecture section

6. Initialize learnings/codebase.md with empty sections

Phase 7: Confirmation

Display summary:

# founder-os Initialized!

## Company
- Name: {COMPANY_NAME}
- Product: {PRODUCT_NAME}
- Type: {COMPANY_TYPE}

## Tech Stack
- Language: {PRIMARY_LANGUAGE}
- Frontend: {FRONTEND_FRAMEWORK}
- Backend: {BACKEND_FRAMEWORK}
- Database: {DATABASE}
- Cloud: {CLOUD_PROVIDER}

## Your Team ({count} members)
- staff-software-architect ✓
- staff-product-manager ✓
- ...

## Next Steps
1. Review your team: `/team:list`
2. Add work to the queue: `/queue:add`
3. Or investigate first: `/queue:research`
4. Start working: `/queue:work`
5. Check your dashboard: `/founder:dashboard`

You're ready to build with your AI team!

Error Handling

If any step fails:

• Report the specific error
• Suggest how to fix it
• Offer to retry that step

If company.yaml already exists:

• Ask if user wants to reconfigure or keep existing
• If reconfigure, backup old config first