spec-interview

# Spec Interview ## When to Use Use this skill when: - Feature requirements are vague or incomplete - You have a general idea but lack specifics - Stakeholders said "you know what I mean" - The spec has obvious gaps - Making assumptions that could be wrong ## What It Does The agent interviews you to **uncover unknown unknowns** in your feature specification, focusing on questions that would change architectural decisions. ## How to Execute ### Step 1: Review Initial Spec Analyze what the user provided: - Explicit requirements (what they said) - Implicit requirements (what they assumed) - Missing details - Ambiguous areas ### Step 2: Categorize Gaps Identify question categories: **Scope & Boundaries**: - What's in scope vs out of scope? - Edge cases to handle? - MVP vs future iterations? **User Experience**: - What happens when...? - Error states and recovery? - Loading and async states? **Technical Decisions**: - Performance requirements? - Data consistency needs? - Integration points? - Security considerations? **Architecture Impact**: - Does this change existing patterns? - New abstractions needed? - Migration strategy for existing data? ### Step 3: Prioritize Questions Sort by impact on implementation: 1. **Architecture-changing**: Would change core approach 2. **High-impact**: Significant implementation difference 3. **Medium-impact**: Affects specific modules 4. **Low-impact**: Nice to clarify but not blocking ### Step 4: Conduct Interview (One Question ...