ddd-implement

One-line summary

Bridge a DDD pattern decision to concrete code by clarifying naming and invariants, then handing off to a language adapter skill.

When to use this skill

• The user already knows which pattern they want (entity, value object, aggregate, domain event, repository, factory).
• The target language is known (or can be inferred from the project).
• The user wants idiomatic scaffolding, not just prose.

When NOT to use this skill

• The user is still designing → route to ddd-design.
• The user has working code with smells → route to ddd-refactor.
• The user wants a critique of existing code → route to ddd-review.

Core content

Three steps, in order. Do not skip step 2.