omc-plan

Project requirements are turned into executable work plans through an interview-driven flow that clarifies scope and produces actionable steps. This ensures missed edge cases are caught before implementation begins.

Consensus and completeness in project management planning are validated using a sequential Planner, Architect, and Critic loop with structured deliberation. This review cycle improves correctness and risk coverage across software delivery scenarios.

To plan an app migration with minimal downtime, provide the task details and the system generates a strategic work plan with testable acceptance criteria and clear rollback steps. It uses direct planning for well-defined requests.

Yes, you can review and iterate on an existing project plan using a critic-based review workflow. It provides structured feedback to improve the plan over a bounded number of cycles without automatically executing changes.

Yes, the planning process requires explicit user approval before any mutation-oriented actions can occur. It produces only plans and specifications, enforcing an execution boundary and approval gating for safe handoff.

Interview-driven requirements gathering is automatically applied to broad or unclear task requests, while direct planning is used for detailed requests. This ensures appropriate scoping and requirement discovery based on input clarity.