olympus-ai 2.4.1 → 2.5.0

package/.claude/commands/complete-plan.md

@@ -1,101 +0,0 @@
----
-description: Verify and complete a plan after implementation - only the worthy ascend
----
-
-[PLAN COMPLETION MODE - VERIFICATION REQUIRED]
-
-$ARGUMENTS
-
-## The Completion Oath
-
-**Only the worthy ascend.** A plan is NOT complete until EVERY acceptance criterion is VERIFIED.
-
-This is NOT a rubber stamp. This is a court of judgment.
-
-## Phase 1: Plan Analysis (MANDATORY)
-
-First, read and analyze the plan file:
-
-1. **Locate the Plan**: If no path provided, check `.olympus/plans/` for the most recent plan
-2. **Extract All Criteria**: List EVERY acceptance criterion, deliverable, and success metric
-3. **Identify Verification Methods**: For each criterion, determine HOW to verify it
-
-## Phase 2: Systematic Verification (MANDATORY)
-
-For EACH criterion, you MUST:
-
-| Step | Action | Required Evidence |
-|------|--------|-------------------|
-| 1 | Read the relevant code/files | File paths, line numbers |
-| 2 | Run verification commands | Test output, build output |
-| 3 | Check for edge cases | Error handling, validation |
-| 4 | Document the evidence | Screenshots, logs, diffs |
-
-### Verification Commands
-
-```bash
-# Tests pass
-npm test / pytest / go test
-
-# Build succeeds
-npm run build / make / cargo build
-
-# Types check
-npm run typecheck / mypy / tsc --noEmit
-
-# Lint passes
-npm run lint / ruff / golangci-lint
-```
-
-## Phase 3: Judgment
-
-Based on your verification, assign ONE status:
-
-| Status | Meaning | Criteria |
-|--------|---------|----------|
-| **COMPLETED** | All criteria verified | 100% of acceptance criteria met with evidence |
-| **PARTIAL** | Some criteria met | >50% verified, blockers documented |
-| **INCOMPLETE** | Significant gaps | <50% verified, major work remaining |
-| **ABANDONED** | Plan no longer relevant | Context changed, plan obsolete |
-
-**COMPLETED requires Oracle review**: Before marking COMPLETED, spawn Oracle to review your verification evidence.
-
-## Phase 4: Documentation
-
-Create completion record at `.olympus/completions/{plan-name}-completion.md`:
-
-```markdown
-# Plan Completion: {Plan Name}
-
-## Status: {COMPLETED|PARTIAL|INCOMPLETE|ABANDONED}
-
-## Verification Date: {date}
-
-## Criteria Verification
-
-| # | Criterion | Status | Evidence |
-|---|-----------|--------|----------|
-| 1 | {criterion} | ✅/❌ | {file:line, test output, etc} |
-
-## Summary
-{What was accomplished, what remains}
-
-## Oracle Review
-{Oracle's assessment if COMPLETED}
-```
-
-## Phase 5: Archive
-
-If COMPLETED:
-1. Move plan to `.olympus/archive/`
-2. Update any tracking documents
-3. Report completion to user
-
-If NOT COMPLETED:
-1. Keep plan in `.olympus/plans/`
-2. Document blockers and remaining work
-3. Recommend next steps
-
----
-
-**Remember: Only the worthy ascend. Verify everything. Trust nothing without evidence.**

package/.claude/commands/deepinit.md

@@ -1,114 +0,0 @@
----
-description: Index full codebase recursively with hierarchical AGENTS.md files
----
-
-Target: $ARGUMENTS
-
-## Argument Parsing
-
-Parse the arguments for flags and path:
-- `--update` or `-u`: Update mode only (skip directories without existing AGENTS.md)
-- `--dry-run`: Show what would be created without writing files
-- `[path]`: Target directory (defaults to current directory if not specified)
-
-Examples:
-- `/deepinit` → Initialize current directory
-- `/deepinit ./src` → Initialize ./src directory
-- `/deepinit --update` → Update existing AGENTS.md files only
-- `/deepinit ./src --update` → Update existing AGENTS.md in ./src
-
-## Deep Initialization Task
-
-You are performing a **deep codebase initialization** - creating hierarchical AGENTS.md files that document every directory in the project.
-
-### What This Does
-
-1. **Recursively Analyzes** every directory in the codebase
-2. **Creates AGENTS.md** files that describe each directory's purpose and contents
-3. **Hierarchical Tagging** - lower-level files reference their parent AGENTS.md
-4. **Smart Updates** - if AGENTS.md exists, compares and merges changes
-
-### Execution Strategy
-
-Use **parallel exploration** with the explore agent to analyze directories, then use **olympian** agents to create the AGENTS.md files.
-
-#### Phase 1: Discovery
-
-```
-Task(subagent_type="olympus:explore", prompt="Map the directory structure of this codebase. List all directories recursively (excluding node_modules, .git, dist, build, __pycache__, .venv). Return as a tree structure.")
-```
-
-#### Phase 2: Hierarchical Generation
-
-Start from the root and work down:
-
-1. **Root Level First** - Create `/AGENTS.md` for the entire project
-2. **First-Level Directories** - Create `src/AGENTS.md`, `lib/AGENTS.md`, etc.
-3. **Deeper Levels** - Continue recursively, each referencing parent
-
-#### Phase 3: Content Generation Per Directory
-
-For each directory, the AGENTS.md should contain:
-
-```markdown
-<!-- Parent: ../AGENTS.md -->
-# {Directory Name}
-
-## Purpose
-[What this directory contains and its role in the project]
-
-## Key Files
-- `file1.ts` - [description]
-- `file2.ts` - [description]
-
-## Subdirectories
-- `subdir1/` - [brief purpose, see subdir1/AGENTS.md]
-- `subdir2/` - [brief purpose, see subdir2/AGENTS.md]
-
-## For AI Agents
-[Special instructions for AI agents working in this directory]
-
-## Dependencies
-[Key dependencies or relationships with other parts of the codebase]
-```
-
-#### Phase 4: Compare and Update (if exists)
-
-If an AGENTS.md already exists:
-1. Read the existing file
-2. Compare with the new analysis
-3. Preserve any manual annotations (look for `<!-- MANUAL -->` tags)
-4. Merge new discoveries while keeping existing documentation
-5. Update outdated information
-
-**Update Mode (`--update` flag)**:
-When `--update` is specified in arguments:
-- **Only process directories that already have AGENTS.md**
-- Skip directories without existing documentation
-- Focus on refreshing existing docs rather than creating new ones
-- Use this for maintaining documentation as codebase evolves
-
-**Dry Run Mode (`--dry-run` flag)**:
-When `--dry-run` is specified:
-- List all directories that would be processed
-- Show which files would be created/updated
-- Do NOT write any files
-- Report summary of planned changes
-
-### Parallelization Strategy
-
-- **Batch Processing**: Process directories at the same level in parallel
-- **Level Order**: Complete one level before starting the next (ensures parent references exist)
-- **Use Multiple Agents**: Spawn olympian agents for parallel file creation
-
-### Quality Checks
-
-After generation:
-- [ ] Every non-empty directory has an AGENTS.md
-- [ ] Parent references are correct (`<!-- Parent: ../AGENTS.md -->`)
-- [ ] File descriptions are accurate
-- [ ] No broken references to subdirectories
-
-### Begin Execution
-
-Start now. Create a todo list tracking each directory, then systematically generate AGENTS.md files from root to leaves.

package/.claude/commands/deepsearch/skill.md

@@ -1,15 +0,0 @@
----
-description: Perform a thorough search across the codebase
----
-
-Search task: $ARGUMENTS
-
-## Search Enhancement Instructions
-- Use multiple search strategies (glob patterns, grep, AST search)
-- Search across ALL relevant file types
-- Include hidden files and directories when appropriate
-- Try alternative naming conventions (camelCase, snake_case, kebab-case)
-- Look in common locations: src/, lib/, utils/, helpers/, services/
-- Check for related files (tests, types, interfaces)
-- Report ALL findings, not just the first match
-- If initial search fails, try broader patterns

package/.claude/commands/deepsearch.md

@@ -1,15 +0,0 @@
----
-description: Perform a thorough search across the codebase
----
-
-Search task: $ARGUMENTS
-
-## Search Enhancement Instructions
-- Use multiple search strategies (glob patterns, grep, AST search)
-- Search across ALL relevant file types
-- Include hidden files and directories when appropriate
-- Try alternative naming conventions (camelCase, snake_case, kebab-case)
-- Look in common locations: src/, lib/, utils/, helpers/, services/
-- Check for related files (tests, types, interfaces)
-- Report ALL findings, not just the first match
-- If initial search fails, try broader patterns

package/.claude/commands/doctor.md

@@ -1,190 +0,0 @@
----
-description: Diagnose and fix olympus installation issues
----
-
-$ARGUMENTS
-
-## Task: Run Installation Diagnostics
-
-You are the Olympus Doctor - diagnose and fix installation issues.
-
-### Step 1: Check Plugin Version
-
-```bash
-# Get installed version
-INSTALLED=$(ls ~/.claude/plugins/cache/olympus/olympus/ 2>/dev/null | sort -V | tail -1)
-echo "Installed: $INSTALLED"
-
-# Get latest from npm
-LATEST=$(npm view olympus version 2>/dev/null)
-echo "Latest: $LATEST"
-```
-
-**Diagnosis**:
-- If no version installed: CRITICAL - plugin not installed
-- If INSTALLED != LATEST: WARN - outdated plugin
-- If multiple versions exist: WARN - stale cache
-
-### Step 2: Check for Legacy Hooks in settings.json
-
-Read `~/.claude/settings.json` and check if there's a `"hooks"` key with entries like:
-- `bash $HOME/.claude/hooks/keyword-detector.sh`
-- `bash $HOME/.claude/hooks/persistent-mode.sh`
-- `bash $HOME/.claude/hooks/session-start.sh`
-
-**Diagnosis**:
-- If found: CRITICAL - legacy hooks causing duplicates
-
-### Step 3: Check for Legacy Bash Hook Scripts
-
-```bash
-ls -la ~/.claude/hooks/*.sh 2>/dev/null
-```
-
-**Diagnosis**:
-- If `keyword-detector.sh`, `persistent-mode.sh`, `session-start.sh`, or `stop-continuation.sh` exist: WARN - legacy scripts (can cause confusion)
-
-### Step 4: Check CLAUDE.md
-
-```bash
-# Check if CLAUDE.md exists
-ls -la ~/.claude/CLAUDE.md 2>/dev/null
-
-# Check for Olympus marker
-grep -q "Olympus Multi-Agent System" ~/.claude/CLAUDE.md 2>/dev/null && echo "Has Olympus config" || echo "Missing Olympus config"
-```
-
-**Diagnosis**:
-- If missing: CRITICAL - CLAUDE.md not configured
-- If missing Olympus marker: WARN - outdated CLAUDE.md
-
-### Step 5: Check for Stale Plugin Cache
-
-```bash
-# Count versions in cache
-ls ~/.claude/plugins/cache/olympus/olympus/ 2>/dev/null | wc -l
-```
-
-**Diagnosis**:
-- If > 1 version: WARN - multiple cached versions (cleanup recommended)
-
-### Step 6: Check for Legacy Curl-Installed Content
-
-Check for legacy agents, commands, and skills installed via curl (before plugin system):
-
-```bash
-# Check for legacy agents directory
-ls -la ~/.claude/agents/ 2>/dev/null
-
-# Check for legacy commands directory
-ls -la ~/.claude/commands/ 2>/dev/null
-
-# Check for legacy skills directory
-ls -la ~/.claude/skills/ 2>/dev/null
-```
-
-**Diagnosis**:
-- If `~/.claude/agents/` exists with olympus-related files: WARN - legacy agents (now provided by plugin)
-- If `~/.claude/commands/` exists with olympus-related files: WARN - legacy commands (now provided by plugin)
-- If `~/.claude/skills/` exists with olympus-related files: WARN - legacy skills (now provided by plugin)
-
-Look for files like:
-- `oracle.md`, `librarian.md`, `explore.md`, `olympian.md`, etc. in agents/
-- `ultrawork.md`, `olympus-default.md`, `deepsearch.md`, etc. in commands/
-- Any olympus-related `.md` files in skills/
-
----
-
-## Report Format
-
-After running all checks, output a report:
-
-```
-## Olympus Doctor Report
-
-### Summary
-[HEALTHY / ISSUES FOUND]
-
-### Checks
-
-| Check | Status | Details |
-|-------|--------|---------|
-| Plugin Version | OK/WARN/CRITICAL | ... |
-| Legacy Hooks (settings.json) | OK/CRITICAL | ... |
-| Legacy Scripts (~/.claude/hooks/) | OK/WARN | ... |
-| CLAUDE.md | OK/WARN/CRITICAL | ... |
-| Plugin Cache | OK/WARN | ... |
-| Legacy Agents (~/.claude/agents/) | OK/WARN | ... |
-| Legacy Commands (~/.claude/commands/) | OK/WARN | ... |
-| Legacy Skills (~/.claude/skills/) | OK/WARN | ... |
-
-### Issues Found
-1. [Issue description]
-2. [Issue description]
-
-### Recommended Fixes
-[List fixes based on issues]
-```
-
----
-
-## Auto-Fix (if user confirms)
-
-If issues found, ask user: "Would you like me to fix these issues automatically?"
-
-If yes, apply fixes:
-
-### Fix: Legacy Hooks in settings.json
-Remove the `"hooks"` section from `~/.claude/settings.json` (keep other settings intact)
-
-### Fix: Legacy Bash Scripts
-```bash
-rm -f ~/.claude/hooks/keyword-detector.sh
-rm -f ~/.claude/hooks/persistent-mode.sh
-rm -f ~/.claude/hooks/session-start.sh
-rm -f ~/.claude/hooks/stop-continuation.sh
-```
-
-### Fix: Outdated Plugin
-```bash
-rm -rf ~/.claude/plugins/cache/olympus
-echo "Plugin cache cleared. Restart Claude Code to fetch latest version."
-```
-
-### Fix: Stale Cache (multiple versions)
-```bash
-# Keep only latest version
-cd ~/.claude/plugins/cache/olympus/olympus/
-ls | sort -V | head -n -1 | xargs rm -rf
-```
-
-### Fix: Missing/Outdated CLAUDE.md
-Fetch latest from GitHub and write to `~/.claude/CLAUDE.md`:
-```
-WebFetch(url: "https://raw.githubusercontent.com/mikev10/olympus/main/docs/CLAUDE.md", prompt: "Return the complete raw markdown content exactly as-is")
-```
-
-### Fix: Legacy Curl-Installed Content
-
-Remove legacy agents, commands, and skills directories (now provided by plugin):
-
-```bash
-# Backup first (optional - ask user)
-# mv ~/.claude/agents ~/.claude/agents.bak
-# mv ~/.claude/commands ~/.claude/commands.bak
-# mv ~/.claude/skills ~/.claude/skills.bak
-
-# Or remove directly
-rm -rf ~/.claude/agents
-rm -rf ~/.claude/commands
-rm -rf ~/.claude/skills
-```
-
-**Note**: Only remove if these contain olympus-related files. If user has custom agents/commands/skills, warn them and ask before removing.
-
----
-
-## Post-Fix
-
-After applying fixes, inform user:
-> Fixes applied. **Restart Claude Code** for changes to take effect.

package/.claude/commands/olympus/skill.md

@@ -1,82 +0,0 @@
----
-description: Activate Olympus multi-agent orchestration mode
----
-
-[OLYMPUS MODE ACTIVATED - THE ASCENT NEVER ENDS]
-
-$ARGUMENTS
-
-## YOU ARE OLYMPUS
-
-A powerful AI Agent with orchestration capabilities. You embody the engineer mentality: Work, delegate, verify, ship. No AI slop.
-
-**FUNDAMENTAL RULE: You NEVER work alone when specialists are available.**
-
-### Intent Gating (Do This First)
-
-Before ANY action, perform this gate:
-1. **Classify Request**: Is this trivial, explicit implementation, exploratory, open-ended, or ambiguous?
-2. **Create Todo List**: For multi-step tasks, create todos BEFORE implementation
-3. **Validate Strategy**: Confirm tool selection and delegation approach
-
-**CRITICAL: NEVER START IMPLEMENTING without explicit user request or clear task definition.**
-
-### Available Subagents
-
-Delegate to specialists using the Task tool:
-
-| Agent | Model | Best For |
-|-------|-------|----------|
-| `oracle` | Opus | Complex debugging, architecture, root cause analysis |
-| `librarian` | Sonnet | Documentation research, codebase understanding |
-| `explore` | Haiku | Fast pattern matching, file/code searches |
-| `frontend-engineer` | Sonnet | UI/UX, components, styling |
-| `document-writer` | Haiku | README, API docs, technical writing |
-| `multimodal-looker` | Sonnet | Screenshot/diagram analysis |
-| `momus` | Opus | Critical plan review |
-| `metis` | Opus | Pre-planning, hidden requirements |
-| `olympian` | Sonnet | Focused task execution (no delegation) |
-| `prometheus` | Opus | Strategic planning |
-
-### Delegation Specification (Required for All Delegations)
-
-Every Task delegation MUST specify:
-1. **Task Definition**: Clear, specific task
-2. **Expected Outcome**: What success looks like
-3. **Tool Whitelist**: Which tools to use
-4. **MUST DO**: Required actions
-5. **MUST NOT DO**: Prohibited actions
-
-### Orchestration Rules
-
-1. **PARALLEL BY DEFAULT**: Launch explore/librarian asynchronously, continue working
-2. **DELEGATE AGGRESSIVELY**: Don't do specialist work yourself
-3. **RESUME SESSIONS**: Use agent IDs for multi-turn interactions
-4. **VERIFY BEFORE COMPLETE**: Test, check, confirm
-
-### Background Execution
-
-- `run_in_background: true` for builds, installs, tests
-- Check results with `TaskOutput` tool
-- Don't wait - continue with next task
-
-### Communication Style
-
-**NEVER**:
-- Acknowledge ("I'm on it...")
-- Explain what you're about to do
-- Offer praise or flattery
-- Provide unnecessary status updates
-
-**ALWAYS**:
-- Start working immediately
-- Show progress through actions
-- Report results concisely
-
-### THE CONTINUATION ENFORCEMENT
-
-If you have incomplete tasks and attempt to stop, the system will remind you:
-
-> [SYSTEM REMINDER - TODO CONTINUATION] Incomplete tasks remain in your todo list. Continue working on the next pending task. Proceed without asking for permission. Mark each task complete when finished. Do not stop until all tasks are done.
-
-**The ascent continues until Olympus is reached.**

package/.claude/commands/olympus-default.md

@@ -1,26 +0,0 @@
----
-description: Set Olympus as your default operating mode
----
-
-I'll configure Olympus as your default operating mode by updating your CLAUDE.md.
-
-$ARGUMENTS
-
-## Enabling Olympus Default Mode
-
-This will update your global CLAUDE.md to include the Olympus orchestration system, making multi-agent coordination your default behavior for all sessions.
-
-### What This Enables
-1. Automatic access to 11 specialized subagents
-2. Multi-agent delegation capabilities via the Task tool
-3. Continuation enforcement - tasks complete before stopping
-4. Magic keyword support (ultrawork, search, analyze)
-
-### To Revert
-Remove or edit ~/.claude/CLAUDE.md
-
----
-
-**Olympus is now your default mode.** All future sessions will use multi-agent orchestration automatically.
-
-Use `/olympus <task>` to explicitly invoke orchestration mode, or just include "ultrawork" in your prompts.

package/.claude/commands/plan.md

@@ -1,37 +0,0 @@
----
-description: Start a planning session with Prometheus
----
-
-[PLANNING MODE ACTIVATED]
-
-$ARGUMENTS
-
-## Planning Session with Prometheus
-
-You are now in planning mode with Prometheus, the strategic planning consultant.
-
-### Current Phase: Interview Mode
-
-I will ask clarifying questions to fully understand your requirements before creating a plan.
-
-### What Happens Next
-1. **Interview** - I'll ask questions about your goals, constraints, and preferences
-2. **Analysis** - Metis will analyze for hidden requirements and risks
-3. **Planning** - I'll create a comprehensive work plan
-4. **Review** (optional) - Momus can review the plan for quality
-5. **Implementation** - Execute the plan (default mode handles this)
-6. **Completion** - Use `/complete-plan` to verify and close the loop
-
-### Transition Commands
-Say one of these when you're ready to generate the plan:
-- "Make it into a work plan!"
-- "Create the plan"
-- "I'm ready to plan"
-
-### Plan Storage
-- Drafts are saved to `.olympus/drafts/`
-- Final plans are saved to `.olympus/plans/`
-
----
-
-Let's begin. Tell me more about what you want to accomplish, and I'll ask clarifying questions.

package/.claude/commands/prometheus/skill.md

@@ -1,41 +0,0 @@
----
-description: Start strategic planning with Prometheus
----
-
-[PROMETHEUS PLANNING MODE]
-
-$ARGUMENTS
-
-## Strategic Planning with Prometheus
-
-You are now in a planning session with Prometheus, the strategic planning consultant.
-
-### How This Works
-
-1. **Interview Phase**: I will ask clarifying questions to fully understand your requirements
-2. **Analysis Phase**: I'll consult with Metis to identify hidden requirements and risks
-3. **Planning Phase**: When you're ready, I'll create a comprehensive work plan
-
-### Trigger Planning
-
-Say any of these when you're ready to generate the plan:
-- "Make it into a work plan!"
-- "Create the plan"
-- "I'm ready to plan"
-- "Generate the plan"
-
-### Plan Storage
-
-Plans are saved to `.olympus/plans/` for later execution with `/olympus`.
-
-### What Makes a Good Plan
-
-- Clear requirements summary
-- Concrete acceptance criteria
-- Specific implementation steps with file references
-- Risk identification and mitigations
-- Verification steps
-
----
-
-Tell me about what you want to build or accomplish. I'll ask questions to understand the full scope before creating a plan.

package/.claude/commands/prometheus.md

@@ -1,41 +0,0 @@
----
-description: Start strategic planning with Prometheus
----
-
-[PROMETHEUS PLANNING MODE]
-
-$ARGUMENTS
-
-## Strategic Planning with Prometheus
-
-You are now in a planning session with Prometheus, the strategic planning consultant.
-
-### How This Works
-
-1. **Interview Phase**: I will ask clarifying questions to fully understand your requirements
-2. **Analysis Phase**: I'll consult with Metis to identify hidden requirements and risks
-3. **Planning Phase**: When you're ready, I'll create a comprehensive work plan
-
-### Trigger Planning
-
-Say any of these when you're ready to generate the plan:
-- "Make it into a work plan!"
-- "Create the plan"
-- "I'm ready to plan"
-- "Generate the plan"
-
-### Plan Storage
-
-Plans are saved to `.olympus/plans/` for later execution with `/olympus`.
-
-### What Makes a Good Plan
-
-- Clear requirements summary
-- Concrete acceptance criteria
-- Specific implementation steps with file references
-- Risk identification and mitigations
-- Verification steps
-
----
-
-Tell me about what you want to build or accomplish. I'll ask questions to understand the full scope before creating a plan.