titan-official-plugin-workflow-builder

To add a new Titan plugin workflow, implement it under the plugins/titan-plugin-*/titan_plugin_*/workflows/ directory. You must reuse existing steps, operations, and clients to maintain consistency, and register new plugin steps via the get_steps() method to ensure proper execution.

You must update public documentation whenever Titan plugin capabilities change. This synchronization ensures that new workflows or modifications to public APIs are accurately reflected in the official docs, maintaining alignment with the official plugin architecture standards.

Yes, you should reuse and extend existing plugin steps, operations, and services. This approach minimizes code duplication and maintains architectural consistency across official Titan plugins inside the titan-cli repository.

Plugin steps in a Titan workflow are registered using the get_steps() method. This registration is required to ensure the titan-cli correctly recognizes and executes the newly added or updated workflow steps within the official plugin architecture.

Titan plugin workflows must be implemented inside the plugins/titan-plugin-*/titan_plugin_*/workflows/ directory path. This specific structure ensures the workflow integrates seamlessly with the official Titan plugin architecture inside the titan-cli repository.

Yes, updating a Titan plugin workflow requires updating public docs if the capability changes. This process enforces that any new public APIs or workflow modifications are properly documented to reflect the current official plugin capabilities.