omc-ralplan

Creates consensus-driven implementation plans for complex software tasks.

1|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/huyhung9630/codex_plugin --skill omc-ralplan-huyhung9630
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omc-ralplan
Source: https://github.com/huyhung9630/codex_plugin/tree/main/plugins/oh-my-codex-workflows/skills/omc-ralplan
Command: npx skills add https://github.com/huyhung9630/codex_plugin --skill omc-ralplan-huyhung9630

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill addresses the need for a comprehensive planning and consensus-building process before executing tasks, ensuring that tasks are well-defined and understood by all stakeholders.

Core Features & Use Cases

  • Consensus Planning: Produces an implementation-ready plan that is reviewed and approved by multiple viewpoints.
  • Task Scoping: Summarizes the goal, constraints, acceptance criteria, and decisions before planning.
  • Plan Verification: Ensures that the plan is comprehensive, with clear steps, dependencies, and verification gates.
  • Deliberate Mode: Incorporates additional steps for high-risk or complex tasks, including pre-mortem analysis and expanded test plans.
  • Plan Handoff: Outputs the final plan and determines the next steps, such as handoff to omc-team, omc-ralph, or omc-autopilot.

Quick Start

Use omc-ralplan to create a consensus implementation plan for the new feature.

Frequently Asked Questions about omc-ralplan

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

FAQPage Schema
How do I facilitate consensus planning for software development tasks?

Consensus planning involves system fit evaluation, role-based reviews, and quality checks to produce an implementation plan approved by multiple stakeholders before execution.

What is plan verification and how does it help high-risk software development workflows?

Plan verification ensures an implementation plan is comprehensive, with clear steps, dependencies, and verification gates, while deliberate mode adds pre-mortem analysis for high-risk tasks.

How do I get stakeholder agreement on an implementation plan before execution?

You can achieve stakeholder engagement by summarizing task goals, constraints, and acceptance criteria, then routing the plan through role-based reviews for consensus before proceeding.

Can I use consensus-driven planning for complex software features?

Yes, consensus-driven planning is suitable for complex or high-risk software development workflows, using deliberate mode to incorporate expanded test plans and pre-mortem analysis.

What are the next steps after finalizing a consensus implementation plan?

After plan verification, the final plan is handed off to determine next steps, such as routing to omc-team, omc-ralph, or omc-autopilot for execution.

Does consensus planning work without specific external dependencies?

Yes, consensus planning operates independently without external dependencies, using internal scripts to evaluate system fit and perform role-based quality checks.