cleanddd-requirements-analysis

Original：🇨🇳 Chinese

Translated

Requirements clarification and decomposition, identify stakeholders and label requirement items with their corresponding owners and business entities; only produce structured requirement descriptions without modeling definitions, which can be used as input for subsequent modeling

4installs

Sourcenetcorepal/cleanddd-skills

Added on2026-02-10

NPX Install

npx skill4agent add netcorepal/cleanddd-skills cleanddd-requirements-analysis

SKILL.md Content (Chinese)

View Translation Comparison →

CleanDDD Requirements Analysis Skill

For requirements clarification and decomposition prior to CleanDDD modeling, produce structured requirement descriptions (scenarios, stakeholders, business entity classification) to facilitate subsequent modeling or implementation.

Prerequisite Inputs

Business requirements/change descriptions (documents, meeting minutes or conversations) have been obtained.
When requirements are not modeled or major adjustments to existing models are needed, run this skill first before passing to cleanddd-modeling.

Workflow (Only Requirements Analysis and Structured Description, No Modeling Definitions)

Scope Acquisition and Confirmation: Collect business scenarios, roles, inputs/outputs, and constraints; follow up on missing information first.
Stakeholder Identification: List all participating roles (e.g., C-end customers, backend administrators, auditors, operations, etc.), and clarify the target object for each requirement item.
Requirement Decomposition: Split into executable items by "view/create/modify/close/asynchronous task", assign requirement IDs, and label corresponding stakeholders.
Business Entity Classification: Classify requirement items by the business entities/domain objects responsible for meeting the requirements, and record core responsibilities and constraints (no aggregation/command/event modeling).
"Do Y When X" Trigger Scenarios: Identify follow-up actions triggered by events/states/operations, record them in the format of "trigger condition → action/impact → involved roles/entities", and remain at the requirement level without entering modeling.
Constraints and Inputs/Outputs: Supplement key business rules, preconditions, dependent systems or data; label gaps and assumptions.
Summary Output and Secondary Confirmation: Present a table to the user, labeling assumptions and items to be confirmed.

Output Format (Structured Markdown)

Stakeholder Table: Role | Goals/Pain Points | Permissions/Restrictions | Remarks
Requirement Item Table: Requirement ID | Scenario Description | Stakeholder/Target | Belonging Business Entity | Operation Type (view/create/modify/close/asynchronous, etc.) | Constraints/Preconditions | Remarks/Gaps
Business Entity View: Business Entity | Covered Requirement Items | Core Responsibilities/Rules | Key Inputs/Outputs
Trigger/Follow-up Action Table: Trigger Condition (When X operation/event/state) | Follow-up Action/Impact (Do Y) | Relevant Stakeholders | Affected Business Entities | Remarks/Assumptions
Business Rules and Dependencies (Optional): Rules/Constraints | Relevant Entities | Dependent Systems/Data | Remarks
Assumptions and To-Confirm List: Item | Description | Responsible Person | Deadline/Priority

Unified Naming and Placement Conventions

Table Naming and Column Headers: Output uniformly according to the header format in the chapters to facilitate parsing by downstream skills.
Term Uniformity: This skill stays at the "requirement-level" terminology, avoiding premature introduction of modeling terms such as aggregation/commands; clearly distinguish from the terminology of
```
cleanddd-modeling
```
.
Document Location: It is recommended to save the output of this skill as
```
analysis/requirements.md
```
in the repository or have it summarized in the session records by the Agent, for easy reference by subsequent
```
cleanddd-modeling
```
.

Post-Production Reminders

Attach a "Parameter Summary + Execution Confirmation" prompt at the end of the output to facilitate subsequent confirmation or transfer to downstream modeling skills.
Clearly define unresolved issues and assumptions for smooth handover in subsequent modeling or implementation phases.