← ClaudeAtlas

decomposesolid

Develop greenfield project context through a layered interview, preserve decisions, and initialize only after the required gates.
arbiterForge/codeArbiter · ★ 145 · AI & Automation · score 83
Install: claude install-skill arbiterForge/codeArbiter
# decompose <!-- 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 --> Spec the project before a line of code exists. Routed to at greenfield startup, or by `/decompose`. ## Pre-flight Run these ordered checks. Each passes silently or hard-stops with a routing action — never guess: 1. Read `<project-root>/.codearbiter/CONTEXT.md`. If it already carries the `<!--INITIALIZED-->` body marker on its own line, STOP — context exists. Route to normal operation. 2. Scan for meaningful source code: any file outside `.git/`, `.codearbiter/`, `.claude/`, `arbiter.md`, `AGENTS.md`, `CLAUDE.md`, `README.md`, `LICENSE`, `.gitignore`, `.gitmodules`, and standard tooling dotfiles. If any exist, STOP and route to `/create-context`. 3. Confirm `<project-root>/.codearbiter/` exists and is writable. If not, surface the gap and STOP. All three pass → proceed to Phase 1. Later phases consume this pass-status; they do not re-run it. ## Phase 1 — Persona adoption · gate: BLOCK Announce the role switch to the user, verbatim: > "Switching to decomposition mode. For this session I operate as a senior software architect and technical lead, decomposing your project vision into a c