ralplan

Coordinate consensus planning for vague execution requests through Planner, Architect, and Critic loops.

5|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/RobinNorberg/oh-my-copilot --skill ralplan-robinnorberg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralplan
Source: https://github.com/RobinNorberg/oh-my-copilot/tree/main/skills/ralplan
Command: npx skills add https://github.com/RobinNorberg/oh-my-copilot --skill ralplan-robinnorberg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ralplan provides a structured gate that redirects vague execution requests through a formal consensus planning workflow (Planner → Architect → Critic) to produce an explicit, reviewable plan before any work is executed.

Core Features & Use Cases

  • Deliberate gating for high-risk or unclear tasks ensures a thorough plan and risk mitigation.
  • Iterative review loop with Planner, Architect, and Critic feedback reduces rework and misalignment.
  • Pre-execution validation enforces explicit scope, acceptance criteria, and testing plans prior to execution.

Quick Start

Use ralplan to gate a new task: /oh-my-copilot:ralplan "describe the task" and let the planning workflow produce an approved plan before execution.

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 vague software requests?

Multi-agent consensus planning routes vague requests through Planner, Architect, and Critic loops to generate explicit, reviewable execution plans. This iterative review cycle enforces structured gating and pre-execution validation to reduce rework before any development begins.

How do I enforce a quality gate before executing high-risk or unclear tasks?

To enforce a quality gate for high-risk tasks, apply deliberate gating modes within a consensus planning workflow. This structured approach mandates pre-mortem analysis, explicit scope definition, and test planning to mitigate risks prior to execution.

What is the best way to reduce misalignment when planning vague execution requests?

The best way to reduce misalignment for vague execution requests is using an iterative review loop with Planner, Architect, and Critic roles. This multi-agent cycle refines the plan until consensus is reached, ensuring explicit scope and acceptance criteria.

Do I need predefined acceptance criteria to use consensus planning workflows?

No, predefined acceptance criteria are not required beforehand. The consensus planning workflow generates explicit scope, acceptance criteria, and testing plans during the iterative Architect and Critic review loops before execution begins.

When should I use a deliberate planning gate versus a non-deliberate mode?

Use a deliberate planning gate for high-risk or unclear tasks requiring thorough risk mitigation and pre-mortem analysis. Non-deliberate modes apply to straightforward tasks where minimal validation is needed before proceeding to execution.