skills.rest
asuridev
asuridevCOMMUNITY
Explore all skills by this author →
GitHub

ddd-step2-refine

Refine a Bounded Context's tactical design by adjusting artifacts and validating business invariants.

Updated Apr 23, 2026
Search Tags:#validation#ddd#domain-driven-design#flows#contracts#bounded-context#tactical-design
One-click install
npx skills add https://github.com/asuridev/dsl-design-system --skill ddd-step2-refine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ddd-step2-refine
Source: https://github.com/asuridev/dsl-design-system/tree/main/src/skills/ddd-step2-refine
Command: npx skills add https://github.com/asuridev/dsl-design-system --skill ddd-step2-refine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Refine the tactical design of a Bounded Context by surgically adjusting artifacts and validating internal coherence with business invariants, ensuring alignment with the existing architectural baseline.

Core Features & Use Cases

  • Dual-voice analysis: two expert perspectives (business domain and senior DDD engineer) to detect design gaps and invariants.
  • Coherence validation: verify alignment with Step 1, architecture/system constraints, and open-api/async-api contracts.
  • Change orchestration: propose surgical edits (to bc.yaml, aggregates, domain rules) and provide actionable guidance for flows and diagrams.
  • Audit and questions: surface inconsistencies, missing exception flows, and surface trade-offs to the designer.

Quick Start

Begin a Step 2 refinement for the specified bounded context to surgically adjust its tactical design while preserving Step 1 coherence.

Frequently Asked Questions about ddd-step2-refine

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

FAQPage Schema
How do I refine tactical DDD design in a bounded context without breaking existing domain rules?▼

You validate bounded context coherence by verifying alignment with architecture constraints and OpenAPI/AsyncAPI contracts. Dual-voice analysis detects design gaps between business requirements and tactical implementation to surface inconsistencies.

What is the best way to audit tactical DDD artifacts for missing exception flows?▼

To correct an existing bounded context tactical model, apply surgical edits to aggregates, entities, and bc.yaml. Change orchestration proposes adjustments while preserving Step 1 coherence and validating against system architecture.

Can I validate OpenAPI and AsyncAPI contracts against my tactical domain model?▼

Yes, you can validate OpenAPI and AsyncAPI contracts against your tactical domain model. Coherence validation verifies alignment between contracts, flows, diagrams, and the bounded context's internal business invariants.

When should I not use surgical refinement for adjusting aggregates?▼

You should avoid surgical refinement of aggregates when initial bounded context design lacks a baseline. Refinement targets existing tactical models to audit domain rules, requiring prior Step 1 architectural coherence to function correctly.

Related Skills

Explore More Software Engineering Skills→
natslashnatslash

ddd-architect

Identify subdomains and bounded contexts to generate DDD architecture documents.

Community
Advanced
slussetslusset
1

domain-modeling

Translate user stories into a formal domain model with entities, value objects, and state machines.

Community
Advanced
paulinghampaulingham
1

internal-eval-validate

Validate internal-eval flows with a stubbed pipeline and managed phases.

Community
Advanced
Prathmesh2000Prathmesh2000
1

domain-driven-design

Decompose complex software domains into bounded contexts using DDD patterns.

Community
Advanced