prometheus-strict

Interview-driven project planning validates requirements by conducting structured interviews before execution. This approach clarifies project needs, challenges underlying assumptions, and synthesizes a validated plan using defined roles like Metis, Momus, and Oracle.

To use an interview-driven workflow for project management handoffs, you participate in a structured interview process. Once requirements are clarified and assumptions challenged, the validated plan is handed off to OMX execution workflows like $ultragoal or $team.

Yes, interview-driven planning supports both individual and team project execution. After the interview process validates the plan, it provides OMX handoffs to execution workflows such as $ultragoal for individual goals and $team for team management.

The best way to challenge project assumptions before execution is through a rigorous interview-driven planning process. By applying specific roles like Momus to challenge assumptions and Metis to clarify requirements, you ensure the project plan is fully validated.

You should not use an interview-driven planning workflow when immediate execution is required without structured validation. This rigorous process demands adherence to clean-room boundaries and structured interview responses, making it unsuitable for rapid, unvalidated prototyping.