https://github.com/halfmoon-mind/fusion-council
Deterministic multi-model planning & review councils for Claude Code (Claude role panel + GPT-5.5). Installable plugin + marketplace.
https://github.com/halfmoon-mind/fusion-council
Last synced: 5 days ago
JSON representation
Deterministic multi-model planning & review councils for Claude Code (Claude role panel + GPT-5.5). Installable plugin + marketplace.
- Host: GitHub
- URL: https://github.com/halfmoon-mind/fusion-council
- Owner: halfmoon-mind
- Created: 2026-06-22T07:59:26.000Z (about 2 months ago)
- Default Branch: main
- Last Pushed: 2026-07-02T06:37:32.000Z (about 1 month ago)
- Last Synced: 2026-07-02T07:26:16.401Z (about 1 month ago)
- Language: JavaScript
- Homepage:
- Size: 1.77 MB
- Stars: 4
- Watchers: 0
- Forks: 1
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
Awesome Lists containing this project
README
# Fusion Council
Two deterministic, read-only **councils** for Claude Code that vet your work with
more than one model family before you commit to it:
- **`/fusion-council:fusion-plan `** — before a non-trivial change. A Claude
role panel (architect · skeptic · test-strategist · maintainer) plus **GPT-5.6 Sol**
deliberate in parallel; a judge compares them on merit and one plan is synthesized.
- **`/fusion-council:fusion-review`** — after the change. One generalist Claude seat
plus **GPT-5.6 Sol** review your current `git diff`, judged and synthesized → one
findings report. This duo is the bench-validated default (matched recall on the
settled case set — n=1 hard case, so recall deltas are anecdote — at ~half the
clean-diff noise and −21% cost; `EVAL.md` §B5′); pass
`args: { roles: true }` to restore the role panel (skeptic · test-strategist ·
maintainer + GPT-5.6 Sol).
Both are **read-only**: panelists may read the repo but never edit it. Only you (the
main session) implement, and only after you approve.
## Install
```
/plugin marketplace add halfmoon-mind/fusion-council # or: /plugin marketplace add /path/to/this/repo
/plugin install fusion-council@fusion-council
```
Local testing without GitHub: point the marketplace at this directory directly
(`/plugin marketplace add .` from the repo root).
## Use
```
/fusion-council:fusion-plan add rate limiting to the upload endpoint
# ...review the plan, approve, implement...
/fusion-council:fusion-review
```
## The GPT-5.6 Sol seat (optional)
The non-Claude panel seat shells out to the local **Codex CLI** (`codex exec`,
ChatGPT subscription — no metered API). If `codex` isn't installed — or a run fails
or times out — that seat drops out and the council runs Claude-only; every report's
**Council Coverage** line says so, so reduced diversity is never silent. Install
Codex CLI to enable it. The seat hands its prompt to `codex exec` on **stdin**
(the `-` / piped form, so large tasks/diffs aren't capped by `ARG_MAX`), which
needs a Codex CLI recent enough to support it (verified on v0.142.0); an older
CLI just shows up as UNAVAILABLE in Council Coverage.
## Telemetry & self-evaluation
Each run appends one compact stats row (the judge JSON, per-seat claim counts,
coverage — never full seat answers) to `~/.fusion-council/telemetry.jsonl`, so the
council's own value is measurable from real usage: per-seat surviving insights,
FP rate, cross-family agreement, and whether you actually acted on the output
(`eval/ack.sh y|n`). `eval/analyze.sh` prints the scoreboard. This is the ONE
write the otherwise read-only workflows perform — pass `noTelemetry: true` to
disable it. The full validation methodology (verified literature, seeded-bug
benchmark design, ablation arms `noGpt`/`roles`, kill metrics, and the §B5′
re-validation that made duo the review default) lives in `EVAL.md`.
## Layout
```
.claude-plugin/plugin.json plugin manifest
.claude-plugin/marketplace.json one-plugin marketplace (this repo)
agents/ 5 read-only role agents (Read/Glob/Grep only)
skills/fusion-plan, fusion-review entry points (call the workflows by path)
workflows/*.js the orchestration (bundled; called via ${CLAUDE_PLUGIN_ROOT})
EVAL.md, eval/ validation methodology + telemetry scoreboard scripts
```
Workflows aren't an auto-loaded plugin component, so the skills invoke them by
`scriptPath` under `${CLAUDE_PLUGIN_ROOT}` — they ship as bundled data, not as a
registered-by-name workflow.