luigidemasi opened a new issue, #74:
URL: https://github.com/apache/camel-kit/issues/74

   > Imported from 
[luigidemasi/camel-kit#140](https://github.com/luigidemasi/camel-kit/issues/140),
 opened by [luigidemasi](https://github.com/luigidemasi) on 2026-07-10.
   > Closed by 
[luigidemasi/camel-kit#20](https://github.com/luigidemasi/camel-kit-web/pull/20),
 merged on 2026-07-12.
   
   ---
   
   ## Summary
   
   The [camel-kit website](https://luigidemasi.github.io/camel-kit-web/) has 
not been updated to reflect a significant number of features, agents, commands, 
and architectural decisions landed since late 2025. This issue tracks 
everything that needs to be added or corrected, grouped by priority.
   
   ---
   
   ## High Priority — Broken or Misleading Content
   
   ### `/camel-flow` references must be removed (3 pages)
   
   `/camel-flow` was removed — superseded by `/camel-start`. Three website 
pages still document it as active:
   
   - `content/reference/commands.md` — dedicated carousel step "Entry Points: 
`/camel-flow` — Greenfield shortcut"
   - `content/reference/_index.md` — lists `/camel-flow` in the command summary 
table
   - `content/architecture/skills.md` — row `flow | /camel-flow | Greenfield 
shortcut into brainstorm` in the user-invocable skills table
   
   ### `/camel-start` is the new entry point — no page exists
   
   `/camel-start` is the Tier 1 meta-router. It auto-discovers context and 
routes into the greenfield or migration pipeline. It is now the **only** 
auto-discovered entry-point command. Zero mention on the website.
   
   Needs: a page under `content/pipeline/` or `content/getting-started/`, plus 
updates to the reference command list and the skills architecture table.
   
   ### Agent count is 5 — actual count is 8
   
   `content/architecture/agents-and-traits.md` says "5 agents". Eight agent 
targets now ship: `bob`, `bob2`, `claude`, `copilot`, `gemini`, `opencode`, 
`pi`, `qwen`. Three are entirely missing from the page and generator table:
   
   - **bob2** — IBM Bob 2, now the default target, uses native subagent 
orchestration (not gates/mode switching)
   - **copilot** — GitHub Copilot CLI target 
(`.github/copilot-instructions.md`, `.github/skills/`, `.github/agents/`, 
`.github/mcp.json`, guard hooks)
   - **pi** — Pi coding agent target (`.pi/skills/`, guard policy, 
pi-mcp-adapter integration)
   
   ### Default `--ai` target and value list are stale
   
   `content/reference/commands.md` lists `--ai` values as `(bob, gemini, 
claude, qwen, opencode)` with default `bob`. Current state:
   - Default is **`bob2`**
   - Full list: `bob`, `bob2`, `claude`, `copilot`, `gemini`, `opencode`, `pi`, 
`qwen`
   
   ### `camel-kit doctor` command is undocumented
   
   `camel-kit doctor` validates workspace contracts (MCP configs, skill 
resources, templates, dispatch blocks). The website command reference only 
documents `camel-kit init` and `camel-kit graph`. Doctor is invisible.
   
   ---
   
   ## Medium Priority — Outdated Technical Content
   
   ### `/camel-debug` skill has no page
   
   `/camel-debug` is a standalone troubleshooting skill. No page or mention on 
the website. Needs at minimum a row in the skills table and an entry in the 
standalone commands reference.
   
   ### Citrus MCP is a third MCP server — never mentioned
   
   `content/architecture/mcp.md` describes exactly two MCP servers (Camel 
catalog + Knowledge search). A **third** MCP server — Citrus 
(`citrus-mcp-server:5.0.0-M2`) — is now generated into agent workspace MCP 
configs for test-generation integration. The architecture page needs a Citrus 
MCP section.
   
   Related: the website Citrus version default is `4.9.2`; current default is 
`5.0.0-M2`.
   
   ### Camel MCP tool list is stale
   
   `content/architecture/mcp.md` lists the Camel MCP catalog tools. Two changes 
not reflected:
   - `camel_catalog_eip_doc` replaced an older tool name
   - `camel_configuration_validate` is now a mandatory gate in 
`/camel-validate` stage 7.1 — a key design invariant worth surfacing
   
   ### `camel-kit doc stale` / `doc unstale` subcommands undocumented
   
   Deterministic document staleness detection CLI subcommands. Not mentioned in 
the command reference or anywhere else.
   
   ### Skills count is wrong
   
   `content/architecture/skills.md` says "11 Skills in Three Categories". 
Current count is 13 named skill directories. Count and category breakdown need 
updating.
   
   ### Bob generator description describes Bob 1 behavior, not Bob 2
   
   The generator table describes `BobGenerator → IBM Bob → .bob/gates/ + mode 
switching`. Bob 2 uses native `spawn_subagent` orchestration with `explore`, 
`general`, and `fork_context` modes — not gates or mode switching. 
Architecturally incorrect for the current default target.
   
   ### Iron Laws count is stale
   
   `content/architecture/skills.md` references "4 non-negotiable pipeline 
rules". The current count is 6 laws (MCP catalog verification, constitution 
compliance, no code without plan & design approval, spec compliance before 
quality, adversarial code review, surgical changes).
   
   ---
   
   ## Low Priority — Missing Architecture Content
   
   ### Forage catalog integration has no page
   
   Forage is now the canonical catalog for bean provisioning: version stream 
mappings in project configuration, ladder-driven catalog queries in 
`/camel-validate`, and integration with the MCP catalog discipline. This is a 
new architectural layer with no coverage on the website. Candidate: a section 
in `content/architecture/` or an extension of `content/pipeline/execute.md`.
   
   ---
   
   ## Current Supported Versions (for reference)
   
   | Runtime | Default Camel version | Supported ladder |
   |---------|----------------------|-----------------|
   | Main / JBang | 4.21.0 | 4.21.0, 4.18.3, 4.14.7 |
   | Spring Boot | 4.21.0 | 4.21.0, 4.18.3, 4.14.7 |
   | Quarkus | 4.18.2 | 4.18.2 |


-- 
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]

Reply via email to