oh-my-claude-sisyphus 3.3.6 → 3.3.8

package/skills/autopilot/SKILL.md

@@ -22,9 +22,9 @@ Autopilot is the ultimate hands-off mode. Give it a brief product idea (2-3 line
 ## Usage
 
 ```
-/autopilot <your idea>
-/ap "A CLI tool that tracks daily habits"
-/autopilot Add dark mode to the app
+/oh-my-claudecode:autopilot <your idea>
+/oh-my-claudecode:ap "A CLI tool that tracks daily habits"
+/oh-my-claudecode:autopilot Add dark mode to the app
 ```
 
 ## Magic Keywords
@@ -115,7 +115,7 @@ Optional settings in `.claude/settings.json`:
 ## Cancellation
 
 ```
-/cancel-autopilot
+/oh-my-claudecode:cancel-autopilot
 ```
 
 Or say: "stop", "cancel", "abort"
@@ -124,23 +124,23 @@ Progress is preserved for resume.
 
 ## Resume
 
-If autopilot was cancelled or failed, just run `/autopilot` again to resume from where it stopped.
+If autopilot was cancelled or failed, just run `/oh-my-claudecode:autopilot` again to resume from where it stopped.
 
 ## Examples
 
 **New Project:**
 ```
-/autopilot A REST API for a bookstore inventory with CRUD operations
+/oh-my-claudecode:autopilot A REST API for a bookstore inventory with CRUD operations
 ```
 
 **Feature Addition:**
 ```
-/autopilot Add user authentication with JWT tokens
+/oh-my-claudecode:autopilot Add user authentication with JWT tokens
 ```
 
 **Enhancement:**
 ```
-/ap Add dark mode support with system preference detection
+/oh-my-claudecode:ap Add dark mode support with system preference detection
 ```
 
 ## Best Practices

package/skills/cancel-autopilot/SKILL.md

@@ -17,7 +17,7 @@ Cancel an active autopilot session gracefully.
 ## Usage
 
 ```
-/cancel-autopilot
+/oh-my-claudecode:cancel-autopilot
 ```
 
 Or say: "stop autopilot", "cancel autopilot", "abort autopilot"
@@ -37,14 +37,14 @@ When cancelled, autopilot preserves:
 - Spec and plan files
 - Validation verdicts
 
-Run `/autopilot` to resume from where you left off.
+Run `/oh-my-claudecode:autopilot` to resume from where you left off.
 
 ## Force Clear
 
 To completely clear all state (no resume):
 
 ```
-/cancel-autopilot --clear
+/oh-my-claudecode:cancel-autopilot --clear
 ```
 
 This removes all autopilot files including:

package/skills/cancel-ralph/SKILL.md

@@ -35,9 +35,9 @@ After running this command, you are free to stop working. The persistent mode ho
 
 ## Note on Linked Modes
 
-Since v3.0, Ralph automatically activates Ultrawork for parallel execution. When you cancel Ralph, the linked Ultrawork is also cancelled. If you started Ultrawork separately (not via Ralph), use `/cancel-ultrawork` to cancel it independently.
+Since v3.0, Ralph automatically activates Ultrawork for parallel execution. When you cancel Ralph, the linked Ultrawork is also cancelled. If you started Ultrawork separately (not via Ralph), use `/oh-my-claudecode:cancel-ultrawork` to cancel it independently.
 
 ## To Start Fresh
 
-- `/ralph "task"` - Start ralph with ultrawork (default)
-- `/ultrawork "task"` - Start ultrawork only (standalone)
+- `/oh-my-claudecode:ralph "task"` - Start ralph with ultrawork (default)
+- `/oh-my-claudecode:ultrawork "task"` - Start ultrawork only (standalone)

package/skills/cancel-ultraqa/SKILL.md

@@ -22,8 +22,8 @@ After running this command, the QA cycling will stop.
 
 ## To Start Fresh
 
-- `/ultraqa --tests` - Run until all tests pass
-- `/ultraqa --build` - Run until build succeeds
-- `/ultraqa --lint` - Run until no lint errors
-- `/ultraqa --typecheck` - Run until no type errors
-- `/ultraqa --custom "pattern"` - Run until pattern matches
+- `/oh-my-claudecode:ultraqa --tests` - Run until all tests pass
+- `/oh-my-claudecode:ultraqa --build` - Run until build succeeds
+- `/oh-my-claudecode:ultraqa --lint` - Run until no lint errors
+- `/oh-my-claudecode:ultraqa --typecheck` - Run until no type errors
+- `/oh-my-claudecode:ultraqa --custom "pattern"` - Run until pattern matches

package/skills/cancel-ultrawork/SKILL.md

@@ -18,7 +18,7 @@ The Ultrawork mode has been cancelled. Clearing state files.
 cat .omc/ultrawork-state.json 2>/dev/null | jq -r '.linked_to_ralph // false'
 ```
 
-**If linked_to_ralph is true**: Use `/cancel-ralph` instead to cancel both Ralph and its linked Ultrawork.
+**If linked_to_ralph is true**: Use `/oh-my-claudecode:cancel-ralph` instead to cancel both Ralph and its linked Ultrawork.
 
 **Otherwise**, execute this command to cancel Ultrawork:
 
@@ -33,10 +33,10 @@ After running this command, ultrawork mode will be deactivated and the HUD will
 ## Note on Linked Modes
 
 Since v3.0, Ralph automatically activates Ultrawork. If you see `linked_to_ralph: true` in the ultrawork state, it means Ultrawork was auto-activated by Ralph. In this case:
-- Use `/cancel-ralph` to cancel both modes
+- Use `/oh-my-claudecode:cancel-ralph` to cancel both modes
 - If you only cancel ultrawork, Ralph will continue but without parallel execution benefits
 
 ## To Start Fresh
 
-- `/ultrawork "task"` - Start ultrawork only (standalone)
-- `/ralph "task"` - Start ralph with ultrawork (default)
+- `/oh-my-claudecode:ultrawork "task"` - Start ultrawork only (standalone)
+- `/oh-my-claudecode:ralph "task"` - Start ralph with ultrawork (default)

package/skills/hud/SKILL.md

@@ -14,16 +14,16 @@ Configure the OMC HUD (Heads-Up Display) for the statusline.
 
 | Command | Description |
 |---------|-------------|
-| `/hud` | Show current HUD status (auto-setup if needed) |
-| `/hud setup` | Install/repair HUD statusline |
-| `/hud minimal` | Switch to minimal display |
-| `/hud focused` | Switch to focused display (default) |
-| `/hud full` | Switch to full display |
-| `/hud status` | Show detailed HUD status |
+| `/oh-my-claudecode:hud` | Show current HUD status (auto-setup if needed) |
+| `/oh-my-claudecode:hud setup` | Install/repair HUD statusline |
+| `/oh-my-claudecode:hud minimal` | Switch to minimal display |
+| `/oh-my-claudecode:hud focused` | Switch to focused display (default) |
+| `/oh-my-claudecode:hud full` | Switch to full display |
+| `/oh-my-claudecode:hud status` | Show detailed HUD status |
 
 ## Auto-Setup
 
-When you run `/hud` or `/hud setup`, the system will automatically:
+When you run `/oh-my-claudecode:hud` or `/oh-my-claudecode:hud setup`, the system will automatically:
 1. Check if `~/.claude/hud/omc-hud.mjs` exists
 2. Check if `statusLine` is configured in `~/.claude/settings.json`
 3. If missing, create the HUD wrapper script and configure settings
@@ -226,9 +226,9 @@ You can manually edit the config file:
 ## Troubleshooting
 
 If the HUD is not showing:
-1. Run `/hud setup` to auto-install and configure
+1. Run `/oh-my-claudecode:hud setup` to auto-install and configure
 2. Restart Claude Code after setup completes
-3. If still not working, run `/doctor` for full diagnostics
+3. If still not working, run `/oh-my-claudecode:doctor` for full diagnostics
 
 Manual verification:
 - HUD script: `~/.claude/hud/omc-hud.mjs`

package/skills/learner/SKILL.md

@@ -27,7 +27,7 @@ If a potential skill fails any of these questions, it's not worth saving.
 
 ## Recognition Pattern
 
-Use /learner ONLY after:
+Use /oh-my-claudecode:learner ONLY after:
 - Solving a tricky bug that required deep investigation
 - Discovering a non-obvious workaround specific to this codebase
 - Finding a hidden gotcha that wastes time when forgotten
@@ -132,5 +132,5 @@ If code helps, show it - but as illustration of the principle, not copy-paste ma
 
 ## Related Commands
 
-- /note - Save quick notes that survive compaction (less formal than skills)
-- /ralph - Start a development loop with learning capture
+- /oh-my-claudecode:note - Save quick notes that survive compaction (less formal than skills)
+- /oh-my-claudecode:ralph - Start a development loop with learning capture

package/skills/mcp-setup/SKILL.md

@@ -0,0 +1,196 @@
+---
+name: mcp-setup
+description: Configure popular MCP servers for enhanced agent capabilities
+user-invocable: true
+---
+
+# MCP Setup
+
+Configure Model Context Protocol (MCP) servers to extend Claude Code's capabilities with external tools like web search, file system access, and GitHub integration.
+
+## 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`.
+
+## Step 1: Show Available MCP Servers
+
+Present the user with available MCP server options using AskUserQuestion:
+
+**Question:** "Which MCP server would you like to configure?"
+
+**Options:**
+1. **Context7** - Documentation and code context from popular libraries
+2. **Exa Web Search** - Enhanced web search (replaces built-in websearch)
+3. **Filesystem** - Extended file system access with additional capabilities
+4. **GitHub** - GitHub API integration for issues, PRs, and repository management
+5. **All of the above** - Configure all recommended MCP servers
+6. **Custom** - Add a custom MCP server
+
+## Step 2: Gather Required Information
+
+### For Context7:
+No API key required. Ready to use immediately.
+
+### For Exa Web Search:
+Ask for API key:
+```
+Do you have an Exa API key?
+- Get one at: https://exa.ai
+- Enter your API key, or type 'skip' to configure later
+```
+
+### For Filesystem:
+Ask for allowed directories:
+```
+Which directories should the filesystem MCP have access to?
+Default: Current working directory
+Enter comma-separated paths, or press Enter for default
+```
+
+### For GitHub:
+Ask for token:
+```
+Do you have a GitHub Personal Access Token?
+- Create one at: https://github.com/settings/tokens
+- Recommended scopes: repo, read:org
+- Enter your token, or type 'skip' to configure later
+```
+
+## Step 3: Update settings.json
+
+Read the current `~/.claude/settings.json` and add/update the `mcpServers` section.
+
+### Context7 Configuration:
+```json
+{
+  "mcpServers": {
+    "context7": {
+      "command": "npx",
+      "args": ["-y", "@context7/mcp"]
+    }
+  }
+}
+```
+
+### Exa Web Search Configuration:
+```json
+{
+  "mcpServers": {
+    "exa": {
+      "command": "npx",
+      "args": ["-y", "@anthropic/exa-mcp-server"],
+      "env": {
+        "EXA_API_KEY": "<user-provided-key>"
+      }
+    }
+  }
+}
+```
+
+### Filesystem Configuration:
+```json
+{
+  "mcpServers": {
+    "filesystem": {
+      "command": "npx",
+      "args": ["-y", "@anthropic/mcp-server-filesystem", "<allowed-directories>"]
+    }
+  }
+}
+```
+
+### GitHub Configuration:
+```json
+{
+  "mcpServers": {
+    "github": {
+      "command": "npx",
+      "args": ["-y", "@anthropic/github-mcp-server"],
+      "env": {
+        "GITHUB_TOKEN": "<user-provided-token>"
+      }
+    }
+  }
+}
+```
+
+## 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
+
+```bash
+# Backup existing settings first
+cp ~/.claude/settings.json ~/.claude/settings.json.bak 2>/dev/null || true
+```
+
+Use the Edit tool or Write tool to update the settings file, preserving existing configuration.
+
+## Step 5: 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')"
+```
+
+## Step 6: Show Completion Message
+
+```
+MCP Server Configuration Complete!
+
+CONFIGURED SERVERS:
+[List the servers that were configured]
+
+NEXT STEPS:
+1. Restart Claude Code for changes to take effect
+2. The configured MCP tools will be available to all agents
+
+USAGE TIPS:
+- Context7: Ask about library documentation (e.g., "How do I use React hooks?")
+- Exa: Use for web searches (e.g., "Search the web for latest TypeScript features")
+- Filesystem: Extended file operations beyond the working directory
+- 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
+- Run /oh-my-claudecode:doctor to diagnose issues
+
+To add more MCP servers later, run: /oh-my-claudecode:mcp-setup
+```
+
+## Custom MCP Server
+
+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)
+
+Then add to mcpServers section accordingly.
+
+## 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
+
+### API Key Issues
+- Exa: Verify key at https://dashboard.exa.ai
+- GitHub: Ensure token has required scopes
+
+### Agents Still Using Built-in Tools
+- Restart Claude Code after configuration
+- The built-in websearch will be deprioritized when exa is configured

package/skills/note/SKILL.md

@@ -12,12 +12,12 @@ Save important context to `.omc/notepad.md` that survives conversation compactio
 
 | Command | Action |
 |---------|--------|
-| `/note <content>` | Add to Working Memory with timestamp |
-| `/note --priority <content>` | Add to Priority Context (always loaded) |
-| `/note --manual <content>` | Add to MANUAL section (never pruned) |
-| `/note --show` | Display current notepad contents |
-| `/note --prune` | Remove entries older than 7 days |
-| `/note --clear` | Clear Working Memory (keep Priority + MANUAL) |
+| `/oh-my-claudecode:note <content>` | Add to Working Memory with timestamp |
+| `/oh-my-claudecode:note --priority <content>` | Add to Priority Context (always loaded) |
+| `/oh-my-claudecode:note --manual <content>` | Add to MANUAL section (never pruned) |
+| `/oh-my-claudecode:note --show` | Display current notepad contents |
+| `/oh-my-claudecode:note --prune` | Remove entries older than 7 days |
+| `/oh-my-claudecode:note --clear` | Clear Working Memory (keep Priority + MANUAL) |
 
 ## Sections
 
@@ -39,11 +39,11 @@ Save important context to `.omc/notepad.md` that survives conversation compactio
 ## Examples
 
 ```
-/note Found auth bug in UserContext - missing useEffect dependency
-/note --priority Project uses TypeScript strict mode, all files in src/
-/note --manual Contact: api-team@company.com for backend questions
-/note --show
-/note --prune
+/oh-my-claudecode:note Found auth bug in UserContext - missing useEffect dependency
+/oh-my-claudecode:note --priority Project uses TypeScript strict mode, all files in src/
+/oh-my-claudecode:note --manual Contact: api-team@company.com for backend questions
+/oh-my-claudecode:note --show
+/oh-my-claudecode:note --prune
 ```
 
 ## Behavior

package/skills/omc-setup/SKILL.md

@@ -151,7 +151,20 @@ fi
 grep -q "oh-my-claudecode" ~/.claude/settings.json && echo "Plugin verified" || echo "Plugin NOT found - run: claude /install-plugin oh-my-claudecode"
 ```
 
-## Step 5: Detect Upgrade from 2.x
+## Step 5: Offer MCP Server Configuration
+
+MCP servers extend Claude Code with additional tools (web search, GitHub, etc.).
+
+Ask user: "Would you like to configure MCP servers for enhanced capabilities? (Context7, Exa search, GitHub, etc.)"
+
+If yes, invoke the mcp-setup skill:
+```
+/oh-my-claudecode:mcp-setup
+```
+
+If no, skip to next step.
+
+## Step 6: Detect Upgrade from 2.x
 
 Check if user has existing configuration:
 ```bash
@@ -161,7 +174,7 @@ ls ~/.claude/commands/ralph-loop.md 2>/dev/null || ls ~/.claude/commands/ultrawo
 
 If found, this is an upgrade from 2.x.
 
-## Step 6: Show Welcome Message
+## Step 7: Show Welcome Message
 
 ### For New Users:
 
@@ -188,6 +201,9 @@ Just include these words naturally in your request:
 
 Combine them: "ralph ulw: migrate the database"
 
+MCP SERVERS:
+Run /oh-my-claudecode:mcp-setup to add tools like web search, GitHub, etc.
+
 HUD STATUSLINE:
 The status bar now shows OMC state. Restart Claude Code to see it.
 

package/skills/ralph-init/SKILL.md

@@ -55,7 +55,7 @@ Started: [ISO timestamp]
 3. **Independent stories**: Minimize dependencies between stories
 4. **Priority order**: Foundational work (DB, types) before UI
 
-After creating files, report summary and suggest running `/ralph-loop` to start.
+After creating files, report summary and suggest running `/oh-my-claudecode:ralph-loop` to start.
 
 Task to break down:
 {{ARGUMENTS}}

package/skills/ralplan/SKILL.md

@@ -77,6 +77,38 @@ Ralplan maintains persistent state in `.omc/ralplan-state.json` to track progres
 
 **Phases**: `planner_planning` → `architect_consultation` → `critic_review` → `handling_verdict` → `complete`
 
+## Plan Mode Interaction (CRITICAL)
+
+**When ralplan is invoked while Plan mode is active:**
+
+The Planner agent has a PHASE 3.5 (CONFIRMATION) that normally requires user confirmation before proceeding. **This MUST be bypassed within ralplan because the Critic serves as the reviewer, not the user.**
+
+### Mandatory Constraints
+
+| Constraint | Rationale |
+|------------|-----------|
+| **Planner MUST skip PHASE 3.5 confirmation** | Critic reviews the plan, not the user |
+| **Critic MUST run before any plan approval** | No plan is approved without Critic verdict |
+| **DO NOT exit plan mode until Critic has rendered verdict** | Premature exit skips the review step |
+| **Log `[RALPLAN] Critic review required before approval`** | Observability for debugging |
+
+### Flow When Plan Mode Is Active
+
+```
+1. Orchestrator invokes ralplan skill
+2. Log: [RALPLAN] Starting - Critic review will be required
+3. Spawn Planner in DIRECT PLANNING MODE (no interview, no confirmation)
+4. Planner outputs PLAN_READY: <path>
+5. Log: [RALPLAN] Plan ready, invoking Critic for review
+6. Spawn Critic with plan path  <-- MUST HAPPEN
+7. Critic renders OKAY or REJECT
+8. ONLY THEN can plan be approved or refined
+```
+
+**CRITICAL: The Critic invocation is MANDATORY. If the Planner completes and signals plan ready, the orchestrator MUST invoke the Critic before any form of plan approval or user confirmation.**
+
+---
+
 ## Execution Protocol
 
 ### Initialization
@@ -98,12 +130,15 @@ The skill begins by establishing the planning environment:
 The Planner creates an initial plan based on task context:
 
 - Invoke Planner in **direct planning mode** (bypassing interview since task context is pre-gathered)
+- **CRITICAL: Planner MUST skip PHASE 3.5 (CONFIRMATION)** - the Critic will review, not the user
 - Planner receives task context directly without preliminary questioning
 - Planner mandatorily consults with Metis for gap detection
 - Planner generates plan directly to `.omc/plans/[feature-name].md`
 - Plan includes: requirements summary, concrete acceptance criteria, specific implementation steps with file references, risk identification with mitigations, and verification steps
 - Signal completion with `PLAN_READY: .omc/plans/[filename].md`
+- **After PLAN_READY: DO NOT approve or confirm the plan. Proceed to Critic Review.**
 - Extract plan path from completion signal and update state
+- Log: `[RALPLAN] Critic review required before approval`
 
 ### Architect Consultation (Conditional)
 
@@ -114,7 +149,11 @@ The Architect provides strategic guidance in two scenarios:
 
 When invoked, the Architect receives file paths to read for analysis, not summaries. This enables thorough examination of the existing codebase context before providing recommendations.
 
-### Critic Review
+### Critic Review (MANDATORY - CANNOT BE SKIPPED)
+
+**CRITICAL: This phase MUST execute. The Critic is the gatekeeper for plan approval.**
+
+Log at start: `[RALPLAN] Invoking Critic for plan review`
 
 The Critic examines the plan against quality standards:
 
@@ -122,6 +161,14 @@ The Critic examines the plan against quality standards:
 - Critic conducts thorough review of plan completeness and feasibility
 - Critic emits verdict: either `OKAY` (approval) or `REJECT` with specific issues
 
+**Enforcement Rules:**
+1. If Planner signals PLAN_READY, Critic MUST be invoked immediately
+2. DO NOT exit ralplan loop before Critic verdict
+3. DO NOT request user confirmation before Critic verdict
+4. DO NOT trigger any plan mode exit behavior before Critic verdict
+
+Log after Critic completes: `[RALPLAN] Critic verdict: <OKAY|REJECT>`
+
 ### Verdict Handling and Iteration
 
 Based on Critic's verdict, the skill either approves the plan or continues iteration:
@@ -129,7 +176,7 @@ Based on Critic's verdict, the skill either approves the plan or continues itera
 **If verdict is OKAY:**
 - Mark plan as approved
 - Log approval with iteration count
-- Prepare plan for execution with `/ralph` or manual orchestration
+- Prepare plan for execution with `/oh-my-claudecode:ralph` or manual orchestration
 - Set state `active: false, current_phase: "complete"`
 
 **If verdict is REJECT:**
@@ -205,15 +252,21 @@ CRITIC_FEEDBACK:
 
 To stop an active ralplan session:
 
-- Use `/cancel-ralph` (automatically detects ralplan via state file)
+- Use `/oh-my-claudecode:cancel-ralph` (automatically detects ralplan via state file)
 - Or manually delete `.omc/ralplan-state.json`
 
 ## Skill Workflow
 
 1. **Initialize state** and log: `[RALPLAN Iteration 0/5] Initializing...`
 2. **Parse task** from user input
-3. **Spawn Planner** in direct planning mode
-4. **Iterate** through planning loop with observability logging at each phase
-5. **Complete** when Critic approves or max iterations reached with warnings
+3. **Spawn Planner** in direct planning mode (SKIP Planner's PHASE 3.5 confirmation)
+4. **Wait for PLAN_READY** signal from Planner
+5. **Log:** `[RALPLAN] Critic review required before approval`
+6. **Invoke Critic** with plan file path (MANDATORY - CANNOT BE SKIPPED)
+7. **Log:** `[RALPLAN] Critic verdict: <verdict>`
+8. **Handle verdict** - if REJECT, loop back to step 3 with feedback
+9. **Complete** ONLY when Critic approves or max iterations reached with warnings
+
+**HARD RULE:** Steps 5-7 are NON-NEGOTIABLE. No plan approval, user confirmation, or plan mode exit can occur before the Critic has rendered its verdict. This prevents the plan mode confirmation flow from short-circuiting the ralplan review loop.
 
 The iterative loop refines the plan until it meets the rigorous standards of all three agents, ensuring comprehensive, architecturally sound work plans ready for execution.

package/skills/release/SKILL.md

@@ -11,10 +11,10 @@ Automate the release process for oh-my-claudecode.
 ## Usage
 
 ```
-/release <version>
+/oh-my-claudecode:release <version>
 ```
 
-Example: `/release 2.4.0` or `/release patch` or `/release minor`
+Example: `/oh-my-claudecode:release 2.4.0` or `/oh-my-claudecode:release patch` or `/oh-my-claudecode:release minor`
 
 ## Release Checklist
 

package/skills/research/SKILL.md

@@ -21,20 +21,20 @@ Research is a multi-stage workflow that decomposes complex research goals into p
 ## Usage Examples
 
 ```
-/research <goal>                    # Standard research with user checkpoints
-/research AUTO: <goal>              # Fully autonomous until complete
-/research status                    # Check current research session status
-/research resume                    # Resume interrupted research session
-/research list                      # List all research sessions
-/research report <session-id>       # Generate report for session
+/oh-my-claudecode:research <goal>                    # Standard research with user checkpoints
+/oh-my-claudecode:research AUTO: <goal>              # Fully autonomous until complete
+/oh-my-claudecode:research status                    # Check current research session status
+/oh-my-claudecode:research resume                    # Resume interrupted research session
+/oh-my-claudecode:research list                      # List all research sessions
+/oh-my-claudecode:research report <session-id>       # Generate report for session
 ```
 
 ### Quick Examples
 
 ```
-/research What are the performance characteristics of different sorting algorithms?
-/research AUTO: Analyze authentication patterns in this codebase
-/research How does the error handling work across the API layer?
+/oh-my-claudecode:research What are the performance characteristics of different sorting algorithms?
+/oh-my-claudecode:research AUTO: Analyze authentication patterns in this codebase
+/oh-my-claudecode:research How does the error handling work across the API layer?
 ```
 
 ## Research Protocol
@@ -151,7 +151,7 @@ Pending stages: {{PENDING_STAGES}}
 ### AUTO Mode Example
 
 ```
-/research AUTO: Comprehensive security analysis of the authentication system
+/oh-my-claudecode:research AUTO: Comprehensive security analysis of the authentication system
 
 [Decomposition]
 - Stage 1 (LOW): Enumerate auth-related files
@@ -281,12 +281,12 @@ Batch 2: Stages 6-7 (parallel)
 
 | Command | Action |
 |---------|--------|
-| `/research status` | Show current session progress |
-| `/research resume` | Resume most recent interrupted session |
-| `/research resume <session-id>` | Resume specific session |
-| `/research list` | List all sessions with status |
-| `/research report <session-id>` | Generate/regenerate report |
-| `/research cancel` | Cancel current session (preserves state) |
+| `/oh-my-claudecode:research status` | Show current session progress |
+| `/oh-my-claudecode:research resume` | Resume most recent interrupted session |
+| `/oh-my-claudecode:research resume <session-id>` | Resume specific session |
+| `/oh-my-claudecode:research list` | List all sessions with status |
+| `/oh-my-claudecode:research report <session-id>` | Generate/regenerate report |
+| `/oh-my-claudecode:research cancel` | Cancel current session (preserves state) |
 
 ## Tag Extraction
 
@@ -481,7 +481,7 @@ Optional settings in `.claude/settings.json`:
 ## Cancellation
 
 ```
-/cancel-research
+/oh-my-claudecode:cancel-research
 ```
 
 Or say: "stop research", "cancel research", "abort"