Skip to content
Development
Command

/create-context

Brownfield back-fill — scout an existing codebase and populate .codearbiter/, then lock it initialized.

From plugin
codearbiter
14542 skills19 agents42 commands
Install
> /plugin marketplace add arbiterForge/codeArbiter

How it fires

How this command gets triggered: by you, by Claude, or both.

  • Fires itselfClaude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/create-context

Context preview

What this command does when you run it.

Brownfield back-fill — scout an existing codebase and populate .codearbiter/, then lock it initialized.

Command definition

create-context.md
description: Brownfield back-fill — scout an existing codebase and populate .codearbiter/, then lock it initialized.
argument-hint: (none)

{{CMD:create-context}} — brownfield populate

<!-- catalog-compatibility-notice:start --> > Compatibility route. Prefer `{{CMD:init}} --brownfield` for new usage. This installed route remains > functional under the command-route compatibility policy at {{PLUGIN_ROOT}}/includes/command-compatibility.md; > continue with the unchanged brownfield workflow below. <!-- catalog-compatibility-notice:end -->

Wraps an existing codebase in project state without guessing. Dispatches parallel scouts to read the repository, synthesizes their findings into the surviving `.codearbiter/` doc set, resolves gaps via a targeted interview, and locks the project initialized. No arguments — the skill reads the repo and asks only what it cannot determine.

The only permitted path to populate `.codearbiter/` when meaningful source code already exists. For a greenfield project with no source, use `{{CMD:decompose}}`.

Routes to

The `context-creation` skill (`{{PLUGIN_ROOT}}/skills/context-creation/SKILL.md`) — six gated phases: pre-flight, scout dispatch, synthesis, gap interview, write, lock. Scouts return paths, line numbers, and named values only — never raw source or secret values. The skill is canonical for the phases and their gates.

When NOT to use

  • Project already initialized (`<!--INITIALIZED-->` in `CONTEXT.md`) → `{{CMD:status}}`.
  • Greenfield project, no source → `{{CMD:decompose}}`.
  • `.codearbiter/` not yet scaffolded → `{{CMD:init}}` first.
  • Update one doc → edit `{{PROJECT_DIR}}/.codearbiter/` directly or use `{{CMD:feature}}`.

Hard gate

BLOCK if `<!--INITIALIZED-->` is already present in `CONTEXT.md`. BLOCK if no meaningful source exists (route to `{{CMD:decompose}}`). BLOCK if any scout fails to return before synthesis. BLOCK if any `[CONFIRM-NN]` exits the gap interview unresolved and undeferred. MUST NOT write `<!--INITIALIZED-->` until every gap is resolved or deferred to `open-questions.md`.

Read more
Ships withcodearbiter

When you can't trust yourself with your code base, trust Arbiter.

Get the whole plugin

Other commands on codearbiter.