Help us improve
Share bugs, ideas, or general feedback.
npx claudepluginhub devy1540/olympus --plugin olympusHow this skill is triggered — by the user, by Claude, or both
Slash command
/olympus:hestiaThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<Purpose>
Scans codebase to auto-generate CLAUDE.md project config and .rune/ state files for full context in AI coding sessions. Use on new repos or missing/stale context.
Scans codebase, builds confidence per data point, only asks what it can't figure out, generates SDLC files. Use for first-time setup or re-running setup.
Initializes Quaestor in projects with auto-framework detection, parallel architecture/security analysis, customized doc generation, user validation, and setup completion.
Share bugs, ideas, or general feedback.
<Execution_Policy>
Quick codebase reconnaissance (orchestrator does this directly — no agent needed):
1. Project detection:
- package.json → Node.js/TypeScript
- pom.xml / build.gradle → JVM
- pyproject.toml / requirements.txt → Python
- go.mod → Go
- Cargo.toml → Rust
- None → ask the user
2. Scale assessment:
- Count source files (Glob **/*.{ts,js,py,java,kt,go,rs})
- Count test files (Glob **/*.{test,spec}.* or **/test_*)
- Check for CI config (.github/workflows/, Jenkinsfile, etc.)
3. Existing Olympus state:
- Check .olympus/ directory exists
- If exists: list prior runs (oracle-*, pantheon-*, odyssey-*)
- If exists: check for latest spec.md
4. Build system:
- Detect build command (npm run build, ./gradlew build, make, etc.)
- Detect test command (npm test, pytest, ./gradlew test, etc.)
- Detect lint command (eslint, prettier, ruff, etc.)
Determine project readiness:
1. Specification Readiness:
- Does a spec or PRD exist? Score: HIGH / MEDIUM / LOW
2. Codebase Readiness:
- Working build? Tests? Structured directories? Score: HIGH / MEDIUM / LOW
3. Complexity Assessment:
- Simple: < 50 files | Medium: 50-500 | Complex: 500+
Decision tree:
IF vague requirements: → /olympus:oracle
ELIF clear reqs, need analysis: → /olympus:pantheon
ELIF technical decision: → /olympus:agora
ELIF evaluate implementation: → /olympus:tribunal
ELIF full pipeline: → /olympus:odyssey
ELSE: → AskUserQuestion with all options
AskUserQuestion:
"Based on your project, I recommend {skill}. What would you like to do?"
["{recommended}", "Show all skills", "I have a specific task"]
Display project profile:
## Project Profile
| Attribute | Value |
|-----------|-------|
| Language | {detected} |
| Framework | {detected} |
| Build | `{command}` |
| Test | `{command}` |
| Scale | {level} ({count} files) |
| Prior Olympus runs | {count or "none"} |
## Recommended Path
**{skill name}** — {reason}
Display: "Run `{recommended skill}` to begin."
Do NOT auto-execute the skill.