luigidemasi opened a new issue, #37: URL: https://github.com/apache/camel-kit/issues/37
> Imported from [luigidemasi/camel-kit#65](https://github.com/luigidemasi/camel-kit/issues/65), opened by [luigidemasi](https://github.com/luigidemasi) on 2026-05-12. > Closed by commit [05e6fdd](https://github.com/luigidemasi/camel-kit/commit/05e6fdd9f83eef436796055d3432e6b9868a44c5). --- ## Parent Issue Part of luigidemasi/camel-kit#61 (Pipeline file-based handoff and clean-context invocability) — Sub-issue C. Depends on: luigidemasi/camel-kit#63, luigidemasi/camel-kit#64 ## Description Wire file-based I/O into the reclassified pipeline, enabling session resilience and CI/CD integration: 1. **Standalone mode detection** — add to brainstorm, plan, execute, validate skills: when no conversation context exists, read input from files in `docs/camel-kit/<PIPELINE_ID>/` 2. **Dual-mode invocation** — chained mode (auto-invoke, HARD-RULEs preserved) + standalone mode (reads from files) 3. **Staleness markers** — implement `⚠️ STALE` markers in brainstorm amend flow when upstream artifacts change 4. **camel-ship --resume staleness detection** — detect staleness markers and re-run stale stages on resume 5. **Re-iteration support** — `/camel-brainstorm <PIPELINE_ID>` amends existing pipeline, marks downstream docs stale ## Acceptance Criteria - [ ] Each pipeline skill can detect and read from file-based artifacts - [ ] Standalone invocation works (skill reads input from files, writes output to files) - [ ] Chained invocation still works (HARD-RULEs preserved) - [ ] Staleness markers embedded in downstream docs when upstream changes - [ ] `camel-ship --resume` detects and re-runs stale stages - [ ] Update documentation in `docs/` (architecture.md, commands.md, user-guide.md) to reflect file-based handoff and standalone mode - [ ] `./mvnw clean install -B` passes -- 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]
