Zeebe Hexagonal Process Automator FAQs

Question 1

What architecture does this skill follow?

Accepted Answer

The skill strictly follows Hexagonal Architecture (Ports and Adapters), generating distinct layers for inbound workers, outbound adapters, port interfaces, and application services.

Question 2

Is the generated code ready for production?

Accepted Answer

The skill generates the structural 'glue-code' and service stubs; while the wiring is production-grade, you will still need to implement the specific business logic inside the generated application services.

Question 3

Does it handle domain-driven design?

Accepted Answer

Yes, it scans your domain package for existing value objects and automatically maps process variables to domain types, creating new ones if they don't exist.

Question 4

Why does it suggest running a review-process first?

Accepted Answer

The review-process subagent ensures your BPMN model follows styleguides and best practices, preventing you from generating code for an invalid or messy process.

Question 5

Can I use this without a BPMN file?

Accepted Answer

Yes, the skill can resolve inputs from a ProcessApi Kotlin file or even a plain description, though providing a BPMN file ensures the most accurate code generation.

Zeebe Hexagonal Process Automator

Key Features

Use Cases

Zeebe Hexagonal Process Automator

Key Features

Use Cases