ralplan

Alias the plan workflow to run consensus planning across Planner, Architect, and Critic.

3|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/Tienching/oh-my-codebuddy --skill ralplan-tienching
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ralplan
Source: https://github.com/Tienching/oh-my-codebuddy/tree/main/.codex/skills/ralplan
Command: npx skills add https://github.com/Tienching/oh-my-codebuddy --skill ralplan-tienching

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ralplan provides a concise alias to trigger the full consensus planning workflow, enabling teams to start Planner/Architect/Critic loops without invoking the Plan command manually.

Core Features & Use Cases

  • Alias for consensus planning: Skips manual gating and launches the Planner/Architect/Critic loop automatically.
  • Deterministic planning workflow: Ensures a structured, repeatable planning process for complex tasks.
  • Interoperability with Plan: Invokes $plan --consensus to trigger the consensus workflow when needed.

Quick Start

Invoke ralplan with a task description to start the consensus planning workflow.

Frequently Asked Questions about ralplan

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

FAQPage Schema
What is consensus planning and when do I need multi-agent planning for complex tasks?▼

Consensus planning is an iterative workflow where Planner, Architect, and Critic agents review and refine a plan sequentially. You need it for complex tasks requiring structured, multi-agent governance to ensure repeatable and deterministic planning outcomes.

How do I run a Planner, Architect, and Critic loop without manual gating?▼

You can trigger the full Planner, Architect, and Critic loop automatically by invoking the ralplan alias with a task description. This skips manual gating and launches the sequential consensus planning workflow immediately.

Does consensus planning require access to the Plan skill in consensus mode?▼

Yes, consensus planning requires access to the Plan skill in consensus mode. The alias invokes the consensus workflow internally to ensure the Planner, Architect, Critic, and re-review loop executes properly.

What is the best way to ensure a deterministic and repeatable planning process?▼

The best way to ensure deterministic and repeatable planning is to use a consensus planning alias that enforces sequential governance. This structured approach runs a Planner, Architect, and Critic loop automatically for your complex tasks.

What are the limitations of using an alias for iterative multi-agent planning?▼

The limitation of using an alias for multi-agent planning is its dependency on the Plan skill in consensus mode. Without that underlying access, the sequential Planner, Architect, Critic, and re-review loop cannot execute.