ralplan

Generate consensus-based plans before multi-agent execution for underspecified requests.

Updated May 20, 2026
One-click install
npx skills add https://github.com/xdkp/oh-my-claudecode --skill ralplan-xdkp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralplan
Source: https://github.com/xdkp/oh-my-claudecode/tree/main/skills/ralplan
Command: npx skills add https://github.com/xdkp/oh-my-claudecode --skill ralplan-xdkp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ralplan prevents wasted, misaligned work by forcing vague execution requests to be converted into a concrete, testable consensus plan before any heavy multi-agent execution starts.

Core Features & Use Cases

  • Consensus planning loop (Planner → Architect → Critic) that iterates until agreement or a bounded retry limit is reached.
  • Pre-execution gate for underspecified requests so ralph/autopilot/team actions don’t begin without clear scope, acceptance criteria, and verification steps.
  • Deliberate mode for high-risk tasks with built-in pre-mortem and expanded test planning across unit/integration/e2e/observability.

Quick Start

Use Ralplan when your request is unclear and you want a safe, structured plan first: run /oh-my-claudecode:ralplan "task description".

Frequently Asked Questions about ralplan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent vague multi-agent execution requests from running without clear scope?

Multi-agent execution requests need a pre-execution gate that converts vague inputs into a concrete, testable consensus plan before any heavy implementation starts, preventing wasted and misaligned work.

What is consensus-based planning for software architecture review?

Consensus-based planning enforces an ordered Planner, Architect, and Critic workflow that iterates until agreement or a bounded retry limit is reached, producing a final plan with explicit verification steps.

How do I add pre-mortem risk guardrails and test planning for high-risk software tasks?

High-risk software tasks require a deliberate mode that applies pre-mortem analysis and expanded test planning across unit, integration, e2e, and observability layers before execution begins.

Can I use interactive approval workflows to gate multi-agent task execution?

Yes, you can gate multi-agent task execution using optional interactive approvals within the consensus planning loop, ensuring human validation occurs before proceeding to the implementation phase.

When do I need ADR-style decision documentation in my test planning workflow?

ADR-style decision documentation is needed when finalizing a consensus plan, as it explicitly records architectural decisions and verification criteria alongside the pre-execution scope definitions.

What are the limitations of running multi-agent orchestration without pre-execution gating?

Without pre-execution gating, multi-agent orchestration risks wasted effort on underspecified requests lacking concrete files, symbols, issue references, or acceptance criteria, leading to misaligned implementations.