vibeX-domain-decomposition

Decompose user requirements into structured MVP domain lists in JSON format.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/MMXC/openclaw-back --skill vibex-domain-decomposition
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibeX-domain-decomposition
Source: https://github.com/MMXC/openclaw-back/tree/main/workspace/skills/vibeX-domain-decomposition
Command: npx skills add https://github.com/MMXC/openclaw-back --skill vibex-domain-decomposition

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of Domain-Driven Design (DDD) decomposition based on user requirements, generating a structured list of domains.

Core Features & Use Cases

  • Domain Decomposition: Analyzes user requirements to identify core, supporting, and generic domains.
  • Structured Output: Generates a JSON output detailing domain hierarchy, features, and dependencies.
  • Use Case: Input "I want to build a live streaming system" and receive a structured breakdown of domains like "Live Interaction," "User Center," and "Content Management," along with their sub-domains and features.

Quick Start

Use the vibeX-domain-decomposition skill to break down the user requirement "I want to build an e-commerce platform".

Frequently Asked Questions about vibeX-domain-decomposition

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

FAQPage Schema
How do I decompose software requirements into domains for architecture planning?

To decompose software requirements into domains, you analyze user needs using Domain-Driven Design principles to categorize and prioritize business capabilities into core, supporting, and generic domains. This generates a structured JSON output detailing domain hierarchy and features.

What is the best way to identify core and supporting domains for an MVP?

The best way to identify core and supporting domains for an MVP is to analyze user requirements through domain decomposition. This categorizes business capabilities, outputting a structured MVP domain list that distinguishes core functions from supporting and generic sub-domains.

How does domain decomposition work for a live streaming system architecture?

Domain decomposition for a live streaming system works by analyzing your requirement input and categorizing business capabilities into structured domains like Live Interaction, User Center, and Content Management, along with their respective sub-domains and features.

Can I get a structured JSON output of domain hierarchy and features from user requirements?

Yes, you can get a structured JSON output of domain hierarchy and features from user requirements. The domain decomposition process analyzes your input and renders domain categories, dependencies, and features directly into JSON format for UI rendering.

Do I need prior Domain-Driven Design knowledge to generate a domain breakdown?

No, you do not need prior Domain-Driven Design knowledge to generate a domain breakdown. The process automates DDD principles to analyze user requirements and categorize business capabilities into core, supporting, and generic domains for you.

When should I use domain decomposition for requirements analysis?

You should use domain decomposition for requirements analysis when you need to transition from raw user needs to a structured software architecture. It is ideal for generating an MVP domain list and defining business capabilities before development begins.