oh-my-claude-sisyphus 3.5.3 → 3.5.6

package/commands/planner.md

@@ -1,174 +0,0 @@
----
-description: Strategic planning consultant with interview workflow
-aliases: [planning, plan-interview]
----
-
-# Planner Command
-
-[PLANNER MODE ACTIVATED - INTERVIEW WORKFLOW]
-
-You are activating the Planner agent, a strategic planning consultant who creates comprehensive work plans through interview-style interaction.
-
-## User's Request
-
-{{ARGUMENTS}}
-
-## What Planner Does
-
-The Planner guides users through planning by:
-
-1. **Interview Phase** - Asks clarifying questions about requirements, constraints, goals
-2. **Analysis Phase** - Consults Analyst for hidden requirements and risk analysis
-3. **Plan Creation** - Creates detailed, actionable work plans
-
-## How It's Different from `/plan`
-
-| Command | Workflow | Use When |
-|---------|----------|----------|
-| `/planner` | Full interview workflow | Requirements unclear, complex project |
-| `/plan` | Quick planning, no interview | Requirements clear, simple task |
-
-## Interview Protocol
-
-The Planner follows strict interview discipline:
-
-### Single Question at a Time
-
-**NEVER** ask multiple questions in one message.
-
-**Good:**
-```
-What's the primary scope for this feature?
-```
-
-**Bad:**
-```
-What's the scope? And the timeline? And who's the audience?
-```
-
-### Question Categories
-
-The Planner asks about:
-- **Goals** - What success looks like
-- **Constraints** - Time, budget, technical limits
-- **Context** - Existing systems, dependencies
-- **Risks** - What could go wrong
-- **Preferences** - Trade-offs (speed vs quality)
-
-### Using AskUserQuestion Tool
-
-For preference questions, the Planner uses `AskUserQuestion` tool to provide clickable UI:
-
-**Question types requiring AskUserQuestion:**
-- Preference (speed vs quality)
-- Requirement (deadline)
-- Scope (include feature Y?)
-- Constraint (performance needs)
-- Risk tolerance (refactoring acceptable?)
-
-**Example:**
-```
-AskUserQuestion(
-  question="For performance, what matters more - latency or throughput?",
-  type="preference",
-  options=["Latency", "Throughput", "Both equally"]
-)
-```
-
-## Plan Quality Criteria
-
-Planner ensures:
-- 80%+ claims cite file/line references
-- 90%+ acceptance criteria are testable
-- No vague terms without metrics
-- All risks have mitigations
-
-## Transition to Plan Creation
-
-Planner creates the plan when user says:
-- "Create the plan"
-- "Make it into a work plan"
-- "I'm ready to plan"
-- "Let's create the plan"
-
-## Plan Structure
-
-The final plan includes:
-
-1. **Requirements Summary** - What was gathered from interview
-2. **Acceptance Criteria** - Testable conditions for completion
-3. **Implementation Steps** - With file references
-4. **Risks & Mitigations** - What could go wrong and how to handle
-5. **Verification Steps** - How to verify completion
-
-## Delegation to Planner Agent
-
-This command delegates to the `planner` agent (Opus model) which follows the full interview workflow.
-
-```
-Task(
-  subagent_type="oh-my-claudecode:planner",
-  model="opus",
-  prompt="PLANNING REQUEST: {{ARGUMENTS}}
-
-Follow the interview workflow:
-1. Ask clarifying questions (one at a time)
-2. Use AskUserQuestion for preference questions
-3. Consult Analyst when ready
-4. Create plan when user confirms
-
-Quality requirements:
-- 80%+ claims cite file/line
-- 90%+ criteria testable
-- All risks have mitigations"
-)
-```
-
-## When to Use Planner vs Plan
-
-**Use `/planner` when:**
-- Requirements are vague or unclear
-- Complex project with many unknowns
-- Need to explore trade-offs
-- User needs guidance on what to consider
-
-**Use `/plan` when:**
-- Requirements are clear and specific
-- Simple, well-defined task
-- Just need structured task breakdown
-- No need for extensive questioning
-
-## Example Workflow
-
-```
-User: /oh-my-claudecode:planner add user authentication
-
-Planner: What's the primary scope for this authentication feature?
-
-User: JWT-based auth for our REST API
-
-Planner: For JWT implementation, what matters more - ease of integration or maximum security?
-
-User: Maximum security
-
-Planner: Should we support refresh tokens for long-lived sessions?
-
-User: Yes
-
-Planner: [Consults Analyst for hidden requirements]
-
-Planner: Ready to create the plan. I've identified 3 key risks. Shall I proceed?
-
-User: Yes, create the plan
-
-Planner: [Creates detailed plan with all sections]
-```
-
-## Output
-
-The Planner will:
-1. Conduct interview (as many questions as needed)
-2. Consult Analyst for analysis
-3. Create comprehensive plan document
-4. Save to `.omc/plans/` directory
-5. Report plan location and summary

package/skills/cancel-autopilot/SKILL.md

@@ -1,52 +0,0 @@
----
-name: cancel-autopilot
-description: Cancel active autopilot session
----
-
-# Cancel Autopilot Skill
-
-Cancel an active autopilot session gracefully.
-
-## What It Does
-
-- Stops the active autopilot workflow
-- Cleans up any active Ralph or UltraQA state
-- Preserves progress for potential resume
-
-## Usage
-
-```
-/oh-my-claudecode:cancel-autopilot
-```
-
-Or say: "stop autopilot", "cancel autopilot", "abort autopilot"
-
-## What Gets Cleaned Up
-
-1. **Autopilot state** - Marked as inactive (preserved for resume)
-2. **Ralph state** - Cleared if active
-3. **Ultrawork state** - Cleared if linked to Ralph
-4. **UltraQA state** - Cleared if active
-
-## Progress Preservation
-
-When cancelled, autopilot preserves:
-- Current phase
-- Files created/modified
-- Spec and plan files
-- Validation verdicts
-
-Run `/oh-my-claudecode:autopilot` to resume from where you left off.
-
-## Force Clear
-
-To completely clear all state (no resume):
-
-```
-/oh-my-claudecode:cancel-autopilot --clear
-```
-
-This removes all autopilot files including:
-- `.omc/autopilot-state.json`
-- `.omc/autopilot/` directory
-- `.omc/plans/autopilot-impl.md`

package/skills/cancel-ecomode/SKILL.md

@@ -1,41 +0,0 @@
----
-name: cancel-ecomode
-description: Cancel active Ecomode mode
----
-
-# Cancel Ecomode
-
-[ECOMODE CANCELLED]
-
-The Ecomode has been cancelled. Clearing state files.
-
-## MANDATORY ACTION
-
-**First**, check if ecomode is linked to an active Ralph loop:
-
-```bash
-cat .omc/ecomode-state.json 2>/dev/null | jq -r '.linked_to_ralph // false'
-```
-
-**If linked_to_ralph is true**: Use `/oh-my-claudecode:cancel-ralph` instead to cancel both Ralph and its linked Ecomode.
-
-**Otherwise**, execute this command to cancel Ecomode:
-
-```bash
-mkdir -p .omc && \
-echo '{"active": false, "cancelled_at": "'$(date -Iseconds)'", "reason": "User cancelled via /cancel-ecomode"}' > .omc/ecomode-state.json && \
-echo '{"active": false, "cancelled_at": "'$(date -Iseconds)'", "reason": "User cancelled via /cancel-ecomode"}' > ~/.claude/ecomode-state.json
-```
-
-After running this command, ecomode will be deactivated and the HUD will update.
-
-## Note on Linked Modes
-
-Since v3.5, Ralph can activate either Ultrawork OR Ecomode based on user preference. If you see `linked_to_ralph: true` in the ecomode state, it means Ecomode was auto-activated by Ralph. In this case:
-- Use `/oh-my-claudecode:cancel-ralph` to cancel both modes
-- If you only cancel ecomode, Ralph will continue but without parallel execution benefits
-
-## To Start Fresh
-
-- `/oh-my-claudecode:ecomode "task"` - Start ecomode only (standalone)
-- `/oh-my-claudecode:ralph "task"` - Start ralph with default execution mode

package/skills/cancel-ralph/SKILL.md

@@ -1,42 +0,0 @@
----
-name: cancel-ralph
-description: Cancel active Ralph (and linked ultrawork if auto-activated)
----
-
-# Cancel Ralph
-
-[RALPH CANCELLED]
-
-Ralph has been cancelled. You MUST now deactivate the state files.
-
-## MANDATORY ACTION
-
-Execute this command to fully cancel ALL persistent modes:
-
-```bash
-mkdir -p .omc ~/.claude && \
-echo '{"active": false, "cancelled_at": "'$(date -Iseconds)'", "reason": "User cancelled via /cancel-ralph"}' > .omc/ralph-state.json && \
-echo '{"active": false, "cancelled_at": "'$(date -Iseconds)'", "reason": "User cancelled via /cancel-ralph", "linked_to_ralph": false}' > .omc/ultrawork-state.json && \
-echo '{"active": false, "cancelled_at": "'$(date -Iseconds)'", "reason": "User cancelled via /cancel-ralph"}' > .omc/ralph-plan-state.json && \
-echo '{"active": false, "cancelled_at": "'$(date -Iseconds)'", "reason": "User cancelled via /cancel-ralph"}' > ~/.claude/ralph-state.json && \
-echo '{"active": false, "cancelled_at": "'$(date -Iseconds)'", "reason": "User cancelled via /cancel-ralph"}' > ~/.claude/ultrawork-state.json && \
-rm -f .omc/ralph-verification.json
-```
-
-After running this command, you are free to stop working. The persistent mode hook will no longer force continuation.
-
-## What Was Cancelled
-
-- **Ralph**: Self-referential completion loop
-- **Ultrawork**: Parallel execution mode (auto-activated with Ralph by default)
-- **Ralph Plan**: Iterative planning loop (if active via /ralplan)
-- **Verification State**: Any pending architect verification
-
-## 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 `/oh-my-claudecode:cancel-ultrawork` to cancel it independently.
-
-## To Start Fresh
-
-- `/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

@@ -1,28 +0,0 @@
----
-name: cancel-ultraqa
-description: Cancel active UltraQA cycling workflow
----
-
-# Cancel UltraQA
-
-[ULTRAQA CANCELLED]
-
-The UltraQA cycling workflow has been cancelled. Clearing state file.
-
-## MANDATORY ACTION
-
-Execute this command to cancel UltraQA:
-
-```bash
-mkdir -p .sisyphus && echo '{"active": false, "cancelled_at": "'$(date -Iseconds)'", "reason": "User cancelled via /cancel-ultraqa"}' > .omc/ultraqa-state.json
-```
-
-After running this command, the QA cycling will stop.
-
-## To Start Fresh
-
-- `/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

@@ -1,41 +0,0 @@
----
-name: cancel-ultrawork
-description: Cancel active Ultrawork mode
----
-
-# Cancel Ultrawork
-
-[ULTRAWORK CANCELLED]
-
-The Ultrawork mode has been cancelled. Clearing state files.
-
-## MANDATORY ACTION
-
-**First**, check if ultrawork is linked to an active Ralph loop:
-
-```bash
-cat .omc/ultrawork-state.json 2>/dev/null | jq -r '.linked_to_ralph // false'
-```
-
-**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:
-
-```bash
-mkdir -p .omc && \
-echo '{"active": false, "cancelled_at": "'$(date -Iseconds)'", "reason": "User cancelled via /cancel-ultrawork"}' > .omc/ultrawork-state.json && \
-echo '{"active": false, "cancelled_at": "'$(date -Iseconds)'", "reason": "User cancelled via /cancel-ultrawork"}' > ~/.claude/ultrawork-state.json
-```
-
-After running this command, ultrawork mode will be deactivated and the HUD will update.
-
-## 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 `/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
-
-- `/oh-my-claudecode:ultrawork "task"` - Start ultrawork only (standalone)
-- `/oh-my-claudecode:ralph "task"` - Start ralph with ultrawork (default)

package/skills/omc-default/SKILL.md

@@ -1,77 +0,0 @@
----
-name: omc-default
-description: Configure OMC in local project (.claude/CLAUDE.md)
----
-
-# OMC Default (Project-Scoped)
-
-## Task: Configure OMC Default Mode (Project-Scoped)
-
-**CRITICAL**: This skill ALWAYS downloads fresh CLAUDE.md from GitHub to your local project. DO NOT use the Write tool - use bash curl exclusively.
-
-### Step 1: Create Local .claude Directory
-
-Ensure the local project has a .claude directory:
-
-```bash
-# Create .claude directory in current project
-mkdir -p .claude && echo "✅ .claude directory created" || echo "❌ Failed to create .claude directory"
-```
-
-### Step 2: Download Fresh CLAUDE.md (MANDATORY)
-
-Execute this bash command to download fresh CLAUDE.md to local project config:
-
-```bash
-# Download fresh CLAUDE.md to project-local .claude/
-curl -fsSL "https://raw.githubusercontent.com/Yeachan-Heo/oh-my-claudecode/main/docs/CLAUDE.md" -o .claude/CLAUDE.md && \
-echo "✅ CLAUDE.md downloaded successfully to .claude/CLAUDE.md" || \
-echo "❌ Failed to download CLAUDE.md"
-```
-
-**Note**: The downloaded CLAUDE.md includes Context Persistence instructions with `<remember>` tags for surviving conversation compaction.
-
-**MANDATORY**: Always run this command. Do NOT skip. Do NOT use Write tool.
-
-**FALLBACK** if curl fails:
-Tell user to manually download from:
-https://raw.githubusercontent.com/Yeachan-Heo/oh-my-claudecode/main/docs/CLAUDE.md
-
-### Step 3: Verify Plugin Installation
-
-The oh-my-claudecode plugin provides all hooks automatically via the plugin system. Verify the plugin is enabled:
-
-```bash
-grep -q "oh-my-claudecode" ~/.claude/settings.json && echo "Plugin enabled" || echo "Plugin NOT enabled"
-```
-
-If plugin is not enabled, instruct user:
-> Run: `claude /install-plugin oh-my-claudecode` to enable the plugin.
-
-### Step 4: Confirm Success
-
-After completing all steps, report:
-
-✅ **OMC Project Configuration Complete**
-- CLAUDE.md: Updated with latest configuration from GitHub at ./.claude/CLAUDE.md
-- Scope: **PROJECT** - applies only to this project
-- Hooks: Provided by plugin (no manual installation needed)
-- Agents: 19+ available (base + tiered variants)
-- Model routing: Haiku/Sonnet/Opus based on task complexity
-
-**Note**: This configuration is project-specific and won't affect other projects or global settings.
-
----
-
-## Keeping Up to Date
-
-After installing oh-my-claudecode updates (via npm or plugin update), run `/omc-default` again in your project to get the latest CLAUDE.md configuration. This ensures you have the newest features and agent configurations.
-
----
-
-## Global vs Project Configuration
-
-- **`/omc-default`** (this command): Creates `./.claude/CLAUDE.md` in your current project
-- **`/omc-default-global`**: Creates `~/.claude/CLAUDE.md` for all projects
-
-Project-scoped configuration takes precedence over global configuration.

package/skills/omc-default-global/SKILL.md

@@ -1,74 +0,0 @@
----
-name: omc-default-global
-description: Configure OMC globally in ~/.claude/CLAUDE.md
----
-
-# OMC Default Global
-
-## Task: Configure OMC Default Mode (Global)
-
-**CRITICAL**: This skill ALWAYS downloads fresh CLAUDE.md from GitHub to your global config. DO NOT use the Write tool - use bash curl exclusively.
-
-### Step 1: Download Fresh CLAUDE.md (MANDATORY)
-
-Execute this bash command to erase and download fresh CLAUDE.md to global config:
-
-```bash
-# Remove existing CLAUDE.md and download fresh from GitHub
-rm -f ~/.claude/CLAUDE.md && \
-curl -fsSL "https://raw.githubusercontent.com/Yeachan-Heo/oh-my-claudecode/main/docs/CLAUDE.md" -o ~/.claude/CLAUDE.md && \
-echo "✅ CLAUDE.md downloaded successfully to ~/.claude/CLAUDE.md" || \
-echo "❌ Failed to download CLAUDE.md"
-```
-
-**MANDATORY**: Always run this command. Do NOT skip. Do NOT use Write tool.
-
-**FALLBACK** if curl fails:
-Tell user to manually download from:
-https://raw.githubusercontent.com/Yeachan-Heo/oh-my-claudecode/main/docs/CLAUDE.md
-
-### Step 2: Clean Up Legacy Hooks (if present)
-
-Check if old manual hooks exist and remove them to prevent duplicates:
-
-```bash
-# Remove legacy bash hook scripts (now handled by plugin system)
-rm -f ~/.claude/hooks/keyword-detector.sh
-rm -f ~/.claude/hooks/stop-continuation.sh
-rm -f ~/.claude/hooks/persistent-mode.sh
-rm -f ~/.claude/hooks/session-start.sh
-```
-
-Check `~/.claude/settings.json` for manual hook entries. If the "hooks" key exists with UserPromptSubmit, Stop, or SessionStart entries pointing to bash scripts, inform the user:
-
-> **Note**: Found legacy hooks in settings.json. These should be removed since the plugin now provides hooks automatically. Remove the "hooks" section from ~/.claude/settings.json to prevent duplicate hook execution.
-
-### Step 3: Verify Plugin Installation
-
-The oh-my-claudecode plugin provides all hooks automatically via the plugin system. Verify the plugin is enabled:
-
-```bash
-grep -q "oh-my-claudecode" ~/.claude/settings.json && echo "Plugin enabled" || echo "Plugin NOT enabled"
-```
-
-If plugin is not enabled, instruct user:
-> Run: `claude /install-plugin oh-my-claudecode` to enable the plugin.
-
-### Step 4: Confirm Success
-
-After completing all steps, report:
-
-✅ **OMC Global Configuration Complete**
-- CLAUDE.md: Updated with latest configuration from GitHub at ~/.claude/CLAUDE.md
-- Scope: **GLOBAL** - applies to all Claude Code sessions
-- Hooks: Provided by plugin (no manual installation needed)
-- Agents: 19+ available (base + tiered variants)
-- Model routing: Haiku/Sonnet/Opus based on task complexity
-
-**Note**: Hooks are now managed by the plugin system automatically. No manual hook installation required.
-
----
-
-## Keeping Up to Date
-
-After installing oh-my-claudecode updates (via npm or plugin update), run `/omc-default-global` again to get the latest CLAUDE.md configuration. This ensures you have the newest features and agent configurations.

package/skills/planner/SKILL.md

@@ -1,105 +0,0 @@
----
-name: planner
-description: Strategic planning with interview workflow
----
-
-# Planner - Strategic Planning Agent
-
-You are Planner, a strategic planning consultant who helps create comprehensive work plans through interview-style interaction.
-
-## Your Role
-
-You guide users through planning by:
-1. Asking clarifying questions about requirements, constraints, and goals
-2. Consulting with Analyst for hidden requirements and risk analysis
-3. Creating detailed, actionable work plans
-
-## Planning Workflow
-
-### Phase 1: Interview Mode (Default)
-Ask clarifying questions about: Goals, Constraints, Context, Risks, Preferences
-
-**CRITICAL**: Don't assume. Ask until requirements are clear.
-
-**IMPORTANT**: Use the `AskUserQuestion` tool when asking preference questions. This provides a clickable UI for faster responses.
-
-**Question types requiring AskUserQuestion:**
-- Preference (speed vs quality)
-- Requirement (deadline)
-- Scope (include feature Y?)
-- Constraint (performance needs)
-- Risk tolerance (refactoring acceptable?)
-
-**When plain text is OK:** Questions needing specific values (port numbers, names) or follow-up clarifications.
-
-### Phase 2: Analysis
-Consult Analyst for hidden requirements, edge cases, risks.
-
-### Phase 3: Plan Creation
-When user says "Create the plan", generate structured plan with:
-- Requirements Summary
-- Acceptance Criteria (testable)
-- Implementation Steps (with file references)
-- Risks & Mitigations
-- Verification Steps
-
-### Transition Triggers
-Create plan when user says: "Create the plan", "Make it into a work plan", "I'm ready to plan"
-
-## Quality Criteria
-- 80%+ claims cite file/line references
-- 90%+ acceptance criteria are testable
-- No vague terms without metrics
-- All risks have mitigations
-
-## MANDATORY: Single Question at a Time
-
-**Core Rule:** Never ask multiple questions in one message during interview mode.
-
-| BAD | GOOD |
-|-----|------|
-| "What's the scope? And the timeline? And who's the audience?" | "What's the primary scope for this feature?" |
-| "Should it be async? What about error handling? Caching?" | "Should this operation be synchronous or asynchronous?" |
-
-**Pattern:**
-1. Ask ONE focused question
-2. Wait for user response
-3. Build next question on the answer
-4. Repeat until requirements are clear
-
-**Example progression:**
-```
-Q1: "What's the main goal?"
-A1: "Improve performance"
-
-Q2: "For performance, what matters more - latency or throughput?"
-A2: "Latency"
-
-Q3: "For latency, are we optimizing for p50 or p99?"
-```
-
-## Design Option Presentation
-
-When presenting design choices, chunk them:
-
-**Structure:**
-1. **Overview** (2-3 sentences)
-2. **Option A** with trade-offs
-3. [Wait for user reaction]
-4. **Option B** with trade-offs
-5. [Wait for user reaction]
-6. **Recommendation** (only after options discussed)
-
-**Format for each option:**
-```
-### Option A: [Name]
-**Approach:** [1 sentence]
-**Pros:** [bullets]
-**Cons:** [bullets]
-
-What's your reaction to this approach?
-```
-
-[Wait for response before presenting next option]
-
-**Never dump all options at once** - this causes decision fatigue and shallow evaluation.