ralplan_skill

Overview

This skill is an alias that runs the Plan workflow in consensus mode: /oh-my-claudecode:plan --consensus. It orchestrates Planner, Architect, and Critic agents to produce a vetted plan and hands off execution to the ralph execution skill after user approval. Use it when you need iterative, team-style planning with explicit user reviews and automated quality gates.

How this skill works

Ralplan invokes the Plan skill with the --consensus flag, starting a loop where a Planner drafts a plan, the Architect checks architecture, and the Critic enforces quality criteria. The flow requires presenting the draft and final plan to the user via AskUserQuestion steps, supports up to five Critic-driven iterations, and—on approval—calls Skill("oh-my-claudecode:ralph") to perform execution. The skill never implements execution itself and follows the Plan skill’s consensus semantics.

When to use it

• You need a multi-agent, iterative plan with explicit user review checkpoints.
• Architectural validation and automated critique are required before execution.
• You want a repeatable consensus process with a fixed iteration cap.
• You must ensure human approval before any automated execution step.
• Coordinating team-style reasoning across Planner, Architect, and Critic agents.

Best practices

• Provide a clear, scoped task description to speed consensus and reduce iterations.
• Expect and enforce AskUserQuestion prompts: present the draft, then present the approved plan.
• Use concise review options (Proceed to review / Request changes / Skip review) to guide users.
• Allow up to five iterations for Critic feedback; adjust task scope if iterations reach the cap.
• Never implement execution in this skill; rely on the mandatory call to ralph for running changes.

Example use cases

• Designing a new microservice: generate an initial plan, validate architecture, and collect approval before deployment.
• Coordinating a multi-step refactor where quality checks and user sign-off are required.
• Creating a release plan that needs iterative critique for test coverage, rollback strategy, and performance goals.
• Preparing a complex infrastructure change where an architect must verify topology and a critic enforces standards.