/install - Space-Agents Installation

Install Space-Agents in the current project. Creates the directory structure and initializes Beads for issue tracking.

Trigger

User runs /install or is prompted from /launch when system not found.

Prerequisites

• bd CLI must be available on the system (v0.47.0+)
• Write permissions for current directory

Installation Steps

Step 1: Check for Existing Installation

if [ -d ".space-agents" ]; then
    # Check version or offer upgrade
fi

If .space-agents/ already exists:

1. Check if .beads/issues.jsonl exists
2. Ask user: Reinstall/upgrade or Cancel
3. If reinstall: backup existing data, proceed with fresh install
4. If cancel: exit gracefully

Step 2: Create Directory Structure

Create the full Space-Agents directory structure:

mkdir -p .space-agents/comms
mkdir -p .space-agents/exploration/{ideas,planned}
mkdir -p .space-agents/mission/{staged,complete}

Directory structure:

.space-agents/
├── comms/
│   └── capcom.md            # Master CAPCOM log (append-only)
├── exploration/             # Exploration kanban
│   ├── ideas/               # Early brainstorming
│   └── planned/             # Has plan.md, ready for Beads
└── mission/                 # Mission execution tracking
    ├── staged/              # Converted to Beads, ready to execute
    └── complete/            # Done

Step 3: Initialize Beads

Initialize Beads for issue tracking (if not already done):

# Initialize Beads if not already done
if [ ! -f ".beads/issues.jsonl" ]; then
    bd init
fi

Beads provides:

• Git-backed issue tracking with .beads/issues.jsonl
• Dependency management between tasks
• Context persistence across session compaction

Step 4: Create Initialization Files

Create empty/default files:

.space-agents/comms/capcom.md:

# CAPCOM Master Log

*Append-only. Grep-only. Never read fully.*

---

## [YYYY-MM-DD HH:MM] System Initialized

Space-Agents installed. HOUSTON standing by.

---

Step 5: Display Installation Complete

Show the installation success screen:

┌────────────────────────────────────────────────────────────────┐
│  ███████╗██████╗  █████╗  ██████╗███████╗                      │
│  ██╔════╝██╔══██╗██╔══██╗██╔════╝██╔════╝                      │
│  ███████╗██████╔╝███████║██║     █████╗                        │
│  ╚════██║██╔═══╝ ██╔══██║██║     ██╔══╝                        │
│  ███████║██║     ██║  ██║╚██████╗███████╗                      │
│  ╚══════╝╚═╝     ╚═╝  ╚═╝ ╚═════╝╚══════╝                      │
│           █████╗  ██████╗ ███████╗███╗   ██╗████████╗███████╗  │
│          ██╔══██╗██╔════╝ ██╔════╝████╗  ██║╚══██╔══╝██╔════╝  │
│          ███████║██║  ███╗█████╗  ██╔██╗ ██║   ██║   ███████╗  │
│          ██╔══██║██║   ██║██╔══╝  ██║╚██╗██║   ██║   ╚════██║  │
│          ██║  ██║╚██████╔╝███████╗██║ ╚████║   ██║   ███████║  │
│          ╚═╝  ╚═╝ ╚═════╝ ╚══════╝╚═╝  ╚═══╝   ╚═╝   ╚══════╝  │
├────────────────────────────────────────────────────────────────┤
│          INSTALLATION COMPLETE. HOUSTON standing by.           │
├────────────────────────────────────────────────────────────────┤
│  Created:                                                      │
│    ✓ .space-agents/ directory structure                        │
│    ✓ Beads initialized (.beads/)                               │
│    ✓ CAPCOM master log                                         │
├────────────────────────────────────────────────────────────────┤
│  Next step: Run /launch to start a session                     │
└────────────────────────────────────────────────────────────────┘

Error Handling

If bd CLI not found:

ERROR: bd CLI is required but not found.

Please install Beads CLI (v0.47.0+):
  npm install -g beads-cli

Verify installation:
  bd --version

If directory creation fails:

ERROR: Could not create .space-agents/ directory.

Check that you have write permissions for the current directory.

If already installed:

Space-Agents is already installed in this project.

What would you like to do?
  [1] Reinstall (backup existing data)
  [2] Cancel

Summary

The /install skill:

1. Checks for existing installation
2. Creates directory structure (comms/, exploration/ with kanban folders)
3. Initializes Beads for issue tracking
4. Creates CAPCOM master log
5. Displays installation complete screen
6. Guides user to run /launch

Run once per project. After installation, use /launch to start sessions.