Naming is hard... Use better names for reusable workflows.

[sfreudenthaler]

Good feedback from @spbolton. The dotcms/claude-workflows repo is poorly named. As are the specific workflow files there. We should update that before it gets used more and changing it gets harder.

@sfreudenthaler My only concern is using the tooling in the name vs the job it is doing e.g. workflow orchestrator. Could this hit us later.

Originally posted by @spbolton in https://github.com/dotCMS/infrastructure-as-code/issues/6288#issuecomment-3019651835

[sfreudenthaler]

The repository rename from claude-workflows to ai-workflows (implemented in dotCMS/infrastructure-as-code#6384) actually provides the perfect foundation to address this naming concern.

Solution: Tool-Specific Reusable Workflows

Rather than genericizing the current workflows, we can maintain tool-specific naming and add new workflows for other AI agents:

Current (Claude-specific):

• claude-orchestrator.yml - Claude-specific workflow
• claude-executor.yml - Claude-specific executor

Future expansion:

• openai-orchestrator.yml - OpenAI/GPT-specific workflow
• anthropic-orchestrator.yml - Generic Anthropic workflow
• gemini-orchestrator.yml - Google Gemini workflow
• ai-orchestrator.yml - Generic AI workflow (if needed)

Benefits

1. Addresses the naming concern - tooling in the name becomes intentional, not accidental
2. Enables tool-specific optimizations - different AI agents have different APIs, capabilities, and requirements
3. Maintains backward compatibility - existing claude-* workflows continue working
4. Supports future growth - easy to add new AI providers without breaking existing integrations
5. Clear consumer choice - repositories explicitly choose which AI tool for their workflow

This approach transforms @spbolton's concern into a feature: the tooling name indicates exactly which AI service the workflow uses, making it easier for consuming repositories to make informed choices.

The infrastructure-as-code PR laid the groundwork by establishing the ai-workflows repo as a multi-tool platform rather than a Claude-only solution.