Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .claude-plugin/marketplace.json
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@
{
"name": "exodia",
"description": "Multi-agent workflow orchestration (7 commands + 2 skills: eight-gates, hades): fix, tournament, mega-swarm, deep-think, batch-implement, red-blue-review, baryon-mode. Hades, eight-gates, and red-blue-review use Teams API for reactive collaboration.",
"version": "3.0.0",
"version": "3.0.1",
"source": "./plugins/exodia"
},
{
Expand Down
2 changes: 1 addition & 1 deletion docs/ARCHITECTURE.md
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ ancplua-claude-plugins/
│ ├── cc-plugin-eval/ # Claude-Code-native plugin/skill evaluator (token budget, scoring, validators)
│ ├── council/ # Five-agent council via Teams API: Opus captain, researcher, clarity, synth, janitor
│ ├── elegance-pipeline/ # Multi-agent code-elegance workflow: scouts → judges → planner → verifier → implementer
│ ├── exodia/ # Multi-agent orchestration (9 commands + 2 skills: eight-gates, hades)
│ ├── exodia/ # Multi-agent orchestration (7 commands + 2 skills: eight-gates, hades)
│ ├── feature-dev/ # Guided feature development with explorer/architect/reviewer agents
│ ├── html-effectiveness/ # Produce self-contained .html artifacts (dashboards, reports, diagrams) over markdown
│ ├── metacognitive-guard/ # Cognitive amplification + epistemic hooks + competitive review
Expand Down
2 changes: 1 addition & 1 deletion plugins/exodia/.claude-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "exodia",
"version": "3.0.0",
"version": "3.0.1",
"description": "Multi-agent workflow orchestration: 7 commands (fix, tournament, mega-swarm, red-blue-review, baryon-mode...) plus eight-gates and hades skills using the Teams API for reactive work.",
Comment on lines 3 to 5
"author": {
"name": "ANcpLua",
Expand Down
4 changes: 2 additions & 2 deletions plugins/exodia/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ Multi-agent workflow orchestration. 7 commands + 2 skills (eight-gates, hades).

| Command | Agents | Pattern | Best For |
|---------|--------|---------|----------|
| `/exodia:fix` | 8-14 | Gated pipeline (`severity` P0-P3, `parallelism` standard\|maximum) | Any bug — ad-hoc, P0 (add `maximum`), or audit findings (auto-inherited) |
| `/exodia:fix` | 6-12 | Gated pipeline (`severity` P0-P3, `parallelism` standard\|maximum) | Any bug — ad-hoc, P0 (`P0 maximum`), or audit findings (auto-inherited) |
| `/exodia:tournament` | N+2 | Competition | Quality optimization |
| `/exodia:mega-swarm` | 6-12 | All parallel | Codebase audit |
| `/exodia:deep-think` | 5 | Multi-perspective | Analysis before action |
Expand All @@ -27,7 +27,7 @@ Multi-agent workflow orchestration. 7 commands + 2 skills (eight-gates, hades).
1. Go all-in on objective → /exodia:eight-gates "ship v2.0" . 8
2. Audit the codebase → /exodia:mega-swarm mode=quick
3. Exterminate warnings → /exodia:baryon-mode path/to/Solution.sln
4. Fix any issue → /exodia:fix "issue" (add `maximum` for P0; auto-inherits audit findings)
4. Fix any issue → /exodia:fix "issue" (use `/exodia:fix "issue" P0 maximum` for P0; auto-inherits audit findings)
5. Security review → /exodia:red-blue-review scope=security
6. Architectural decisions → /exodia:deep-think mode=architecture
7. Batch implement features → /exodia:batch-implement type=endpoints
Expand Down
2 changes: 1 addition & 1 deletion plugins/exodia/commands/fix.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
description: "IF a bug needs fixing THEN use this — the one exodia fix command. 4 gated phases (analyze → design → implement → verify). Args: severity P0|P1|P2|P3 and parallelism standard|maximum (use maximum for P0 emergencies). Auto-inherits audit findings.json from a prior mega-swarm / eight-gates run when present."
description: "IF a bug needs fixing THEN use this — the one exodia fix command. 4 gated phases (analyze → design → implement → verify). Args: severity P0|P1|P2|P3 and parallelism standard|maximum (for a P0 emergency pass `P0 maximum`). Auto-inherits audit findings.json from a prior mega-swarm run when present."
allowed-tools: Task, Bash, TodoWrite
effort: high
---
Expand Down
3 changes: 2 additions & 1 deletion plugins/exodia/commands/mega-swarm.md
Original file line number Diff line number Diff line change
Expand Up @@ -187,4 +187,5 @@ AUDIT GATE:
| # | Category | Issue | Location |
|---|----------|-------|----------|

**Next:** `/exodia:fix "[P0 issue]"` — it auto-inherits these findings from `findings.json`.
**Next:** `/exodia:fix "<finding-id>" P0` — fix's STEP -1 filters `findings.json` by `finding.id`

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Expose finding IDs before asking users to pass them

The new handoff requires /exodia:fix "<finding-id>" P0, but the final P0 report template immediately above still only prints #, category, issue, and location, so a user following the generated mega-swarm report has no visible finding.id to copy. Since fix filters by an exact finding.id match, this makes the documented auto-inherit path fail unless the user manually opens .eight-gates/artifacts/findings.json; add an ID column or otherwise print the persisted IDs in the report before using them as the next command argument.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Request maximum parallelism for P0 handoffs

This P0 follow-up command omits the third maximum argument, so it runs /exodia:fix with severity P0 but default standard parallelism. The same commit updates the fix docs to say a P0 emergency should pass P0 maximum, and this section is specifically the “P0 Issues (Fix Immediately)” handoff from mega-swarm, so users following it do not get the intended maximum P0 pass; make the example /exodia:fix "<finding-id>" P0 maximum.

Useful? React with 👍 / 👎.

matching `$0`, so pass the finding id (not prose) and `P0` severity to auto-inherit that finding.
Comment on lines +190 to +191
Loading