ca-decompose
Greenfield decomposition interview — a layered interview that populates .codearbiter/ and locks it initialized.
npx skills add arbiterForge/codeArbiter --skill ca-decompose --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# $ca-decompose — greenfield populate 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 (`${CLAUDE_PLUGIN_ROOT}/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/` direc
- Routes to
- When NOT to use
- Hard gate
What does the ca-decompose skill do?
Greenfield decomposition interview — a layered interview that populates .codearbiter/ and locks it initialized.
How do I install it?
Run `npx skills add arbiterForge/codeArbiter --skill ca-decompose --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From arbiterForge/codeArbiter, a repository with 138 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.