Plan

Overview

Plan is a strategic planning skill that supports four modes: interview, direct, consensus, and review. It automatically selects a mode based on how specific the request is, explores the codebase first, then asks the user questions.

Usage

/oh-my-claudecode:omc-plan "implement user authentication"
/oh-my-claudecode:omc-plan --consensus "redesign the API layer"
/oh-my-claudecode:omc-plan --direct "add caching to the search endpoint"
/oh-my-claudecode:omc-plan --review

Also activated via magic keywords.

plan this feature
plan the migration
let's plan the refactoring

Mode Selection

Interview Mode

Interactively gathers requirements for broad or vague requests.

• Codebase facts are gathered first via the explore agent
• Only one question is asked at a time
• Each question builds on previous answers
• Generates a plan when the user is ready

Consensus Mode

A consensus mode using RALPLAN-DR structured deliberation.

1. Planner writes the initial plan and RALPLAN-DR summary
2. Architect reviews architectural soundness (runs sequentially)
3. Critic evaluates quality criteria (runs after Architect completes)
4. Iterates up to 5 times on rejection
5. Outputs final plan with ADR on approval

RALPLAN-DR Summary Structure

• Principles (3-5)
• Decision drivers (top 3)
• Actionable options (2 or more), each with pros and cons
• --deliberate mode: pre-mortem analysis (3 scenarios) + extended test plan

Options / Flags

Plan Output Format

Every plan includes:

• Requirements summary
• Acceptance criteria (testable)
• Implementation steps (with file references)
• Risks and mitigations
• Verification steps
• Consensus mode: RALPLAN-DR summary + ADR

Plans are saved to .omc/plans/.

Related Skills

• ralplan - shortcut alias for plan --consensus
• autopilot - autonomous execution after planning
• ralph - continuous loop execution after planning
• deep-interview - deep interview before planning

Reference