spec-decomposition

Decompose specifications into independent changes with dependency graphs.

39|3|Updated Nov 21, 2025

Search Tags:#planning #dependencies #epics #decomposition #change-management #spec-analysis

Ready to run

npx skills add https://github.com/LiorCohen/sdd --skill spec-decomposition

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-decomposition
Source: https://github.com/LiorCohen/sdd/tree/main/plugin/core/skills/spec-decomposition
Command: npx skills add https://github.com/LiorCohen/sdd --skill spec-decomposition

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec Decomposition identifies and isolates dense specifications into independent changes to enable modular planning, clearer ownership, and safer incremental delivery.

Core Features & Use Cases

Boundary-aware decomposition: detects natural change boundaries within a specification.
Dependency graph generation: outputs a structured graph to guide sequencing and integration.
Mode flexibility: supports outline, section, and hierarchical epic/feature decomposition for varying spec sizes.
Workflow-ready artifacts: emits structured data models (changes, epics, dependencies) for downstream tooling and automation.

Quick Start

Decompose your spec content by running this skill and review the resulting changes, dependencies, and suggested ordering.

Frequently Asked Questions about spec-decomposition

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

FAQPage Schema

How do I decompose a complex specification into independent changes?▼

To decompose a specification, extract its structure, detect change boundaries, identify dependencies, score independence, and refine the output to generate modular, boundary-defined changes. This enables modular planning, clearer ownership, and safer incremental delivery.

What is spec decomposition and when do I need it for engineering handoffs?▼

Spec decomposition isolates dense specifications into independent changes for engineering handoffs. You need it when complex documents must be broken into boundary-defined, independently implementable changes to enable modular planning and traceability.

Can I generate a dependency graph and hierarchical epics from a product spec?▼

Yes, you can generate a dependency graph and hierarchical epics from a product spec. The decomposition process supports varying spec sizes and outputs a formal artifact mapping component dependencies to guide sequencing and integration.

What is the best way to break down a dense document for modular planning?▼

The best way to break down a dense document is to apply a 5-phase decomposition process: structure extraction, boundary detection, dependency detection, independence scoring, and refinement. This yields workflow-ready artifacts for downstream tooling.

Does spec decomposition support outline and section modes for varying document sizes?▼

Yes, spec decomposition supports outline, section, and hierarchical epic modes. This mode flexibility accommodates varying spec sizes by emitting structured data models that map changes and dependencies for downstream automation.

When should I not use automated spec decomposition for change management?▼

You should avoid automated spec decomposition for change management when specifications lack defined structural boundaries or clear dependencies, as the process relies on detecting natural change boundaries to isolate independent changes.