Flow Spec

Recommended sections:

1. Summary (goal and scope)
2. Referenced Agreements (name + version)
3. Internal Notes (implementation constraints)
4. External Notes (integration constraints)
5. Work Specification (prep, layout, logs, deliverables, validation, publish decision, error handling)

Required execution rules

• A flow should define the success condition for installation or setup work.
• For service-building flows, the default success condition should be: the generated service can be called successfully through asactl.
• For service-building flows, the generated project should include a service usage document in the project directory, covering how to start, stop, restart, verify, and modify the service later.
• After installation or setup succeeds, the agent should explicitly ask whether the user wants to publish the service to ASAHub.