oh-my-claude-sisyphus 3.5.3 → 3.5.6

package/scripts/uninstall.sh

@@ -63,8 +63,6 @@ rm -f "$CLAUDE_CONFIG_DIR/agents/prometheus.md"
 # Remove commands
 echo -e "${BLUE}Removing commands...${NC}"
 rm -f "$CLAUDE_CONFIG_DIR/commands/sisyphus.md"
-rm -f "$CLAUDE_CONFIG_DIR/commands/sisyphus-default.md"
-rm -f "$CLAUDE_CONFIG_DIR/commands/sisyphus-default-global.md"
 rm -f "$CLAUDE_CONFIG_DIR/commands/ultrawork.md"
 rm -f "$CLAUDE_CONFIG_DIR/commands/deepsearch.md"
 rm -f "$CLAUDE_CONFIG_DIR/commands/analyze.md"
@@ -72,8 +70,6 @@ rm -f "$CLAUDE_CONFIG_DIR/commands/plan.md"
 rm -f "$CLAUDE_CONFIG_DIR/commands/review.md"
 rm -f "$CLAUDE_CONFIG_DIR/commands/prometheus.md"
 rm -f "$CLAUDE_CONFIG_DIR/commands/orchestrator.md"
-rm -f "$CLAUDE_CONFIG_DIR/commands/ralph-loop.md"
-rm -f "$CLAUDE_CONFIG_DIR/commands/cancel-ralph.md"
 rm -f "$CLAUDE_CONFIG_DIR/commands/update.md"
 
 # Remove skills

package/skills/autopilot/SKILL.md

@@ -114,7 +114,7 @@ Optional settings in `.claude/settings.json`:
 ## Cancellation
 
 ```
-/oh-my-claudecode:cancel-autopilot
+/oh-my-claudecode:cancel
 ```
 
 Or say: "stop", "cancel", "abort"

package/skills/cancel/SKILL.md

@@ -38,6 +38,8 @@ The skill checks state files to determine what's active:
 - `.omc/swarm-state.json` → Swarm detected
 - `.omc/ultrapilot-state.json` → Ultrapilot detected
 - `.omc/pipeline-state.json` → Pipeline detected
+- `.omc/state/plan-consensus.json` → Plan Consensus detected
+- `.omc/ralplan-state.json` → Plan Consensus detected (legacy)
 
 If multiple modes are active, they're cancelled in order of dependency:
 1. Autopilot (includes ralph/ultraqa/ecomode cleanup)
@@ -48,6 +50,7 @@ If multiple modes are active, they're cancelled in order of dependency:
 6. Swarm (standalone)
 7. Ultrapilot (standalone)
 8. Pipeline (standalone)
+9. Plan Consensus (standalone)
 
 ## Force Clear All
 
@@ -73,6 +76,8 @@ This removes all state files:
 - `.omc/state/swarm-tasks.json`
 - `.omc/ultrapilot-state.json`
 - `.omc/pipeline-state.json`
+- `.omc/state/plan-consensus.json`
+- `.omc/ralplan-state.json`
 - `~/.claude/ralph-state.json`
 - `~/.claude/ultrawork-state.json`
 - `~/.claude/ecomode-state.json`
@@ -120,6 +125,15 @@ fi
 if [[ -f .omc/ultraqa-state.json ]]; then
   ULTRAQA_ACTIVE=$(cat .omc/ultraqa-state.json | jq -r '.active // false')
 fi
+
+PLAN_CONSENSUS_ACTIVE=false
+
+# Check both new and legacy locations
+if [[ -f .omc/state/plan-consensus.json ]]; then
+  PLAN_CONSENSUS_ACTIVE=$(cat .omc/state/plan-consensus.json | jq -r '.active // false')
+elif [[ -f .omc/ralplan-state.json ]]; then
+  PLAN_CONSENSUS_ACTIVE=$(cat .omc/ralplan-state.json | jq -r '.active // false')
+fi
 ```
 
 ### 3A. Force Mode (if --force or --all)
@@ -140,6 +154,8 @@ if [[ "$FORCE_MODE" == "true" ]]; then
   rm -f .omc/state/swarm-tasks.json
   rm -f .omc/ultrapilot-state.json
   rm -f .omc/pipeline-state.json
+  rm -f .omc/state/plan-consensus.json
+  rm -f .omc/ralplan-state.json
 
   # Remove global state files
   rm -f ~/.claude/ralph-state.json
@@ -308,6 +324,8 @@ if [[ "$FORCE_MODE" == "true" ]]; then
   rm -f .omc/state/swarm-tasks.json
   rm -f .omc/ultrapilot-state.json
   rm -f .omc/pipeline-state.json
+  rm -f .omc/state/plan-consensus.json
+  rm -f .omc/ralplan-state.json
 
   # Remove global state files
   rm -f ~/.claude/ralph-state.json
@@ -526,6 +544,20 @@ if [[ -f .omc/pipeline-state.json ]]; then
   fi
 fi
 
+# 9. Check Plan Consensus (standalone)
+if [[ "$PLAN_CONSENSUS_ACTIVE" == "true" ]]; then
+  echo "Cancelling Plan Consensus mode..."
+
+  # Clear state files
+  rm -f .omc/state/plan-consensus.json
+  rm -f .omc/ralplan-state.json
+
+  echo "Plan Consensus cancelled. Planning session ended."
+  echo "Note: Plan file preserved at path specified in state."
+  CANCELLED_ANYTHING=true
+  exit 0
+fi
+
 # No active modes found
 if [[ "$CANCELLED_ANYTHING" == "false" ]]; then
   echo "No active OMC modes detected."
@@ -539,6 +571,7 @@ if [[ "$CANCELLED_ANYTHING" == "false" ]]; then
   echo "  - Swarm (.omc/swarm-state.json)"
   echo "  - Ultrapilot (.omc/ultrapilot-state.json)"
   echo "  - Pipeline (.omc/pipeline-state.json)"
+  echo "  - Plan Consensus (.omc/state/plan-consensus.json)"
   echo ""
   echo "Use --force to clear all state files anyway."
 fi
@@ -556,6 +589,7 @@ fi
 | Swarm | "Swarm cancelled. Coordinated agents stopped." |
 | Ultrapilot | "Ultrapilot cancelled. Parallel autopilot workers stopped." |
 | Pipeline | "Pipeline cancelled. Sequential agent chain stopped." |
+| Plan Consensus | "Plan Consensus cancelled. Planning session ended." |
 | Force | "All OMC modes cleared. You are free to start fresh." |
 | None | "No active OMC modes detected." |
 
@@ -570,6 +604,7 @@ fi
 | Swarm | No | N/A |
 | Ultrapilot | No | N/A |
 | Pipeline | No | N/A |
+| Plan Consensus | Yes (plan file path preserved) | N/A |
 
 ## Notes
 

package/skills/doctor/SKILL.md

@@ -91,7 +91,7 @@ ls -la ~/.claude/skills/ 2>/dev/null
 
 Look for files like:
 - `architect.md`, `researcher.md`, `explore.md`, `executor.md`, etc. in agents/
-- `ultrawork.md`, `omc-default.md`, `omc-default-global.md`, `deepsearch.md`, etc. in commands/
+- `ultrawork.md`, `deepsearch.md`, etc. in commands/
 - Any oh-my-claudecode-related `.md` files in skills/
 
 ---

package/skills/help/SKILL.md

@@ -51,7 +51,7 @@ This is the **only command** you need to know. It downloads the configuration an
 
 ## For 2.x Users
 
-Your old commands still work! `/ralph`, `/ultrawork`, `/planner`, etc. all function exactly as before.
+Your old commands still work! `/ralph`, `/ultrawork`, `/plan`, etc. all function exactly as before.
 
 But now you don't NEED them - everything is automatic.
 
@@ -62,4 +62,4 @@ But now you don't NEED them - everything is automatic.
 
 ---
 
-*Version: 3.4.0*
+*Version: 3.5.5*

package/skills/learn-about-omc/SKILL.md

@@ -0,0 +1,128 @@
+---
+name: learn-about-omc
+description: Analyze your OMC usage patterns and get personalized recommendations
+---
+
+# Learn About OMC
+
+Analyzes your oh-my-claudecode usage and provides tailored recommendations to improve your workflow.
+
+## What It Does
+
+1. Reads token tracking from `~/.omc/state/token-tracking.jsonl`
+2. Reads session history from `.omc/state/session-history.json`
+3. Analyzes agent usage patterns
+4. Identifies underutilized features
+5. Recommends configuration changes
+
+## Implementation
+
+### Step 1: Gather Data
+
+```bash
+# Check for token tracking data
+TOKEN_FILE="$HOME/.omc/state/token-tracking.jsonl"
+SESSION_FILE=".omc/state/session-history.json"
+CONFIG_FILE="$HOME/.claude/.omc-config.json"
+
+echo "📊 Analyzing OMC Usage..."
+echo ""
+
+# Check what data is available
+HAS_TOKENS=false
+HAS_SESSIONS=false
+HAS_CONFIG=false
+
+if [[ -f "$TOKEN_FILE" ]]; then
+  HAS_TOKENS=true
+  TOKEN_COUNT=$(wc -l < "$TOKEN_FILE")
+  echo "Token records found: $TOKEN_COUNT"
+fi
+
+if [[ -f "$SESSION_FILE" ]]; then
+  HAS_SESSIONS=true
+  SESSION_COUNT=$(cat "$SESSION_FILE" | jq '.sessions | length' 2>/dev/null || echo "0")
+  echo "Sessions found: $SESSION_COUNT"
+fi
+
+if [[ -f "$CONFIG_FILE" ]]; then
+  HAS_CONFIG=true
+  DEFAULT_MODE=$(cat "$CONFIG_FILE" | jq -r '.defaultExecutionMode // "not set"')
+  echo "Default execution mode: $DEFAULT_MODE"
+fi
+```
+
+### Step 2: Analyze Agent Usage (if token data exists)
+
+```bash
+if [[ "$HAS_TOKENS" == "true" ]]; then
+  echo ""
+  echo "TOP AGENTS BY USAGE:"
+  cat "$TOKEN_FILE" | jq -r '.agentName // "main"' | sort | uniq -c | sort -rn | head -10
+
+  echo ""
+  echo "MODEL DISTRIBUTION:"
+  cat "$TOKEN_FILE" | jq -r '.modelName' | sort | uniq -c | sort -rn
+fi
+```
+
+### Step 3: Generate Recommendations
+
+Based on patterns found, output recommendations:
+
+**If high Opus usage (>40%) and no ecomode:**
+- "Consider using ecomode for routine tasks to save tokens"
+
+**If no pipeline usage:**
+- "Try /pipeline for code review workflows"
+
+**If no security-reviewer usage:**
+- "Use security-reviewer after auth/API changes"
+
+**If defaultExecutionMode not set:**
+- "Set defaultExecutionMode in /omc-setup for consistent behavior"
+
+### Step 4: Output Report
+
+Format a nice summary with:
+- Token summary (total, by model)
+- Top agents used
+- Underutilized features
+- Personalized recommendations
+
+### Graceful Degradation
+
+If no data found:
+```
+📊 Limited Usage Data Available
+
+No token tracking found. To enable tracking:
+1. Ensure ~/.omc/state/ directory exists
+2. Run any OMC command to start tracking
+
+Tip: Run /omc-setup to configure OMC properly.
+```
+
+## Example Output
+
+```
+📊 Your OMC Usage Analysis
+
+TOKEN SUMMARY:
+- Total records: 1,234
+- By Model: opus 45%, sonnet 40%, haiku 15%
+
+TOP AGENTS:
+1. executor (234 uses)
+2. architect (89 uses)
+3. explore (67 uses)
+
+UNDERUTILIZED FEATURES:
+- ecomode: 0 uses (could save ~30% on routine tasks)
+- pipeline: 0 uses (great for review workflows)
+
+RECOMMENDATIONS:
+1. Set defaultExecutionMode: "ecomode" to save tokens
+2. Try /pipeline review for PR reviews
+3. Use explore agent before architect to save context
+```

package/skills/mcp-setup/SKILL.md

@@ -9,7 +9,7 @@ Configure Model Context Protocol (MCP) servers to extend Claude Code's capabilit
 
 ## Overview
 
-MCP servers provide additional tools that Claude Code agents can use. This skill helps you configure popular MCP servers in your `~/.claude/settings.json`.
+MCP servers provide additional tools that Claude Code agents can use. This skill helps you configure popular MCP servers using the `claude mcp add` command-line interface.
 
 ## Step 1: Show Available MCP Servers
 
@@ -55,95 +55,51 @@ Do you have a GitHub Personal Access Token?
 - Enter your token, or type 'skip' to configure later
 ```
 
-## Step 3: Update settings.json
+## Step 3: Add MCP Servers Using CLI
 
-Read the current `~/.claude/settings.json` and add/update the `mcpServers` section.
+Use the `claude mcp add` command to configure each MCP server. The CLI automatically handles settings.json updates and merging.
 
 ### Context7 Configuration:
-```json
-{
-  "mcpServers": {
-    "context7": {
-      "command": "npx",
-      "args": ["-y", "@upstash/context7-mcp"]
-    }
-  }
-}
+```bash
+claude mcp add context7 -- npx -y @upstash/context7-mcp
 ```
 
 ### Exa Web Search Configuration:
-```json
-{
-  "mcpServers": {
-    "exa": {
-      "command": "npx",
-      "args": ["-y", "exa-mcp-server"],
-      "env": {
-        "EXA_API_KEY": "<user-provided-key>"
-      }
-    }
-  }
-}
+```bash
+claude mcp add -e EXA_API_KEY=<user-provided-key> exa -- npx -y exa-mcp-server
 ```
 
 ### Filesystem Configuration:
-```json
-{
-  "mcpServers": {
-    "filesystem": {
-      "command": "npx",
-      "args": ["-y", "@modelcontextprotocol/server-filesystem", "<allowed-directories>"]
-    }
-  }
-}
+```bash
+claude mcp add filesystem -- npx -y @modelcontextprotocol/server-filesystem <allowed-directories>
 ```
 
 ### GitHub Configuration:
-```json
-{
-  "mcpServers": {
-    "github": {
-      "command": "docker",
-      "args": ["run", "-i", "--rm", "-e", "GITHUB_PERSONAL_ACCESS_TOKEN", "ghcr.io/github/github-mcp-server"],
-      "env": {
-        "GITHUB_PERSONAL_ACCESS_TOKEN": "<user-provided-token>"
-      }
-    }
-  }
-}
-```
-
-> Note: GitHub MCP requires Docker. Alternatively, configure as a remote URL: https://api.githubcopilot.com/mcp/
 
-## Step 4: Merge Configuration
-
-When updating settings.json:
-
-1. Read existing file: `~/.claude/settings.json`
-2. Parse as JSON (handle comments with jsonc-parser if needed)
-3. Merge new `mcpServers` entries with existing ones (don't overwrite user's other MCP servers)
-4. Write back to file with proper formatting
+**Option 1: Docker (local)**
+```bash
+claude mcp add -e GITHUB_PERSONAL_ACCESS_TOKEN=<user-provided-token> github -- docker run -i --rm -e GITHUB_PERSONAL_ACCESS_TOKEN ghcr.io/github/github-mcp-server
+```
 
+**Option 2: HTTP (remote)**
 ```bash
-# Backup existing settings first
-cp ~/.claude/settings.json ~/.claude/settings.json.bak 2>/dev/null || true
+claude mcp add --transport http github https://api.githubcopilot.com/mcp/
 ```
 
-Use the Edit tool or Write tool to update the settings file, preserving existing configuration.
+> Note: Docker option requires Docker installed. HTTP option is simpler but may have different capabilities.
 
-## Step 5: Verify Installation
+## Step 4: Verify Installation
 
 After configuration, verify the MCP servers are properly set up:
 
 ```bash
-# Check if settings.json has mcpServers
-grep -q "mcpServers" ~/.claude/settings.json && echo "MCP servers configured" || echo "Configuration may have failed"
-
-# List configured servers
-node -e "const s = require('$HOME/.claude/settings.json'); console.log('Configured MCP servers:', Object.keys(s.mcpServers || {}).join(', ') || 'none')"
+# List configured MCP servers
+claude mcp list
 ```
 
-## Step 6: Show Completion Message
+This will display all configured MCP servers and their status.
+
+## Step 5: Show Completion Message
 
 ```
 MCP Server Configuration Complete!
@@ -154,6 +110,7 @@ CONFIGURED SERVERS:
 NEXT STEPS:
 1. Restart Claude Code for changes to take effect
 2. The configured MCP tools will be available to all agents
+3. Run `claude mcp list` to verify configuration
 
 USAGE TIPS:
 - Context7: Ask about library documentation (e.g., "How do I use React hooks?")
@@ -162,11 +119,15 @@ USAGE TIPS:
 - GitHub: Interact with GitHub repos, issues, and PRs
 
 TROUBLESHOOTING:
-- If MCP servers don't appear, check ~/.claude/settings.json for syntax errors
-- Ensure you have Node.js 18+ installed for npx commands
+- If MCP servers don't appear, run `claude mcp list` to check status
+- Ensure you have Node.js 18+ installed for npx-based servers
+- For GitHub Docker option, ensure Docker is installed and running
 - Run /oh-my-claudecode:doctor to diagnose issues
 
-To add more MCP servers later, run: /oh-my-claudecode:mcp-setup
+MANAGING MCP SERVERS:
+- Add more servers: /oh-my-claudecode:mcp-setup or `claude mcp add ...`
+- List servers: `claude mcp list`
+- Remove a server: `claude mcp remove <server-name>`
 ```
 
 ## Custom MCP Server
@@ -175,23 +136,50 @@ If user selects "Custom":
 
 Ask for:
 1. Server name (identifier)
-2. Command to run (e.g., `npx`, `node`, path to executable)
-3. Arguments (comma-separated)
-4. Environment variables (optional, key=value pairs)
+2. Transport type: `stdio` (default) or `http`
+3. For stdio: Command and arguments (e.g., `npx my-mcp-server`)
+4. For http: URL (e.g., `https://example.com/mcp`)
+5. Environment variables (optional, key=value pairs)
+6. HTTP headers (optional, for http transport only)
+
+Then construct and run the appropriate `claude mcp add` command:
+
+**For stdio servers:**
+```bash
+# Without environment variables
+claude mcp add <server-name> -- <command> [args...]
+
+# With environment variables
+claude mcp add -e KEY1=value1 -e KEY2=value2 <server-name> -- <command> [args...]
+```
 
-Then add to mcpServers section accordingly.
+**For HTTP servers:**
+```bash
+# Basic HTTP server
+claude mcp add --transport http <server-name> <url>
+
+# HTTP server with headers
+claude mcp add --transport http --header "Authorization: Bearer <token>" <server-name> <url>
+```
 
 ## Common Issues
 
 ### MCP Server Not Loading
 - Ensure Node.js 18+ is installed
 - Check that npx is available in PATH
-- Verify no JSON syntax errors in settings.json
+- Run `claude mcp list` to verify server status
+- Check server logs for errors
 
 ### API Key Issues
 - Exa: Verify key at https://dashboard.exa.ai
-- GitHub: Ensure token has required scopes
+- GitHub: Ensure token has required scopes (repo, read:org)
+- Re-run `claude mcp add` with correct credentials if needed
 
 ### Agents Still Using Built-in Tools
 - Restart Claude Code after configuration
 - The built-in websearch will be deprioritized when exa is configured
+- Run `claude mcp list` to confirm servers are active
+
+### Removing or Updating a Server
+- Remove: `claude mcp remove <server-name>`
+- Update: Remove the old server, then add it again with new configuration

package/skills/omc-setup/SKILL.md

@@ -338,14 +338,14 @@ That's it! Just use Claude Code normally.
 OMC Setup Complete! (Upgraded from 2.x)
 
 GOOD NEWS: Your existing commands still work!
-- /ralph, /ultrawork, /planner, etc. all still function
+- /ralph, /ultrawork, /plan, etc. all still function
 
 WHAT'S NEW in 3.0:
 You no longer NEED those commands. Everything is automatic now:
 - Just say "don't stop until done" instead of /ralph
 - Just say "fast" or "parallel" instead of /ultrawork
-- Just say "plan this" instead of /planner
-- Just say "stop" instead of /cancel-ralph
+- Just say "plan this" instead of /plan
+- Just say "stop" instead of /cancel
 
 MAGIC KEYWORDS (power-user shortcuts):
 | Keyword | Same as old... | Example |
@@ -354,7 +354,7 @@ MAGIC KEYWORDS (power-user shortcuts):
 | ralplan | /ralplan | "ralplan this feature" |
 | ulw | /ultrawork | "ulw refactor API" |
 | eco | (new!) | "eco fix all errors" |
-| plan | /planner | "plan the endpoints" |
+| plan | /plan | "plan the endpoints" |
 
 HUD STATUSLINE:
 The status bar now shows OMC state. Restart Claude Code to see it.