luigidemasi opened a new issue, #43: URL: https://github.com/apache/camel-kit/issues/43
> Imported from [luigidemasi/camel-kit#75](https://github.com/luigidemasi/camel-kit/issues/75), opened by [luigidemasi](https://github.com/luigidemasi) on 2026-05-13. > Closed on 2026-09-04 without a linked pull request. --- ## Context **Source pattern:** The `context-engineering` skill in [agent-skills](https://github.com/addyosmani/agent-skills) defines structured templates for surfacing ambiguity: ``` CONFUSION: The spec says X but the existing code has Y. Options: A) Follow the spec B) Follow existing patterns C) Ask — this seems intentional → Which approach should I take? ``` ``` ASSUMPTIONS I'M MAKING: 1. [assumption about requirements] 2. [assumption about architecture] → Correct me now or I'll proceed with these. ``` ## Problem Iron Laws handle many cases (Iron Law 3: never implement without approved spec). But there's no formalized format for *specific types* of ambiguity in Camel integration work: - When two valid EIP patterns exist for the same flow - When source XML (MuleSoft/BizTalk) has an undocumented behavior - When MCP catalog returns unexpected results - When a component property has multiple valid configurations Currently, the agent either silently picks an interpretation or asks an unstructured question. ## Proposed Solution Add `CONFUSION:` and `ASSUMPTIONS:` templates to `skills/shared/` as a guide referenced by all skills. Standardize how the agent surfaces uncertainty. **Camel-specific CONFUSION examples:** ``` CONFUSION: The source MuleSoft flow uses a custom Java transformer. Camel has both a bean() processor and a process() lambda. Options: A) bean() — cleaner, but requires a named Spring bean B) process() — inline, but less testable C) Ask — the original Java class may have side effects I can't detect → Which approach should I take? ``` ## Acceptance Criteria - [ ] `skills/shared/confusion-management.md` guide created - [ ] `CONFUSION:` template with structured options format - [ ] `ASSUMPTIONS I'M MAKING:` template with numbered list format - [ ] All Tier 1 skills reference the confusion management guide - [ ] `camel-migrate` specifically uses CONFUSION for ambiguous source patterns -- 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]
