omh-ralplan

OMH Ralplan — Consensus Planning

When to Use

• Before implementing any feature that touches multiple files or components
• When architectural decisions need validation from multiple perspectives
• When you need a plan that's been stress-tested against adversarial critique
• When the user says: "plan this", "consensus plan", "ralplan", "let's think this through"

When NOT to Use

• Trivial single-file changes (just do them)
• Tasks where the approach is obvious and low-risk
• When the user explicitly wants to skip planning

Prerequisites

• A clear goal or specification (if ambiguous, use omh-deep-interview first)
• The delegate_task tool must be available

Procedure

Phase 0: Context Gathering

Before planning, gather project context:

1. Read relevant files to understand the codebase structure
2. Identify existing patterns, conventions, and constraints
3. Summarize context into a brief (~500 words) that all agents will receive

Phase 1: Planning Loop (max 3 rounds)

Round 1 — All Sequential (Planner → Architect → Critic):

Step 1 — Planner (single delegate_task)

delegate_task(
    goal="[omh-role:planner] Create an implementation plan for: {goal}\n\n{detailed_requirements}",
    context="# Project Context\n\n{project_context}"
)

The goal should include the full specification — don't assume the subagent knows anything.

Step 2 — Architect Review (single delegate_task)

delegate_task(
    goal="[omh-role:architect] Review this implementation plan for architectural soundness:\n\nPLAN:\n{planner_output}",
    context="# Project Context\n\n{project_context}"
)

Step 3 — Critic Challenge (single delegate_task)

delegate_task(
    goal="[omh-role:critic] Critically challenge this plan and architect review:\n\nPLAN SUMMARY:\n{plan_summary}\n\nARCHITECT REVIEW:\n{architect_verdict_and_concerns}",
    context="# Project Context\n\n{project_context}"
)

Step 4 — Consensus Check Check all three verdicts:

• If ALL three are APPROVE → consensus reached, proceed to output
• If any is REQUEST_CHANGES → collect all feedback, proceed to Round 2
• If any is REJECT → output concerns and ask user whether to continue