context-creationlisted

The brownfield back-fill. Routed to by /create-context, and by startup when .codearbiter/CONTEXT.md lacks the  body marker but source code exists. Six gated phases — pre-flight, scout dispatch, synthesis, gap interview, write, lock. Reads the existing codebase through parallel scouts, drafts every surviving project-state doc, resolves gaps with the user, and locks the project as initialized.
arbiterForge/codeArbiter · ★ 141 · AI & Automation · score 78

Install: claude install-skill arbiterForge/codeArbiter

# context-creation Wrap an existing codebase in project state, without guessing. Routed to by `/create-context`, and by startup when `.codearbiter/CONTEXT.md` exists but carries no `` body marker and meaningful source code is present. When no meaningful source exists, this is the wrong skill — route to `decompose` instead. This back-fills from existing source. It complements `$ca-init`, which scaffolds an empty `.codearbiter/` for a fresh project; here the docs are derived from what is already on disk. ## Pre-flight Read these, or STOP and surface the gap — never guess project identity or a command: - `<project-root>/.codearbiter/CONTEXT.md` — if it already carries ``, context exists. Stop and route to normal operation. - The repository root listing (one level deep) — the source surface this skill extracts from. The excluded set (not "meaningful source"): `.git/`, `.codearbiter/`, `.claude/`, `AGENTS.md`, `CLAUDE.md`, `README.md`, `LICENSE`, `.gitignore`, `.gitmodules`, and standard tooling dotfiles (`.editorconfig`, `.prettierrc`, etc.). Meaningful source MUST exist beyond it. ## Phase 1 — Pre-flight confirmation · gate: BLOCK Confirm the repository is a brownfield codebase safe for scout-based extraction: 1. Confirm `` is absent from `CONTEXT.md`. 2. Confirm meaningful source code is present beyond the excluded set. 3. Identify the primary source directories (`src/`, `backend/`, `frontend/`, `lib/`, `app/`, or e