breeze

Breeze Plugin for Claude Code

A Claude Code plugin that integrates with the Breeze AI platform for functional graph management, code analysis, design analysis, and requirement tracing.

Quick Start

1. Add the marketplace

In Claude Code, run:

/plugin marketplace add accionlabs/breezeai-hubexo-plugin

This registers the marketplace from GitHub. It does not install the plugin yet.

For plugin developers / local testing, use a local-directory marketplace instead: /plugin marketplace add /absolute/path/to/breezeai-hubexo-plugin Claude Code writes "source": "directory" into known_marketplaces.json and re-installs always pull from that local path.

2. Install the plugin

/plugin install breeze@breezeai-plugins

Claude Code copies the plugin into your local plugin cache.

3. Reload (or restart) Claude Code

/reload-plugins

Plugin skills, hooks, and MCP servers are picked up. Restart only if /reload-plugins doesn't surface the skills (rare).

You can confirm everything loaded by running:

/plugin list

breeze should show as installed and enabled. The available skills will appear with the /breeze:* namespace.

4. Initialize the workspace

/breeze:project setup

This walks you through:

• Authenticating with the Breeze MCP (browser-based Keycloak sign-in; no API key to paste)
• Linking to an existing project or creating a new one
• Checking ontology status

The linked projectUuid is saved to .breeze.json in the project root (gitignored). The MCP session is authenticated separately — no credentials are stored on disk. The Keycloak token lasts roughly 7 days from the last successful sign-in; after that, any /breeze:* skill will prompt you to re-run /breeze:project auth.

Available Skills

Project management

Skill	Command	Description
Project	/breeze:project [show | list | use <name> | create <name> | auth | status | setup]	Canonical home for all project management. Sub-modes: show (no args, print active project), list (all accessible projects), use <name|uuid> (switch and persist), create <name> [--desc "..."] (create a new project and link), auth (re-authenticate MCP), status (full metadata report — alias of show), setup (full bootstrap = auth + link/create + status). The auth and setup modes handle the MCP auth handshake; all others assume an active session.
Setup Project	/breeze:setup-project	Backward-compatible alias for /breeze:project setup. Identical behavior. Prefer /breeze:project setup for new docs and prompts.

Search & analysis

Skill	Command	Description
Search	/breeze:search <query>	Smart-search across functional, design, code, and architecture graphs — routes to one or many based on query intent. Default entry point for any question about the project.
Impact Analysis	/breeze:impact-analysis [--detailed] <prompt>	Structured cross-layer impact analysis. Summary + optional detailed document with Mermaid diagrams: legend on every detailed doc, marker tables for all four ontologies, structured Risk Taxonomy (Why / Worst case / Mitigation per risk), concrete QA Test Plan as a table, Implementation Options (A/B/C with pros/cons), Multi-Service Deploy Coordination, Open Questions, Out of Scope sections, Schema-Side Impact (Data Context block) with 🔴/🟡/🟢 verdict. Pass --detailed to skip the summary and emit the full document directly.

Spec generation

Skill	Command	Description
Generate Spec	/breeze:generate-spec	Generate functional specification documents from the functional graph.

Project resolution

Every analysis skill (search, impact-analysis, generate-spec) resolves the active project for each invocation using the flow below. The full rule lives in CLAUDE.md at the plugin root — skills defer to it rather than duplicating logic.

How a skill picks the project

1. Explicit --project <uuid|name> argument anywhere in the prompt. UUIDs are used directly. Names are resolved via Call_List_Project_ (case-insensitive substring match).
2. Bare UUID anywhere in the prompt (matches the standard UUID pattern). Used directly, no lookup.
3. Natural-language hint at the start of the prompt — for <project>: ..., on <project>: ..., <project> impact: ..., in the <project> project .... Resolved the same way as --project.
4. .breeze.json fallback — the persisted default, written by /breeze:project setup / use / create.
5. If nothing matches — the skill calls Call_List_Project_, shows the accessible projects, and asks you to pick one. No hard error.