deep-interview

To turn vague software requirements into clear specifications, you can use a Socratic questioning loop that iteratively clarifies intent, scope, and non-goals. This process generates interview transcripts and execution-ready spec artifacts for downstream planning.

The best way to clarify ambiguous project ideas is through an interactive interview process that scores ambiguity across configurable depth profiles. It automatically handles early-exit conditions to ensure all underspecified requirements are resolved into actionable specifications.

Yes, you can use Socratic questioning to create execution-ready specs for existing codebases. The interview process applies to both greenfield and brownfield contexts, automatically exploring your codebase when needed to clarify underspecified requirements.

You generate project specifications by invoking the skill with your initial idea. It runs interactive question rounds, scores the ambiguity of your responses, and outputs ready-to-use specification artifacts into the .forge directory.

You can configure requirements clarification interviews using three depth profiles: quick, standard, and deep. These profiles control the thoroughness of the Socratic questioning loop and include automatic early-exit handling when ambiguity is sufficiently resolved.

Interview transcripts and specification artifacts are stored in the .forge directory. These generated files capture the full interactive questioning history and provide ready-to-use outputs for downstream project execution and planning.