plan

To turn vague project requests into actionable roadmaps, the planning process evaluates the input scope and triggers interactive interviewing to clarify constraints before generating a structured plan. This ensures the final output includes implementation steps, acceptance criteria, and verification steps.

Interactive requirements gathering for project scoping is needed when requests are broad or ambiguous, prompting guided questions to clarify scope. Direct plan generation applies when the user provides detailed instructions or triggers a specific mode like --direct for immediate results.

The best way to manage architecture refinement and consensus trade-offs is using a multi-step consensus mode that runs iterative Planner, Architect, and Critic loops. This workflow evaluates options and gates readiness before producing a final approved plan.

The plan review and approval workflow applies a critic-based approach to evaluate existing drafts for risks and missing mitigations. It triggers revisions or grants final approval, ensuring all testable acceptance criteria and verification steps are met before execution.

Yes, you can generate codebase-informed work plans by running internal fact-finding consultations to gather context before planning. The resulting output maps implementation steps with specific file references, identifies potential risks, and outlines targeted mitigations.

Generated project plans are saved automatically to the .omg/plans/ directory structure. This ensures that all roadmaps, including their acceptance criteria and verification steps, remain accessible for later review, iterative updates, or final approval workflows.