ralplan

Orchestrate a consensus planning workflow among Planner, Architect, and Critic roles.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/KYRIE66nb/codex-omx-public-config --skill ralplan-kyrie66nb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralplan
Source: https://github.com/KYRIE66nb/codex-omx-public-config/tree/main/home/.agents/skills/ralplan
Command: npx skills add https://github.com/KYRIE66nb/codex-omx-public-config --skill ralplan-kyrie66nb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, multi-agent planning framework that transforms vague requests into validated, executable plans by coordinating Planner, Architect, and Critic roles to produce a high-quality plan before execution.

Core Features & Use Cases

  • Consensus-driven planning: Orchestrates iterative planning loops to converge on an accepted plan.
  • Role-based review: Ensures architectural soundness, tradeoffs, and risk mitigation via Planner, Architect, and Critic.
  • Auditable ADR output: Produces decision drivers, alternatives, and follow-ups as a formal record.
  • Use Case: For underspecified tasks like "improve the app," it generates a bounded, testable plan and a clear execution path.

Quick Start

Use ralplan to start a consensus planning workflow for a vague task.

Frequently Asked Questions about ralplan

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

FAQPage Schema
How does multi-agent consensus planning work for high-risk software tasks?

Multi-agent consensus planning works by orchestrating Planner, Architect, and Critic roles to review, revise, and approve a vetted plan iteratively. This closed-loop workflow enforces architectural soundness and risk mitigation before execution, producing an auditable record.

What is the best way to create an executable plan from a vague software request?

The best way to create an executable plan from a vague request is running a consensus planning workflow. It transforms underspecified tasks into bounded, testable plans by coordinating AI agents through iterative reviews, outputting a clear execution path with decision drivers.

How do I generate an ADR-style plan with AI agents for architecture review?

To generate an ADR-style plan with AI agents, initiate a multi-agent workflow that enforces a closed-loop review. Once approved through iterative revisions, it outputs decision drivers, alternatives considered, and follow-ups as a formal architectural decision record.

Can I use an iterative planning workflow for underspecified tasks like improving an app?

Yes, you can use an iterative planning workflow for underspecified tasks like improving an app. It applies a bounded, multi-iteration review process up to five cycles, converging vague requirements into a testable plan with optional interactive approval.

When should I not use a consensus planning workflow for AI agents?

You should not use a consensus planning workflow for low-risk or fully specified tasks. The multi-iteration review loop adding Planner, Architect, and Critic roles introduces overhead unnecessary for simple requests that already have clear execution paths.