Skip to content
Development
Skill

/ca-decompose

Greenfield decomposition interview — a layered interview that populates .codearbiter/ and locks it initialized.

From plugin
codearbiter
14562 skills19 agents42 commands
Install
$ npx -y skills add arbiterForge/codeArbiter --skill ca-decompose --agent claude-code

How it fires

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

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/ca-decompose

Context preview

The summary Claude sees to decide when to auto-load this skill.

Greenfield decomposition interview — a layered interview that populates .codearbiter/ and locks it initialized.

SKILL.md

ca-decompose.SKILL.md
name: ca-decompose
description: Greenfield decomposition interview — a layered interview that populates .codearbiter/ and locks it initialized.
argument-hint: (none)

$ca-decompose — greenfield populate

<!-- catalog-compatibility-notice:start --> > Compatibility route. Prefer `$ca-init --greenfield` 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 greenfield workflow below. <!-- catalog-compatibility-notice:end -->

Stands up project state for a greenfield project — one with no meaningful source code yet. A senior-architect persona drives a six-layer interview eliciting purpose, scope, primary users, domain vocabulary, and architectural constraints, persisting each layer to disk so a context reset loses nothing, then writes the surviving `.codearbiter/` doc set and locks the project initialized. No arguments — the skill interviews the user (a handoff summary may be supplied freely during the interview).

The only permitted path to populate `.codearbiter/` when no meaningful source exists. For an existing codebase, use `$ca-create-context`.

Routes to

The `decompose` skill ([routines/decompose/SKILL.md](../../routines/decompose/SKILL.md)) — six gated phases: pre-flight, persona adoption, layered interview, synthesis, population, lock. The skill is canonical for the layers and their gates.

When NOT to use

  • Project already initialized (`<!--INITIALIZED-->` in `CONTEXT.md`) → `$ca-status`.
  • Existing codebase with source present → `$ca-create-context`.
  • `.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 meaningful source is detected (route to `$ca-create-context`). BLOCK if any `[CONFIRM-NN]` exits synthesis unresolved and undeferred. MUST NOT write `<!--INITIALIZED-->` until every required doc is present and non-empty.

Read more
Ships withcodearbiter

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

Get the whole plugin

Other skills on codearbiter.