Claude Skill

ca-decompose

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

LLM Mart · 0 points · 15 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download arbiterForge-codeArbiter-plugins_ca-codex_skills_ca-decompose-bc9c216.zip · 1 KB

arbiterforge/codearbiter 145 7 forks AGPL-3.0 Updated 7d ago

Part of arbiterforge/codearbiter — 238 skills

Install

skills CLI npx skills add https://github.com/arbiterForge/codeArbiter/tree/main/plugins/ca-codex/skills/ca-decompose

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-decompose — greenfield populate

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; continue with the unchanged greenfield workflow below.

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) — 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 ( 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  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  until every required doc is present and non-empty.

Files (codearbiter)

SKILL.md 2.1 KB

---
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.