ddd-step1-refine

Refine strategic DDD designs by propagating changes across YAML, specs, and diagrams.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/asuridev/dsl-design-system --skill ddd-step1-refine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ddd-step1-refine
Source: https://github.com/asuridev/dsl-design-system/tree/main/src/skills/ddd-step1-refine
Command: npx skills add https://github.com/asuridev/dsl-design-system --skill ddd-step1-refine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Refines an existing strategic DDD design surgically, touching only what changes, and propagating corrections to all affected artefacts from a dual expert perspective (business domain specialist + senior DDD design engineer).

Core Features & Use Cases

  • Surgical refinement of a strategic DDD design to minimize drift across artefacts.
  • Dual-voice critique to surface business-value or technical coherence issues.
  • Automated detection of inconsistencies, ambiguities, or design errors, with controlled corrections on request.
  • Cross-artifact consistency checks and propagation through system.yaml, system-spec.md, and system-diagram.mmd.

Quick Start

Refine the Paso 1 design by describing the changes you want, and let the system apply surgical corrections across all artefacts.

Frequently Asked Questions about ddd-step1-refine

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

FAQPage Schema
How do I refine a strategic DDD design without causing drift across artifacts?

Apply surgical refinement to your DDD design to adjust only the changed parts, enforcing dual expert critique and propagating corrections to YAML, specs, and diagrams to minimize drift.

What is dual expert critique in domain-driven design refinement?

Dual expert critique evaluates DDD changes from two perspectives: a business domain specialist and a senior DDD design engineer, surfacing business-value and technical coherence issues during refinement.

How do I check cross-artifact consistency across bounded contexts and aggregates?

Run cross-artifact consistency checks before and after modifications to validate alignment across bounded contexts, aggregates, events, and integrations within your system.yaml, system-spec.md, and system-diagram.mmd files.

Can I update only specific parts of an existing DDD design when requirements shift?

Yes, you can surgically adjust only the bounded contexts, aggregates, events, and integrations that change when business requirements shift, leaving the rest of your strategic DDD design untouched.

Does DDD refinement automatically propagate changes to YAML specs and diagrams?

Yes, the refinement process automatically propagates controlled corrections to all affected artifacts, ensuring your system.yaml, system-spec.md, and system-diagram.mmd remain synchronized after any design modification.

When should I use surgical refinement for DDD corrections and audits?

Use surgical refinement for DDD corrections, validations, and audits whenever business context or requirements shift, requiring controlled adjustments across bounded contexts and integrations with consistency checks.