Decompose specifications into independent changes with dependency graphs.
npx skills add https://github.com/LiorCohen/sdd --skill spec-decomposition
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
Spec Decomposition identifies and isolates dense specifications into independent changes to enable modular planning, clearer ownership, and safer incremental delivery.
Decompose your spec content by running this skill and review the resulting changes, dependencies, and suggested ordering.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
ReidondGuide software teams through structured specification and planning workflows before implementation.
patrickrmooreDecompose PRD and SAD artifacts into prioritized, dependency-aware epics.
evandrodevbrCreate OpenSpec change artifacts in dependency order for implementation preparation.
jaydubya818Analyze project plans to validate PRD, Architecture, Epics, and UX completeness and alignment.
