Help us improve
Share bugs, ideas, or general feedback.
Olympus — Harness engineering plugin marketplace
npx claudepluginhub devy1540/olympusOlympus — Harness engineering plugin. 15 agents perform requirement refinement, multi-perspective analysis, evolution loops, and evaluation.
Share bugs, ideas, or general feedback.
English | 한국어
𝛀 ─────────── 𝛀
O L Y M P U S
올 림 푸 스
𝛀 ─────────── 𝛀
"The gods merely pose questions. Fate lies in what I ask — the answers are yours to find."
15 gods argue, challenge, and verify — so your software doesn't ship on assumptions.
Quick Start · Philosophy · Pipeline · Skills · Agents · Examples
The gods don't agree. That's the point.
Olympus is a harness engineering plugin for Claude Code. 15 agents — each a Greek deity with a distinct role and strict permissions — refine requirements, analyze from multiple perspectives, implement, and evaluate your software through structured adversarial collaboration.
Most AI coding fails because nobody questioned the requirements. Olympus forces the question before allowing the answer.
"Know thyself" — Inscription at the Temple of Apollo at Delphi
Software fails at three points: unclear requirements, unchallenged assumptions, and unverified outcomes. Olympus addresses all three through separation of concerns at the agent level:
The one who plans (Zeus) cannot review their own plan (Themis does).
The one who builds (Prometheus) cannot evaluate their own work (Athena does).
The one who analyzes (Ares) must survive the devil's advocate (Eris does).
This is not bureaucracy — it's structural honesty. Every claim requires file:line evidence. Every analysis survives adversarial challenge. Every gate has a mathematical threshold, not a vibes check.
Ambiguity Gate ≤ 0.2 "Are we clear enough to build?"
Convergence Gate ≥ 0.95 "Has the spec stabilized?"
Consensus Gate ≥ 66% "Do the reviewers agree?"
Quality Gate ≥ 0.8 "Is the output good enough?"
Four numbers. Four moments where the system refuses to proceed until the math says yes.
# In your terminal
claude plugin marketplace add devy1540/olympus
claude plugin install olympus@olympus-marketplace
# Inside Claude Code
/plugin marketplace add devy1540/olympus
/plugin install olympus@olympus-marketplace
# Verify installation
/olympus:setup
# Project onboarding — scan your project and get a recommendation
/olympus:hestia
# Refine your requirements
/olympus:oracle
# Full pipeline: requirements → analysis → implementation → evaluation
/olympus:odyssey
/olympus:oracle → Socratic interview exposed hidden assumptions
Ambiguity scored and gated (≤ 0.2)
Gap analysis against your codebase
→ spec.md
/olympus:odyssey → Oracle (refine) → Genesis (evolve) → Pantheon (analyze)
→ Plan + Implement → Tribunal (evaluate)
→ verdict.md
The gods deliberated. Your spec survived the gauntlet.
Olympus operates as a pipeline of specialized skills, each orchestrating multiple agents:
Oracle → Genesis → Pantheon → Plan → Execute → Tribunal
(ask) (evolve) (analyze) (design) (build) (judge)
↑ ↓
└──────────── Rejected? Retry or rewind ─────────┘
Each stage has a gate. No stage proceeds without passing.
| Stage | Gate | Threshold | What Happens |
|---|---|---|---|
| Oracle | Ambiguity Score | ≤ 0.2 | Socratic interview until requirements are 80%+ clear |
| Genesis | Ontology Convergence | ≥ 0.95 | Spec evolves generation by generation until stable |
| Pantheon | Consensus | ≥ 66% | Multi-perspective analysis survives devil's advocate |
| Tribunal | Mechanical + Semantic | Pass all | Build, test, type-check, then AC verification |
/olympus:oracle — The Oracle of DelphiTurn vague ideas into validated specifications.
Hermes (explore) → Apollo (interview) → Ambiguity Gate → Metis (gap analysis) → spec.md
/olympus:genesis — CreationEvolve specifications through generational iteration.
Seed → Metis (wonder) → Eris (reflect) → Next Seed → Convergence? (≥ 0.95)
↑ ↓ NO
└────────────────────────────────────────────────────────┘
/olympus:pantheon — Council of the GodsAnalyze problems from multiple orthogonal perspectives.