ralplan

Create consensus plans for vague execution requests using a Planner-Architect-Critic loop.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ralplan prevents underspecified or vague execution requests from wasting multi-agent cycles by forcing a consensus planning step before any real work starts.

Core Features & Use Cases

  • Consensus Planning Loop (Planner → Architect → Critic): Produces an initial plan, stress-tests architectural soundness, then validates quality and testability before execution.
  • Structured RALPLAN-DR Deliberation: Includes Principles, Decision Drivers, and Viable Options (with bounded tradeoffs) to make scope and rationale explicit.
  • Optional High-Risk Mode: In deliberate mode, adds a pre-mortem and expanded test planning (unit/integration/e2e/observability) and tightens Critic rejection criteria.
  • Interactive Review Gate: When enabled, asks for user feedback on the draft plan and final approval/approval path.
  • Correct Execution Handoff: On approval, invokes the appropriate execution skill via team (parallel) or ralph (sequential) rather than implementing directly.

Quick Start

Use ralplan to turn a vague build request into a vetted, executable plan by running: /oh-my-claudecode:ralplan "Implement authentication for the app with clear acceptance criteria and tests".

Frequently Asked Questions about ralplan

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

FAQPage Schema
How do I prevent vague software requests from wasting multi-agent execution cycles?

Consensus planning prevents vague software requests from wasting multi-agent execution cycles by establishing architectural soundness, risk awareness, and testable acceptance criteria before implementation begins. A Planner, Architect, and Critic loop validates scope and rationale prior to any code changes.

What is the best way to plan architectural soundness and test criteria before implementation?

The best way to plan architectural soundness and test criteria before implementation is using a structured deliberation process that captures principles, decision drivers, and viable options with bounded tradeoffs to make scope explicit.

How do I add risk mitigation and test planning to multi-agent orchestration workflows?

You can add risk mitigation and test planning to multi-agent orchestration workflows by enabling a deliberate high-risk mode that introduces pre-mortems, expands test coverage across unit and integration layers, and tightens critic rejection criteria.

Can I require user approval and interactive checkpoints during agent workflow planning?

Yes, you can require user approval and interactive checkpoints during agent workflow planning by enabling an interactive review gate that asks for feedback on draft plans before finalizing the execution handoff path.

When do I need consensus planning for iterative software changes versus direct implementation?

You need consensus planning for iterative software changes when requests are underspecified and would otherwise waste cycles on scope discovery, whereas direct implementation suits only fully specified tasks with clear architectural parameters.

Does multi-agent consensus planning hand off to parallel or sequential execution skills automatically?

Multi-agent consensus planning hands off to execution skills automatically upon user approval, invoking team execution for parallel processing or ralph execution for sequential processing rather than implementing changes directly.