Use Case Specification

It asks just enough questions to capture your business problem, who'll use the model, and measurable success criteria that an LLM-as-a-Judge can evaluate. The workflow is deliberately low-friction: it infers from context instead of interrogating you, asks one thing at a time, and skips the whole process if you already have a spec file in your project. Think of it as enforced documentation that actually pays off later when you need to evaluate whether your fine-tuned model solved the problem you set out to solve. It won't ask about model selection, that's handled separately.