decompose

Decompose uninitialized projects into durable specifications via guided multi-layer interviews.

139|7|Updated May 8, 2026
One-click install
npx skills add https://github.com/arbiterForge/codeArbiter --skill decompose-arbiterforge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decompose
Source: https://github.com/arbiterForge/codeArbiter/tree/main/plugins/ca/skills/decompose
Command: npx skills add https://github.com/arbiterForge/codeArbiter --skill decompose-arbiterforge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents vague or premature implementation by turning an uninitialized project into a durable, interview-backed specification before any code is written. It is designed to catch hidden complexity early, force concrete trade-offs, and preserve every decision across session resets.

Core Features & Use Cases

  • Greenfield project decomposition: Runs a structured six-layer interview to define vision, users, scope, technical shape, integrations, and risks.
  • Compaction-safe persistence: Writes draft layers, ADRs, plans, and project-state files to disk so work can resume after interruptions.
  • Initialization lock: Populates the project with context, standards, questions, tasks, and decisions, then marks the project initialized and returns to normal orchestration.
  • Use case: A team starts a new Claude Code repository and needs a complete, reviewable foundation before allowing implementation to begin.

Quick Start

Use the decompose skill to initialize this project from scratch and capture the full specification on disk before implementation begins.

Frequently Asked Questions about decompose

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a project specification before writing any code in Claude Code?

To decompose a greenfield project before implementation, a guided six-layer interview extracts vision, users, scope, technical shape, integrations, and risks. This process writes draft layers, ADRs, and plans to disk, creating a durable specification ready for review.

How do I preserve architecture decisions and project context across session resets?

Preserve architecture decisions across session resets by writing ADRs, draft layers, and project-state files to disk. This compaction-safe persistence ensures your specification and locked project state survive interruptions and can resume cleanly.

What is the best way to initialize a greenfield project and track unresolved questions?

Initialize a greenfield project by running a structured interview that populates context, standards, tasks, and decisions on disk. This process enforces an initialization lock and explicitly tracks unresolved questions before returning to normal orchestration.

Can I use this project decomposition workflow for manual sessions that need staged review?

Yes, project decomposition applies to manual sessions requiring staged review. It enforces on-disk persistence and ADR capture, ensuring draft layers and decisions are saved to disk for review across multiple sessions.

Does project initialization require any existing dependencies or components?

Project initialization requires no existing dependencies or components. The decompose workflow operates on an uninitialized project, turning a blank repository into a durable specification through a guided interview without external tooling.