Hey @nguyenthieutoan, thank you so much for the kind words! One of the biggest advantages of splitting the workflow dials back to what you mentioned. If my friend wants to add new functionality later on, I don’t have to dive back into one huge workflow and modify everything. Instead, I can simply update the relevant subworkflow or add another one without affecting the existing logic. It makes the whole setup much easier to maintain and extend over time.
The post-generation validation step was actually already on my roadmap after the first round of testing. The only reason I haven’t implemented it yet is that I wanted it to validate more than just the key values (which I completely agree is important). I also want it to check whether the generated content matches the desired tone of voice.
The challenge is that my friend is still figuring out what tone of voice he wants for the shop. So we agreed to ship the first version, let him generate content for a while, and then use that experience to define a consistent style. Once that’s clear, I’ll add the validation step to enforce both factual correctness and the desired writing style.
I completely agree with you, though. A validation layer is what separates a reliable production workflow from a generic content generator that occasionally hallucinates.