luigidemasi opened a new issue, #57: URL: https://github.com/apache/camel-kit/issues/57
> Imported from [luigidemasi/camel-kit#96](https://github.com/luigidemasi/camel-kit/issues/96), opened by [luigidemasi](https://github.com/luigidemasi) on 2026-06-23. > Closed by [luigidemasi/camel-kit#110](https://github.com/luigidemasi/camel-kit/pull/110), merged on 2026-06-25. --- ## Description `PlanAnalyzer` currently parses implementation plans from Markdown using regexes and computes parallel execution waves mostly from file overlap. That is useful, but too weak for reliable agent execution. Tasks can depend on each other through non-file relationships such as: - shared endpoint URIs - route IDs and `direct:` / `seda:` links - properties - schemas - generated test data - beans and processors - external services - route contracts Those logical dependencies may not appear as shared file paths, so the analyzer can incorrectly place dependent tasks in the same wave. ## Expected Behavior Execution wave analysis should use structured task metadata with both file dependencies and logical dependencies. ## Actual Behavior Wave analysis depends primarily on plan Markdown shape and shared file paths. ## Proposed Solution Keep Markdown plans for humans, but add a structured sidecar or frontmatter block for tooling, for example: ```yaml tasks: - id: 1 title: Order ingestion route files: creates: - src/main/resources/camel/order-ingestion.camel.yaml provides: routes: - order-ingestion endpoints: - direct:validate-order consumes: properties: - orders.input.dir dependsOn: [] ``` Then update `PlanAnalyzer` to consume structured metadata first and fall back to Markdown parsing for old plans. ## Acceptance Criteria - [ ] Define structured task metadata for implementation plans - [ ] Update `camel-plan` skill/template to emit the metadata - [ ] Update `PlanAnalyzer` to prefer structured metadata - [ ] Preserve backward compatibility with existing Markdown-only plans - [ ] Add tests for logical dependencies beyond shared files -- 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]
