spec-interview

# Spec Interview

## Overview
This skill transforms vague or incomplete requirements into a comprehensive, actionable specification through structured interviewing. It reads existing requirement documents in the project, identifies gaps and ambiguities, then conducts a rigorous multi-round interview using the AskUserQuestion tool. The interview continues until all critical dimensions are clarified. Upon completion, it produces a structured markdown specification file.

## Instructions

### Phase 1: Discovery & Analysis
1. Scan the project for requirement-related files. Search patterns include:
   - `**/SPEC.md`, `**/spec.md`, `**/SPEC*.md`
   - `**/PRD.md`, `**/prd.md`
   - `**/REQUIREMENTS.md`, `**/requirements.md`
   - `**/README.md` (if it contains requirement-like content)
   - `**/docs/requirements/**`, `**/docs/specs/**`
   - Any file passed as an argument to the skill invocation
2. Read and deeply analyze all discovered files.
3. Before starting the interview, internally identify:
   - What is explicitly stated vs. what is assumed
   - Logical contradictions or inconsistencies
   - Missing technical details that would block implementation
   - Unstated constraints (performance, scale, compatibility)
   - Ambiguous terms that could be interpreted multiple ways

### Phase 2: Interview Execution
4. Conduct the interview using `AskUserQuestion`. Follow these principles:

   **Question Quality Rules:**
   - NEVER ask questions whose answers are already in the document
   - NEVER ask generic questions like "What's the target audience?" unless genuinely unclear
   - Each question must be derived from a specific gap, contradiction, or ambiguity found in the requirement document
   - Questions should reveal hidden assumptions and force the user to think about scenarios they haven't considered
   - Prefer questions that expose trade-offs ("If X and Y conflict, which takes priority?") over simple information gathering
   - Ask "what happens when..." questions for edge c