kata-feature-design-docs

Feature design documentation for DDD entities and OpenAPI specs is generated by applying bounded-context conventions and category templates to output canonical files with preserved cross-references. It produces entity files, OpenAPI 3.x definitions, and CloudEvents catalogs under the correct docs path.

Keeping CloudEvents documentation and OpenAPI specs consistent across bounded contexts requires enforcing canonical folder structures, filenames, and template conformance during the feature design cycle. This approach validates naming rules and outputs aligned per-context events catalogs and entity lifecycle diagrams.

To create OpenAPI definitions aligned with your bounded context, generate specifications using category templates that enforce paths ordering, schemas, parameters, and auth/idempotency headers. This ensures the generated OAS documents match the bounded context conventions and reference the correct DDD entities.

Yes, feature design doc generation enforces canonical folder structure and filenames while validating conformance to Lexis/Codex rules. It ensures DDD-classified entity files include fields, business rules, invariants, and relationships correctly structured within the specified docs directory.

You need to generate per-context events catalogs and entity lifecycle state diagrams when creating or modifying published CloudEvents for a bounded context. This process writes full CloudEvents payload examples and idempotency notes to maintain accurate event documentation during feature design.

Feature design documentation loses cross-references when files are created without enforcing canonical paths and template conformance. Generating entities, OpenAPI specs, and CloudEvents docs through bounded-context conventions validates structure and outputs the required documents with cross-references preserved.