/bootstrap

Quick Ref: One command to set up the full AgentOps product layer. Progressive — bare repos get everything, existing repos fill gaps only.

YOU MUST EXECUTE THIS WORKFLOW. Do not just describe it.

Quick Start

/bootstrap

That is it. One command. Every step below is idempotent — existing artifacts are never overwritten.

Flags

--dry-run

--force

Execution Steps

Step 0: Detect Repo State

git rev-parse --is-inside-work-tree >/dev/null 2>&1 || { echo "NOT_A_GIT_REPO"; exit 1; }
HAS_GOALS=$([[ -f GOALS.md ]] && echo true || echo false)
HAS_PRODUCT=$([[ -f PRODUCT.md ]] && echo true || echo false)
HAS_README=$([[ -f README.md ]] && echo true || echo false)
HAS_AGENTS=$([[ -d .agents ]] && echo true || echo false)
HAS_HOOKS=$(grep -q "agentops" .claude/settings.json 2>/dev/null && echo true || echo false)
HAS_AO=$(command -v ao >/dev/null && echo true || echo false)

Classify the repo:

If

--dry-run

If the repo is complete and

--force

Step 1: GOALS.md

If

HAS_GOALS

--force

Run the goals skill to initialize GOALS.md interactively:

Skill(skill="goals", args="init")

If

HAS_GOALS

--force

Step 2: PRODUCT.md

If

HAS_PRODUCT

--force

Run the product skill to generate PRODUCT.md interactively:

Skill(skill="product")

If

HAS_PRODUCT

--force

Step 3: README.md

If

HAS_README

--force

Run the readme skill to generate README.md:

Skill(skill="readme")

If

HAS_README

--force

If PRODUCT.md does not exist (Step 2 was skipped or failed): skip. Report "README.md skipped -- PRODUCT.md required first."

Step 4: .agents/ Structure

If

HAS_AGENTS

--force

Create the directory structure:

mkdir -p .agents/learnings .agents/council .agents/research .agents/plans .agents/rpi

Create

.agents/AGENTS.md

# Agent Knowledge Store

This directory contains accumulated knowledge from agent sessions.

## Structure

| Directory | Purpose |
|-----------|---------|
| `learnings/` | Extracted lessons and patterns |
| `council/` | Council validation artifacts |
| `research/` | Research phase outputs |
| `plans/` | Implementation plans |
| `rpi/` | RPI execution packets and phase logs |

## Usage

Knowledge is automatically managed by the AgentOps flywheel:
- `/inject` surfaces relevant prior knowledge at session start
- `/post-mortem` extracts and processes new learnings
- `/compile` runs maintenance (mine, grow, defrag)

If

HAS_AGENTS

--force

Step 5: Hook Activation

If

HAS_AO

HAS_HOOKS

--force

ao init --hooks

If

HAS_AO

If

HAS_HOOKS

--force

Step 6: Report

Output a summary table:

Bootstrap complete.

| Artifact      | Status  |
|---------------|---------|
| GOALS.md      | created / skipped / failed |
| PRODUCT.md    | created / skipped / failed |
| README.md     | created / skipped / failed |
| .agents/      | created / skipped / failed |
| Hooks         | activated / skipped / failed |

Repo is now AgentOps-ready. Next: /rpi "your first goal"

Examples

Bare Repo

User says:

/bootstrap

What happens: Agent detects no AgentOps artifacts. Runs /goals init, /product, /readme, creates .agents/ structure, activates hooks. Reports all five artifacts created.

Partial Repo (has GOALS.md and .agents/)

User says:

/bootstrap

What happens: Agent detects existing artifacts. Skips GOALS.md and .agents/. Runs /product, /readme. Activates hooks if needed. Reports two created, three skipped.

Dry Run

User says:

/bootstrap --dry-run

What happens: Agent detects repo state and reports what would be created. No files are written.

Troubleshooting

git init

/goals init

/bootstrap

brew tap boshu2/agentops https://github.com/boshu2/homebrew-agentops && brew install agentops

--force

See Also

• goals -- Fitness specification and directive management
• product -- Product definition generation
• readme -- README generation
• quickstart -- New user onboarding (lighter than bootstrap)