Ralplan is a shorthand alias for /oh-my-claudecode:omc-plan --consensus. It triggers iterative planning with Planner, Architect, and Critic agents until consensus is reached, with RALPLAN-DR structured deliberation (short mode by default, deliberate mode for high-risk work).
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionralplanExecute the skills CLI command in your project's root directory to begin installation:
Fetches ralplan from yeachan-heo/oh-my-claudecode and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate ralplan. Access via /ralplan in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
21
total installs
21
this week
24.9K
GitHub stars
0
upvotes
Run in your terminal
21
installs
21
this week
24.9K
stars
Ralplan is a shorthand alias for /oh-my-claudecode:omc-plan --consensus. It triggers iterative planning with Planner, Architect, and Critic agents until consensus is reached, with RALPLAN-DR structured deliberation (short mode by default, deliberate mode for high-risk work).
/oh-my-claudecode:ralplan "task description"
--interactive: Enables user prompts at key decision points (draft review in step 2 and final approval in step 6). Without this flag the workflow runs fully automated — Planner → Architect → Critic loop — and outputs the final plan without asking for confirmation.--deliberate: Forces deliberate mode for high-risk work. Adds pre-mortem (3 scenarios) and expanded test planning (unit/integration/e2e/observability). Without this flag, deliberate mode can still auto-enable when the request explicitly signals high risk (auth/security, migrations, destructive changes, production incidents, compliance/PII, public API breakage).--architect codex: Use Codex for the Architect pass when Codex CLI is available. Otherwise, briefly note the fallback and keep the default Claude Architect review.--critic codex: Use Codex for the Critic pass when Codex CLI is available. Otherwise, briefly note the fallback and keep the default Claude Critic review./oh-my-claudecode:ralplan --interactive "task description"
This skill invokes the Plan skill in consensus mode:
/oh-my-claudecode:omc-plan --consensus <arguments>
The consensus workflow:
--interactive is set, use AskUserQuestion to present the draft plan plus the Principles / Drivers / Options summary before review (Proceed to review / Request changes / Skip review). Otherwise, automatically proceed to review.APPROVE Critic verdict (ITERATE or REJECT) MUST run the same full closed loop:
a. Collect Architect + Critic feedback
b. Revise the plan with Planner
c. Return to Architect review
d. Return to Critic evaluation
e. Repeat this loop until Critic returns APPROVE or 5 iterations are reached
f. If 5 iterations are reached without APPROVE, present the best version to the user--interactive is set, use AskUserQuestion to present the plan with approval options (Approve and implement via team (Recommended) / Approve and execute via ralph / Clear context and implement / Request changes / Reject). Final plan must include ADR (Decision, Drivers, Alternatives considered, Why chosen, Consequences, Follow-ups). Otherwise, output the final plan and stop.Skill("oh-my-claudecode:team") for parallel team execution (recommended) or Skill("oh-my-claudecode:ralph") for sequential execution -- never implement directlyImportant: Steps 3 and 4 MUST run sequentially. Do NOT issue both agent Task calls in the same parallel batch. Always await the Architect result before issuing the Critic Task.
Follow the Plan skill's full documentation for consensus mode details.
Execution modes (ralph, autopilot, team, ultrawork, ultrapilot) spin up heavy multi-agent orchestration. When launched on a vague request like "ralph improve the app", agents have no clear target — they waste cycles on scope discovery that should happen during planning, often delivering partial or misaligned work that requires rework.
The ralplan-first gate intercepts underspecified execution requests and redirects them through the ralplan consensus planning workflow. This ensures:
Passes the gate (specific enough for direct execution):
ralph fix the null check in src/hooks/bridge.ts:326autopilot implement issue #42team add validation to function processKeywordDetectorralph do:\n1. Add input validation\n2. Write tests\n3. Update READMEultrawork add the user model in src/models/user.tsGated — redirected to ralplan (needs scoping first):
ralph fix thisautopilot build the appteam improve performanceralph add authenticationultrawork make it betterBypass the gate (when you know what you want):
force: ralph refactor the auth module! autopilot optimize everythingThe gate auto-passes when it detects any concrete signal. You do not need all of them — one is enough:
| Signal Type | Example prompt | Why it passes |
|---|---|---|
| File path | ralph fix src/hooks/bridge.ts |
References a specific file |
| Issue/PR number | ralph implement #42 |
Has a concrete work item |
| camelCase symbol | ralph fix processKeywordDetector |
Names a specific function |
| PascalCase symbol | ralph update UserModel |
Names a specific class |
| snake_case symbol | team fix user_model |
Names a specific identifier |
| Test runner | ralph npm test && fix failures |
Has an explicit test target |
| Numbered steps | ralph do:\n1. Add X\n2. Test Y |
Structured deliverables |
| Acceptance criteria | ralph add login - acceptance criteria: ... |
Explicit success definition |
| Error reference | ralph fix TypeError in auth |
Specific error to address |
| Code block | ralph add: \``ts ... ```` |
Concrete code provided |
| Escape prefix | force: ralph do it or ! ralph do it |
Explicit user override |
ralph add user authenticationralph) + underspecified prompt (no files, functions, or test spec)| Issue | Solution |
|---|---|
| Gate fires on a well-specified prompt | Add a file reference, function name, or issue number to anchor the request |
| Want to bypass the gate | Prefix with force: or ! (e.g., force: ralph fix it) |
| Gate does not fire on a vague prompt | The gate only catches prompts with <=15 effective words and no concrete anchors; add more detail or use /ralplan explicitly |
| Redirected to ralplan but want to skip planning | In the ralplan workflow, say "just do it" or "skip planning" to transition directly to execution |
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Solid pick for teams standardizing on skills: ralplan is focused, and the summary matches what you get after install.
Keeps context tight: ralplan is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for ralplan matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: ralplan is focused, and the summary matches what you get after install.
We added ralplan from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
We added ralplan from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in ralplan — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: ralplan is the kind of skill you can hand to a new teammate without a long onboarding doc.
ralplan fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
ralplan fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 45