omc-plan

<Purpose> Plan creates comprehensive, actionable work plans through intelligent interaction. It auto-detects whether to interview the user (broad requests) or plan directly (detailed requests), and supports consensus mode (iterative Planner/Architect/Critic loop with RALPLAN-DR structured deliberation) and review mode (Critic evaluation of existing plans). </Purpose> <Use_When> - User wants to plan before implementing -- "plan this", "plan the", "let's plan" - User wants structured requirements gathering for a vague idea - User wants an existing plan reviewed -- "review this plan", `--review` - User wants multi-perspective consensus on a plan -- `--consensus`, "ralplan" - Task is broad or vague and needs scoping before any code is written </Use_When> <Do_Not_Use_When> - User wants autonomous end-to-end execution -- use `autopilot` instead - User wants to start coding immediately with a clear task -- use `ralph` or delegate to executor - User asks a simple question that can be answered directly -- just answer it - Task is a single focused fix with obvious scope -- use an execution skill instead of running it from this planning module </Do_Not_Use_When> <Why_This_Exists> Jumping into code without understanding requirements leads to rework, scope creep, and missed edge cases. Plan provides structured requirements gathering, expert analysis, and quality-gated plans so that execution starts from a solid foundation. The consensus mode adds multi-perspective validation for ...