omc-plan

Executable work plans are generated from vague ideas through iterative interviews or direct planning, producing testable acceptance criteria, ADRs, and file-referenced implementation steps. The system automatically adapts its mode based on the specificity of your initial request.

Scoping high-risk migrations uses a consensus-driven quality gate loop involving a Planner, Architect, and Critic. This iterative process generates a RALPLAN-DR summary and enforces testable acceptance criteria before approving any architectural design or migration plan.

Architecture Decision Records are generated automatically during the consensus review process. The Planner, Architect, and Critic loop iterates on the design to ensure quality before producing the final ADRs alongside structured, file-referenced implementation steps.

Automatic mode selection chooses between interview, direct, consensus, or review flows based on request specificity. If your project requirements are already detailed, the system bypasses manual interviews and directly generates a structured, actionable work plan.

State lifecycle management writes and clears ralplan states while preserving approved plans in the .omc/plans/ directory. This ensures structured handoffs to execution skills like team or ralph orchestrators for immediate implementation.

Automated planning requires sufficient initial context to select the correct mode, and while it supports organizational projects, complex change management may still need extensive manual interview iterations to capture all stakeholder requirements accurately before generating the final plan.