flow-next-interview

Spec refinement through interviewing works by detecting Flow IDs, file paths, or epic contexts and then guiding you through targeted questions. It systematically surfaces requirements, constraints, and acceptance criteria to produce a ready-to-plan specification payload.

To start an interview to refine a spec, request the flow using a Flow ID or file path, such as initiating the command with your specific identifier. The system then uses structured detection to begin the questioning approach and capture your epic or task details.

Yes, you can use this structured interview approach for task planning. It supports epic, task, and spec contexts alongside Flow IDs and file paths, ensuring that your task planning workflows remain aligned with your overarching project goals.

The best way to prepare a ready-to-plan spec is to conduct a thorough requirements interview that captures complete implementation details. This produces a refined spec payload that can be directly fed into your planning and execution workflows.

No, this requirements interview does not require any specific dependencies. It operates independently using a structured detection and questioning approach via the AskUserQuestion tool to surface requirements and guide the refinement process.