Claude Skill

ca-create-context

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

LLM Mart · 0 points · 15 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download arbiterForge-codeArbiter-plugins_ca-codex_skills_ca-create-context-bc9c216.zip · 1 KB
Part of arbiterforge/codearbiter — 238 skills

Install

skills CLI npx skills add https://github.com/arbiterForge/codeArbiter/tree/main/plugins/ca-codex/skills/ca-create-context
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install arbiterforge-codearbiter@llmmart
Git git clone https://github.com/arbiterForge/codeArbiter.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole arbiterforge/codearbiter collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

$ca-create-context — brownfield populate

Compatibility route. Prefer $ca-init --brownfield for new usage. This installed route remains functional under the command-route compatibility policy at includes/command-compatibility.md; continue with the unchanged brownfield workflow below.

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 $ca-decompose.

Routes to

The context-creation skill (routines/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) → $ca-status.
  • Greenfield project, no source → $ca-decompose.
  • .codearbiter/ not yet scaffolded → $ca-init first.
  • Update one doc → edit <project-root>/.codearbiter/ directly or use $ca-feature.

Hard gate

BLOCK if <!--INITIALIZED--> is already present in CONTEXT.md. BLOCK if no meaningful source exists (route to $ca-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.

Files (codearbiter)
  • SKILL.md 2.1 KB
    ---
    name: ca-create-context
    description: Brownfield back-fill — scout an existing codebase and populate .codearbiter/, then lock it initialized.
    argument-hint: (none)
    ---
    
    # $ca-create-context — brownfield populate
    
    <!-- catalog-compatibility-notice:start -->
    > Compatibility route. Prefer `$ca-init --brownfield` for new usage. This installed route remains
    > functional under the command-route compatibility policy at [includes/command-compatibility.md](../../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 `$ca-decompose`.
    
    ## Routes to
    
    The `context-creation` skill ([routines/context-creation/SKILL.md](../../routines/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`) → `$ca-status`.
    - Greenfield project, no source → `$ca-decompose`.
    - `.codearbiter/` not yet scaffolded → `$ca-init` first.
    - Update one doc → edit `<project-root>/.codearbiter/` directly or use `$ca-feature`.
    
    ## Hard gate
    
    BLOCK if `<!--INITIALIZED-->` is already present in `CONTEXT.md`. BLOCK if no meaningful source exists
    (route to `$ca-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`.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related