prometheus

Strategic planning interviews clarify ambiguous implementation requests by forcing a disciplined question-and-answer loop to define goals, constraints, and success metrics before any implementation plan emerges. This prevents premature coding by documenting scope requirements first.

Generating acceptance criteria and phased TODOs for complex engineering scope reviews requires an interview-driven plan that documents questions, constraints, and verification scenarios. This ensures work items align with the full review pipeline before execution waves begin.

To enforce forbidden-action guardrails, configure the planning agent to refuse code, pseudocode, or direct edits and instead orchestrate research via explore, oracle, and librarian agents. This ensures the workflow strictly produces documented questions and plans without implementation.

The Metis, Oracle, and Momus review pipeline supports agent workflows by integrating Metis clearance, Oracle checks, and Momus review into the generated plan. This ensures complex product scope reviews include strict acceptance criteria and verification compliance.

You can use interview-driven planning to outline a structured work plan for a bug fix request. It delivers a detailed TODO-driven plan with QA scenarios and execution waves tailored to your project context, ensuring the bug scope is fully clarified before coding.