luigidemasi opened a new issue, #58: URL: https://github.com/apache/camel-kit/issues/58
> Imported from [luigidemasi/camel-kit#97](https://github.com/luigidemasi/camel-kit/issues/97), opened by [luigidemasi](https://github.com/luigidemasi) on 2026-06-23. > Closed by [luigidemasi/camel-kit#102](https://github.com/luigidemasi/camel-kit/pull/102), merged on 2026-06-24. --- ## Description Camel-Kit currently defines its workflow contract in multiple places: - Java generator command list - skill frontmatter - skill body text - generated `AGENTS.md` - MCP config templates - website/reference docs - user guide and README content This makes it easy for the product contract to drift. For example, command names, user-invocable status, pipeline transitions, internal skills, and MCP tools are not all derived from one source. ## Expected Behavior There should be one authoritative machine-readable workflow definition for commands, skills, pipeline stages, artifacts, transitions, MCP tools, and user-facing visibility. ## Actual Behavior The same information is manually duplicated across Java code and Markdown resources. ## Proposed Solution Introduce a central workflow manifest, for example `camel-kit-workflow.yaml`, containing: - command names and aliases - skill names and user-invocable/internal status - pipeline stages and transitions - stage input/output artifacts - standalone vs chained behavior - MCP servers and allowed tools - generated command stubs - website/reference metadata Then generate or validate the following from that manifest: - command stubs - generated `AGENTS.md` command list - resource consistency tests - website command tables - documentation snippets - MCP tool allowlists ## Acceptance Criteria - [ ] Add a central workflow manifest for command/stage/tool metadata - [ ] Update generator code to read or validate against the manifest - [ ] Add tests that ensure generated command stubs and skill metadata match the manifest - [ ] Document the manifest as the source of truth for future skill/workflow changes - [ ] Reduce manually duplicated command/stage/tool lists where practical -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
