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

ddd-step2-tactical-design

Validate bounded contexts in arch/system.yaml and generate canonical tactical design artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides Step 2 of the DDD framework to produce the tactical design of a bounded context. It validates the BC exists in arch/system/system.yaml and then generates the canonical artifacts in arch/{bc-name}/, including the domain YAML, detailed spec, flow definitions, and the OpenAPI/AsyncAPI contracts, plus the mermaid diagrams in diagrams/.

Core Features & Use Cases

  • Validates the target BC against arch/system/system.yaml to ensure it exists and is design-ready.
  • Produces the six artefacts for the Tactical Design Phase 2: BC YAML, detailed spec (use cases), flow definitions, diagrams (domain and state/sequence views), and REST/async contracts.
  • Coordinates with the two expert voices (business and engineering) to surface domain language, invariants, and design decisions, and to resolve ambiguities before drafting the design.

Quick Start

Run the Step 2 tactical design workflow to validate the BC against arch/system.yaml and generate the canonical artifacts (arch/{bc-name}/{bc-name}.yaml, arch/{bc-name}-spec.md, arch/{bc-name}-flows.md, arch/{bc-name}-open-api.yaml, arch/{bc-name}-async-api.yaml, and the diagrams under diagrams/{bc-name}-diagram*.mmd).

Frequently Asked Questions about ddd-step2-tactical-design

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

FAQPage Schema
How do I generate tactical DDD artifacts for a bounded context end-to-end?▼

To generate tactical DDD artifacts, validate your bounded context in arch/system.yaml first. This produces canonical files including domain YAML, use case specs, flow definitions, OpenAPI/AsyncAPI contracts, and mermaid diagrams for the complete tactical design.

What diagrams are produced during tactical domain-driven design?▼

Tactical domain-driven design produces mermaid diagrams under the diagrams/ directory. These include domain model views and state/sequence diagrams that visually map aggregates, value objects, and domain events for the bounded context.

How do I define aggregates, value objects, and domain events for a bounded context?▼

Defining aggregates, value objects, and domain events requires coordinating business and engineering expert voices to surface domain language and invariants. The process resolves ambiguities before drafting the design into the canonical BC YAML and detailed spec files.

Can I generate OpenAPI and AsyncAPI contracts from a tactical DDD design?▼

Yes, you can generate OpenAPI and AsyncAPI contracts from a tactical DDD design. The process outputs both REST and asynchronous API contract files alongside the domain model to define integrations for the bounded context.

Does tactical DDD design require a bounded context to be defined in system.yaml?▼

Yes, tactical DDD design requires the bounded context to be present and design-ready in arch/system/system.yaml. The workflow validates the BC against this file before generating any canonical artifacts to ensure architectural alignment.

When should I not use a full tactical DDD workflow for my bounded context?▼

You should not use a full tactical DDD workflow if your bounded context is not yet defined in arch/system.yaml. The workflow explicitly validates BC presence and readiness before generating domain models, events, and integration contracts.

Related Skills

Explore More Software Engineering Skills→
asuridevasuridev

ddd-step2-refine

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

Community
Advanced
giuseppe-trisciuogliogiuseppe-trisciuoglio
322

spring-boot-openapi-documentation

Generate OpenAPI 3.0 documentation and Swagger UI for Spring Boot 3.x applications.

Community
Advanced
zhongadamwangzhongadamwang

diagram-generatecollaboration

Generate Mermaid collaboration diagrams from domain concepts and requirements.

Community
Advanced
hachejhachej
45

grill-with-docs

Interrogate domain models to identify gaps and generate ADRs and glossaries.

Community
Intermediate