Does this skill perform actual domain modeling?

No, this skill specifically focuses on the analysis and clarification phase. It produces the structured inputs required for modeling skills like cleanddd-modeling to function effectively.

Can I use this for existing projects?

Yes, it is highly effective for analyzing new feature requests or major changes within an existing codebase to ensure business alignment.

Where should I store the output of this skill?

It is recommended to save the output in an 'analysis/requirements.md' file within your repository for easy reference by Claude and other developers.

What kind of output can I expect from this skill?

The skill generates structured Markdown tables including Stakeholder Lists, Requirement Item Tables, Business Entity Views, and Trigger/Action tables.

CleanDDD Requirements Analyst

Name: CleanDDD Requirements Analyst
Author: LDmoxeii

byLDmoxeii

•

Productivity & Workflow

Decomposes complex business requirements into structured stakeholders and entities to prepare for CleanDDD modeling.

The CleanDDD Requirements Analysis skill acts as a bridge between raw business requests and formal architectural design. It facilitates the early stages of Domain-Driven Design by clarifying scope, identifying stakeholders, and mapping requirements to business entities without prematurely jumping into implementation or complex modeling. By producing structured Markdown tables covering operational triggers, business rules, and entity responsibilities, it ensures that developers have a crystal-clear, verified foundation before proceeding to the modeling and coding phases of a project.

Key Features

01Structured 'Trigger-Action' sequence mapping for complex business logic

02Stakeholder identification and pain point mapping

032 GitHub stars

04Standardized Markdown output compatible with downstream modeling workflows

05Requirement decomposition with traceability IDs and entity categorization

06Identification of business constraints, rules, and external dependencies

Use Cases

01Bridging the gap between non-technical stakeholders and technical domain modeling

02Clarifying business rules and entity boundaries before starting a new feature refactor

03Transforming messy meeting notes or PRDs into structured developer specifications

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add ldmoxeii/only-danmuku cleanddd-requirements-analysis

For use in Claude.ai and ChatGPT

Download Skill