# Storytime Bootstrap

> This skill should be used when the user asks to "bootstrap storytime", "set up storytime", "init storytime", "initialize the team structure", or wants to prepare a repository for storytime use. Creates the .storytime/ directory structure and chooses the operating mode.

- Skill: `1ps0/storytime-bootstrap` (Agent Skill)
- Install (CLI): `npx skillmds@latest add 1ps0/storytime-bootstrap`
- Raw SKILL.md: https://api.skillmd.com/api/skills/1ps0/storytime-bootstrap/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: 1ps0 (https://skillmd.com/u/1ps0)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/1ps0/storytime-bootstrap

---


<!-- version-echo: display "storytime v1.0.1" at start of execution -->
# Storytime Bootstrap

Set up the storytime structure in a repository. Detect what exists,
choose an operating mode, and create the directory tree.

## Arguments

Optional mode override: $ARGUMENTS

## Process

### 1. Detect the Landscape

Scan the repo to understand what already exists:
- Does `specs/.storytime/` exist? → already bootstrapped
- Does the repo have its own doc structure (`team/`, `docs/`, `specs/`)? → established conventions
- Is this a fresh repo with minimal structure? → clean slate
- Are there other spec systems (`.kiro/`, ADRs, etc.)? → coexistence needed

### 2. Choose Mode

Present the three modes with a recommendation based on what was found:

**Storytime-native** (recommended for new or lightly-structured repos):
- Full `.storytime/` directory tree
- Sessions, cohort, archive, history all under one root
- Maximum storytime functionality

**Adapt-in-place** (recommended for repos with established conventions):
- Work within the repo's existing doc structure
- Write team docs where team docs already live
- Write plans where plans already live
- Create a minimal `.storytime/config.md` to track mode and settings

**Export-only** (for one-shot use or feeding other systems):
- No persistent storytime state
- Produce output files wherever the user specifies
- No cohort, no archive, no history

If the user provided a mode argument, use it. Otherwise recommend based
on the landscape and ask.

### 3. Create Structure

**All modes — run the mechanical floor first (BOARD-020):**
```bash
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/bootstrap_repo.py --repo . --mode <chosen mode>
```
Idempotent, never overwrites: creates the mode's directories,
`config.md` (only if absent), and the ignore block (only if missing).
The sections below describe what it writes plus the mode-specific
extras this skill still handles (adapt-mode `output_paths` detection).

**Storytime-native:**
```bash
mkdir -p specs/.storytime/{sessions,cohort,specialists,archive/{current,rollups,cold},history/sessions}
```

Write `specs/.storytime/config.md`:
```yaml
mode: native
created: <YYYY-MM-DD>
default_mode: inline
automation: guided
team_size: project-appropriate   # bias small; sized to the work
max_team_size: 12                # hard ceiling, override required
default_core: [owner, operator, critic]
naming: codename                 # non-human by default
driving_persona: required        # one driver per leg
require_nongoals: true
visual_style: ascii
citation_format: "file:line — snippet"
```

**Adapt-in-place:**

Write `specs/.storytime/config.md` (minimal):
```yaml
mode: adapt
created: <YYYY-MM-DD>
output_paths:
  team: <detected team doc location>
  specs: <detected spec location>
  plans: <detected plan location>
  archive: specs/.storytime/archive/
```

Create only `specs/.storytime/` and `specs/.storytime/archive/` — the
rest uses existing directories.

**Export-only:**

Write `specs/.storytime/config.md` (minimal):
```yaml
mode: export
created: <YYYY-MM-DD>
```

No other directories created.

**All modes with persistent state (native, adapt) — ignore block:**

Append to the repo's `.gitignore` (create it if absent). User-local
state never commits (BOARD-016); derived board state is fold-owned and
regenerable (FIX-004):

```gitignore
# storytime: user-local state (BOARD-016) + derived board state (FIX-004)
specs/.storytime/cohort/_user.md
specs/.storytime/cohort/operator-model-*.md
specs/.storytime/intents.md
specs/.storytime/commands.jsonl
board/state.json
```

### 4. Report

Show what was created and what the next step is:
- "Run `/storytime:storytime <problem>` to start your first session"
- "Run `/storytime:survey` to scan the codebase first"
- "Run `/storytime:consolidate` to organize existing docs"
- "Run `python3 ${CLAUDE_PLUGIN_ROOT}/scripts/board_server.py --repo .`
  for the live board — board.html serves from the plugin (BOARD-018),
  state.json folds from this repo"
- Verify: `python3 ${CLAUDE_PLUGIN_ROOT}/scripts/fold.py --check --repo .`
  — the board-readiness gate (BOARD-019); expect `ready` or
  `ready (empty)` on a fresh bootstrap

## If Already Bootstrapped

If `specs/.storytime/` exists, report current state instead of re-creating:
- Mode in use
- Number of personas in cohort
- Number of sessions
- Archive contents
- Suggest `/storytime:status` for a full dashboard