Command Reference

Camel-Kit provides both CLI commands for project initialization and slash commands for use within your AI coding assistant. The slash commands follow a 3-phase orchestrated flow: Design → Plan → Execute.

Pipeline Commands

/camel-brainstorm — Design Phase

Design an integration through an AI-guided interview. This is Phase 1 of the pipeline and the primary entry point for all camel-kit work.

When to use: Any new integration, connecting systems, building data pipelines, or starting migration projects.

Process:

  1. Detects project type (greenfield or migration)
  2. Runs a Socratic interview: business purpose, systems, data formats, processing, error handling, performance
  3. Verifies all components via MCP catalog (Iron Law 1)
  4. Produces a formal Design Specification
  5. After user approval, automatically invokes /camel-plan

Output: docs/design-spec.md

/camel-plan — Planning Phase

Generate an implementation plan from an approved design spec. This is Phase 2 of the pipeline, auto-invoked by /camel-brainstorm after spec approval.

Process:

  1. Reads the approved design spec
  2. Decomposes into implementation tasks with acceptance criteria
  3. Runs wave analysis to identify parallelizable tasks
  4. Specifies two-stage review per task (spec compliance then quality)
  5. After user approval, automatically invokes /camel-execute

Output: docs/implementation-plan.md

Key rule: The plan is a recipe, not the meal — it describes WHAT to generate, not the generated code itself.

/camel-execute — Execution Phase

Execute the approved implementation plan with orchestrated task dispatch. This is Phase 3 of the pipeline, auto-invoked by /camel-plan after plan approval.

Process:

  1. Analyzes plan for parallel execution waves
  2. For each task: implement → spec compliance review → code quality review
  3. Loads internal skills as needed (camel-implement, camel-test, camel-validate)
  4. After all tasks complete, auto-invokes /camel-verify

Generated artifacts:

  • .camel.yaml routes
  • application.properties
  • docker-compose.yaml
  • DataMapper files (XSLT/Groovy)
  • Citrus test definitions
  • Validation report

Entry Point Commands

/camel-flow — Greenfield Shortcut

Shortcut into /camel-brainstorm for greenfield projects. Use when creating a new integration from scratch.

Immediately starts the design interview process optimized for new integrations.

/camel-migrate — Migration Shortcut

Shortcut into /camel-brainstorm for migration projects.

Supported source platforms:

PlatformVersionsDetection
MuleSoft Mule3.x, 4.xXML namespace, pom.xml groupId
Apache Camel2.x, 3.xcamel-context.xml, Spring XML, Blueprint

Features:

  • Auto-detect source vendor
  • Graph-based flow analysis
  • DataWeave parsing
  • Flow-by-flow incremental migration

Standalone Commands

/camel-verify — Runtime Verification

Runtime verification feedback loop. Builds, starts, tests, classifies errors, applies fixes, and retries until the application works.

5-phase loop:

  1. Environment — prepare Docker containers
  2. Build — Maven/Gradle compilation
  3. Start — route startup with health checks
  4. Behavioral — send test data, verify output
  5. Report — structured summary of findings and fixes

Can be invoked standalone for troubleshooting or auto-invoked by /camel-execute.

/camel-validate — Route Validation

Validate Camel routes for correctness, security, and constitution compliance. Produces timestamped validation reports.

Validation categories:

  • Schema validation
  • Endpoint verification
  • Quality checks
  • Security analysis
  • Anti-pattern detection
  • Constitution compliance (all 7 rules)

Output: docs/validation-report-YYYY-MM-DD_HH-mm.md

/camel-knowledge — Documentation Lookup

Look up Apache Camel documentation, component details, CVEs, migration guides, release notes, and JIRA issues via MCP tools.

MCP Tools:

  • camel_docs_search — general documentation search
  • camel_docs_component_info — component information + CVE lookup
  • camel_docs_cve_search — security advisory search
  • camel_docs_release_info — release notes
  • camel_docs_jira_lookup — JIRA issue lookup

CLI Commands

camel-kit init — Project Initialization

Initialize a new Camel-Kit project.

Usage:

camel-kit init <project-name> [options]
camel-kit init --here [options]

Options:

OptionDefaultDescription
--ai, -abobAI coding assistant to configure (bob, gemini, claude, qwen, opencode)
--citrus-version4.9.2Citrus Framework version for test schemas
--herefalseInitialize in current directory
--no-fetchfalseSkip external catalog fetching
--source-platformautoSource platform for migration: mulesoft, camel, auto
--silentfalseSuppress all output — useful for CI/scripted environments
-p-Override a single configuration property (e.g., -p camelVersion=4.19.0)
-c-Load configuration from a properties file (e.g., -c my-config.properties)

Examples:

# Create new project for Claude Code
camel-kit init my-integration --ai claude

# Create new project for IBM Project Bob
camel-kit init my-integration --ai bob

# Initialize in current directory
camel-kit init --here --ai claude

# Explicitly declare MuleSoft source platform
camel-kit init my-integration --ai claude --source-platform mulesoft

Output structure:

📁 my-integration/
📄 AGENTS.md Cross-agent skill routing and iron laws
📁 CLAUDE.md Agent-specific configuration (or GEMINI.md / QWEN.md)
📁 .claude/
📁 commands/ Slash commands (Claude Code)
📝 camel-brainstorm.md
📝 camel-plan.md
📝 camel-execute.md
📝 camel-verify.md
📝 camel-flow.md
📝 camel-validate.md
📝 camel-migrate.md
📝 camel-knowledge.md
📁 skills/ Skill files with guides
📄 .mcp.json MCP server configuration
📁 .camel-kit/
📄 config.properties Project configuration
📄 constitution.md Best practices (7 rules)
camel-kit graph — Property Graph Queries

Query the project’s property graph for code intelligence.

camel-kit graph stats                           # Graph availability check
camel-kit graph generate                        # Rebuild project graph
camel-kit graph find --type CAMEL_ROUTE         # Find nodes by type
camel-kit graph neighbors <node-id>             # Get connected nodes
camel-kit graph route-flow <route-id>           # Trace a route's flow
camel-kit graph dead-code                       # Detect unused code
camel-kit graph project-norms                   # Get project norms for validation
camel-kit graph project-context                 # Get context for implementation
camel-kit graph route-context <route-id>        # Get context for testing
camel-kit graph visualize                       # Generate interactive HTML visualization
camel-kit plan analyze <plan-file>              # Analyze plan for parallel execution waves

Command Cheat Sheet

# CLI
camel-kit init my-project --ai claude           # Create project
camel-kit graph stats                           # Check graph availability
camel-kit graph visualize                       # Interactive graph HTML
camel-kit plan analyze docs/implementation-plan.md  # Wave analysis

# 3-Phase Pipeline (in AI assistant)
/camel-brainstorm                # Phase 1: Design interview → design-spec.md
/camel-plan                      # Phase 2: Task decomposition → implementation-plan.md
/camel-execute                   # Phase 3: Generate code + tests + validation

# Entry Points
/camel-flow                      # Greenfield shortcut → brainstorm
/camel-migrate                   # Migration shortcut → brainstorm

# Standalone
/camel-verify                    # Runtime verification loop
/camel-validate                  # Route quality check
/camel-knowledge                 # Documentation lookup