decompose

Decompose concept documents into independent PRDs with acceptance criteria and dependencies.

10|2|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/dixus/claudeframework --skill decompose-dixus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decompose
Source: https://github.com/dixus/claudeframework/tree/main/.claude/skills/decompose
Command: npx skills add https://github.com/dixus/claudeframework --skill decompose-dixus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break concept documents into independent, ship-ready PRDs that can be worked on in parallel.

Core Features & Use Cases

  • Ingests all input materials from .claude/input/ and CLAUDE.md to build a concept model.
  • Identifies independent feature boundaries and outputs per-feature PRDs.
  • Generates a decomposition manifest and archives original inputs.

Quick Start

Place your concept document in .claude/input/ and run the decomposition workflow to produce PRDs, a specs manifest, and a deployment-ready plan.

Frequently Asked Questions about decompose

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

FAQPage Schema
How do I break a concept document into independent PRDs for parallel development?

Concept document decomposition identifies independent feature boundaries within your inputs and outputs discrete PRDs containing acceptance criteria, dependencies, and a deployment-ready implementation plan for parallel execution.

What is the best way to split a large product spec into ship-ready feature requirements?

Splitting a large product spec uses the decomposition workflow to generate a decomposition manifest and per-feature PRDs, enforcing structured outputs that can be shipped separately across independent feature boundaries.

How do I generate a decomposition manifest from concept inputs for product management?

Generating a decomposition manifest requires placing concept documents in the input directory and running the workflow, which ingests all input materials, builds a concept model, and outputs the manifest alongside per-feature PRDs.

Can I use this PRD decomposition workflow without any external dependencies?

Yes, this PRD decomposition workflow operates without external dependencies, independently ingesting concept inputs to identify feature boundaries and enforce structured PRD outputs with acceptance criteria.

Does the decomposition workflow preserve the original concept document inputs?

Yes, the decomposition workflow preserves original concept document inputs by saving them to an archive before generating the decomposition manifest and per-feature PRDs.

When do I need to decompose a PRD into separate ship-ready features?

You need to decompose a PRD when you have a project-wide concept document and want to identify independent feature boundaries, allowing teams to ship and work on discrete PRDs in parallel.