omc-plan

Consensus planning workflows apply a sequential Planner, Architect, and Critic validation loop to resolve design tradeoffs. This process iterates up to five re-review cycles, generating an Architecture Decision Record (ADR) and changelog updates to ensure high-stakes feature designs are fully validated.

The best way to gather requirements for multi-service features is using a structured scoping process that applies interview modes for broad requests. It produces file-referenced implementation steps and testable acceptance criteria, ensuring all service design tradeoffs are documented before development starts.

Structured project planning supports architecture decision records (ADR) output and enforces explicit ralplan state lifecycle management. It uses strict state_write and state_clear rules to manage persistent handoff states safely, ensuring non-autonomous execution delegation to approved execution skills.

You can use consensus planning workflows, specifically RALPLAN-DR flows, for high-stakes software design tradeoffs. These workflows orchestrate sequential validation across Planner, Architect, and Critic roles, generating ADRs and saved plan artifacts in the .omc/plans/ directory before any code changes.

You should avoid jumping into implementation without a plan when a project lacks clear requirements, testable acceptance criteria, or validated architecture. Without structured work plans, you risk wasted effort from building features without a firm, verifiable foundation or resolved design tradeoffs.