Skip to main content
ClaudeWave
Skill389 estrellas del repoactualizado today

bootstrap

# ClaudeWave: bootstrap This Claude Code skill initializes AgentOps project structures by creating or completing essential configuration files including GOALS.md, PRODUCT.md, README.md, PROGRAM.md, and .agents/ directories. Use it when setting up a new AgentOps project or filling gaps in existing repositories, with options for dry-run preview and forced recreation of artifacts.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/boshu2/agentops /tmp/bootstrap && cp -r /tmp/bootstrap/images/gemini/skills/bootstrap ~/.claude/skills/bootstrap
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# /bootstrap

> **Quick Ref:** Product/operations layer around the `ao quick-start` core seed. Progressive — bare repos get the golden path first, 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.

## External Tools

- **ao** (optional) — AgentOps CLI. Required only for optional hook activation (Step 6). Bootstrap skips hooks gracefully when missing.
- **bd** (optional, recommended) — beads CLI. Bootstrap probes for `bd` in Step 0.5 and, when missing, points the user at `scripts/install-bd.sh` with a copy-paste command. Bootstrap never installs `bd` on the user's behalf.

## Flags

| Flag | Effect |
|------|--------|
| `--dry-run` | Report what would be created without doing anything |
| `--force` | Recreate artifacts even if they already exist |

## Execution Steps

### Step 0: Detect Repo State

```bash
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_PROGRAM=$([[ -f PROGRAM.md || -f AUTODEV.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)
HAS_BD=$(command -v bd >/dev/null && echo true || echo false)
```

Classify the repo:

| State | Condition |
|-------|-----------|
| **bare** | No GOALS.md, no PRODUCT.md, no .agents/ |
| **partial** | Some artifacts present, some missing |
| **complete** | GOALS.md, PRODUCT.md, README.md, PROGRAM.md/AUTODEV.md, and .agents/ present |

If `--dry-run` is set: report the state and what would be created, including whether `bd` would be recommended (when `HAS_BD` is false), then stop. Do not proceed to Steps 1-6.

If the repo is **complete** and `--force` is not set: report "Repo is fully bootstrapped. Nothing to do." and stop.

### Step 0.5: Recommend bd

If `HAS_BD` is true: skip. Report "bd: present."

If `HAS_BD` is false: report **"bd: not installed (recommended). Install with: `bash scripts/install-bd.sh`"** and continue. Bootstrap does NOT run the installer — `bd` is optional, the user decides.

If `scripts/install-bd.sh` is absent at the repo root, drop the install hint and just report "bd: not installed (recommended). See https://github.com/steveyegge/beads".

### Step 1: GOALS.md

If `HAS_GOALS` is false (or `--force` is set):

Run the goals skill to initialize GOALS.md interactively:

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

If `HAS_GOALS` is true and `--force` is not set: skip. Report "GOALS.md exists -- skipped."

### Step 2: PRODUCT.md

If `HAS_PRODUCT` is false (or `--force` is set):

Run the product skill to generate PRODUCT.md interactively:

```
Skill(skill="product")
```

If `HAS_PRODUCT` is true and `--force` is not set: skip. Report "PRODUCT.md exists -- skipped."

### Step 3: README.md

If `HAS_README` is false (or `--force` is set) AND PRODUCT.md now exists:

Run the doc skill in README mode to generate README.md:

```
Skill(skill="doc", args="--mode=readme")
```

If `HAS_README` is true and `--force` is not set: skip. Report "README.md exists -- skipped."

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

### Step 4: Core Seed and .agents/ Structure

If `HAS_AGENTS` is false (or `--force` is set):

Prefer the CLI golden path:

```bash
ao quick-start --no-beads
```

If `ao` is unavailable, create the minimal directory structure and report the exact command to repair later:

```bash
mkdir -p .agents/learnings .agents/council .agents/research .agents/plans .agents/rpi .agents/patterns .agents/retro .agents/handoff
```

Create `.agents/AGENTS.md` if it does not exist:

```markdown
# 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` is true and `--force` is not set: skip. Report ".agents/ exists -- skipped."

If `ao` is unavailable after fallback creation: report "Core seed repair command: `ao quick-start --dry-run` after installing ao."

### Step 5: PROGRAM.md / AUTODEV.md

If `HAS_PROGRAM` is false (or `--force` is set):

Use the existing autodev CLI path:

```bash
ao autodev init "your current objective"
```

If `ao` is unavailable: do not create a placeholder. Report "PROGRAM.md skipped -- install ao, then run: `ao autodev init \"your current objective\"`."

If `HAS_PROGRAM` is true and `--force` is not set: skip. Report "PROGRAM.md/AUTODEV.md exists -- skipped."

### Step 6: Optional Hook Activation

Do not activate hooks. AgentOps 3.0 is hookless: `ao quick-start`, execution
packets, explicit validation, and knowledge compounding deliver first value
with no runtime hooks, and CI is the authoritative gate. There is no `ao`
command or flag that installs hooks — hooks were removed from the CLI.

If the user explicitly requests hooks, they are opt-in and author-it-yourself:
point them at the `hooks-authoring` skill, which scaffolds project-local hooks
into `.claude/settings.json`. Bootstrap itself never writes hooks.

If hooks were not explicitly requested: skip. Report "Hooks optional -- sk