ddd-step2-tactical-design

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).