prometheus

To turn an implementation request into a structured project plan, use an interview-driven workflow that clarifies requirements, scopes the task, and generates mandatory plan artifacts for formal handoff.

The best way to scope project requirements is conducting interview-driven research that uncovers gaps in the initial request, ensuring alignment and decision-making before execution begins.

You need a formal planning process instead of direct coding when tasks require strategic alignment, scoping, and structured decision-making to establish a clear path to execution.

Create a formal work plan without writing code by interpreting user requests strictly as planning tasks, interviewing stakeholders to uncover gaps, and saving plan artifacts for project kickoff.

No specific dependencies or components are required to run this planning workflow, allowing teams to enforce a structured handoff process and generate work plans independently.

Finalized work plans are saved as mandatory plan artifacts within a designated plans directory, facilitating structured project handoff and kickoff for the execution phase.