luigidemasi opened a new issue, #45: URL: https://github.com/apache/camel-kit/issues/45
> Imported from [luigidemasi/camel-kit#77](https://github.com/luigidemasi/camel-kit/issues/77), opened by [luigidemasi](https://github.com/luigidemasi) on 2026-05-13. > Closed by [luigidemasi/camel-kit#200](https://github.com/luigidemasi/camel-kit/pull/200), merged on 2026-09-01. --- ## Context **Source pattern:** The `idea-refine` skill in [agent-skills](https://github.com/addyosmani/agent-skills) requires a `## Not Doing (and Why)` section in every design one-pager. *"The 'Not Doing' list is arguably the most valuable part. Focus is about saying no to good ideas. Make the trade-offs explicit."* ## Problem `camel-brainstorm` and `camel-design` produce specs with requirements and implementation approach. There's no formalized exclusion list. During `camel-execute`, the agent is tempted to add features that seem natural but weren't part of the approved spec — scope creep that accumulates context and delays completion. ## Proposed Solution Add a `## Not Doing (and Why)` section to the design spec template used by `camel-brainstorm`/`camel-design`: Example for a Kafka-to-PostgreSQL integration: ``` ## Not Doing (and Why) - **Dead letter queue** — Adds complexity; start with simple error logging, add DLQ in iteration 2 if needed - **Schema registry integration** — Source topic uses plain JSON, not Avro. No schema evolution concern. - **Multi-tenant partitioning** — Single tenant deployment. Partition strategy is out of scope. ``` ## Benefits - Prevents scope creep during `camel-execute` (agent references the Not Doing list before adding features) - Makes trade-offs visible at spec review time (strengthens Iron Law 3) - Aligns with pipeline file-based handoff (ADR-0031) — the Not Doing list is part of the persisted spec artifact ## Acceptance Criteria - [ ] Design spec template includes `## Not Doing (and Why)` section - [ ] `camel-brainstorm` interview process asks about scope boundaries - [ ] `camel-execute` references the Not Doing list before adding features beyond the spec - [ ] At least 3 examples of good Not Doing entries in the template -- 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]
