ralplan

Convert underspecified execution requests into consensus-based plans via Planner, Architect, and Critic.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ralplan prevents vague ralph/autopilot/team requests from wasting orchestration cycles by forcing a scoped, consensus-driven plan before execution.

Core Features & Use Cases

  • Consensus planning loop: Runs Planner → Architect → Critic until quality consensus is reached, with iterative re-review when needed.
  • Risk-aware deliberation: Supports a deliberate mode that adds pre-mortem scenarios and expanded test planning for high-risk work.
  • Optional interactive approvals: Can request user feedback at draft and final stages to align on principles, options, and acceptance criteria.
  • Execution routing after approval: Redirects to approved execution paths (via team for parallelism or ralph for sequential execution) only after Critic approval.

Quick Start

Use /oh-my-claudecode:ralplan --interactive "Implement the null check fix in src/hooks/bridge.ts:326 and add tests for the regression" to get a gated, consensus plan before any code is written.

Frequently Asked Questions about ralplan

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

FAQPage Schema
How do I convert vague execution requests into a scoped plan with clear deliverables?

Consensus planning converts underspecified requests by running a Planner, Architect, and Critic loop to define deliverables, risks, and testable acceptance criteria before execution begins.

What is the best way to add risk triage and pre-mortem analysis to workflow orchestration?

Risk triage in deliberate mode adds pre-mortem scenarios and expanded test planning to high-risk workflow automation, ensuring potential failures are evaluated before routing to execution.

How does interactive approval work during code review and test planning?

Interactive approvals request user feedback at draft and final stages to align on principles, options, and acceptance criteria, ensuring human consensus before any code review or test planning execution.

Can I use sequential Architect-before-Critic evaluation for incident triage?

Yes, incident triage enforces sequential Architect-before-Critic evaluation to validate the scoped plan, redirecting to execution paths only after the Critic grants approval.

When do I need ADR generation during consensus planning?

ADR generation is needed when consensus planning requires documenting architectural decisions and trade-offs, capturing the rationale approved during the Planner, Architect, and Critic evaluation loop.