ralphex-adopt
Convert plans from various source formats (OpenSpec, spec-kit, GitHub/GitLab issues with…
Run ralphex autonomous plan execution with progress monitoring
$ npx -y skills add umputun/ralphex --skill ralphex --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/ralphexContext preview
The summary Claude sees to decide when to auto-load this skill.
Run ralphex autonomous plan execution with progress monitoring
description: Run ralphex autonomous plan execution with progress monitoring argument-hint: 'optional plan file path' allowed-tools: [Bash, Read, AskUserQuestion, TaskOutput, Glob]
**SCOPE**: This command ONLY launches ralphex, monitors progress, and reports status. Do NOT take any other actions.
Check if ralphex CLI is installed:
which ralphex
**If not found**, guide installation based on platform:
Use AskUserQuestion to confirm installation method, then guide through it. **Do not proceed until `which ralphex` succeeds.**
Check `$ARGUMENTS` for optional plan file path:
Use AskUserQuestion:
description: "Task execution + Claude review + Codex loop + final Claude review"
description: "Skip tasks, run full review pipeline (Claude + Codex + Claude)"
description: "Skip tasks and first Claude review, run only Codex loop"
**If Full mode selected:**
**If Review or Codex-only mode selected:**
Use AskUserQuestion:
description: "Default - suitable for most plans"
description: "Shorter plans or quick iterations"
description: "Large plans with many tasks"
Build and run the command:
ralphex \ [--review] # if user selected "Review" mode [--codex-only] # if user selected "Codex-only" mode [--max-iterations N] # from user selection (25, 50, or 100) [plan-file] # from argument OR plan selection (omit if "None" selected)
Run using Bash tool with `run_in_background: true`. **Save the task_id from the response** - needed for status checks later.
**Determine progress filename** based on mode and plan selection:
Where `{plan-stem}` is the plan filename without extension (e.g., `fix-bugs` from `fix-bugs.md`).
1. Wait 10-15 seconds for initialization 2. Read last 20 lines of progress file: `tail -20 [progress-filename]` 3. Confirm ralphex started by checking for "Plan:", "Branch:", "Started:" lines 4. Report launch confirmation:
ralphex started. Task ID: [task_id] Plan: [plan file from progress file] Branch: [branch from progress file] Mode: [mode from progress file] Progress file: [progress-filename] Manual monitoring: tail -f [progress-filename] # live stream tail -50 [progress-filename] # recent activity ralphex runs autonomously (can take hours). Process continues if you close this conversation. Ask "check ralphex" to get status update.
**STOP HERE after reporting launch status. Do not continue monitoring automatically.**
If user explicitly asks "check ralphex", "ralphex status", or "how is ralphex doing":
1. Use TaskOutput tool with `block: false` to check process status (use task_id from Step 5) 2. Read last 40 lines of progress file (use filename from Step 5)
**If process still running:**
**If process exited (TaskOutput shows completion):**
**After reporting status, STOP. Do not offer to do anything else.**
ralphex automatically strips Claude Co
Convert plans from various source formats (OpenSpec, spec-kit, GitHub/GitLab issues with…
Create structured implementation plan in docs/plans/
Smart-merge updated ralphex defaults into customized prompts/agents