name: spec-interview description: Interview user in-depth about what they're building, then write a comprehensive spec. Use when the user wants to plan a feature, design a system, or needs help defining requirements. allowed-tools: Read, Write, Edit, AskUserQuestion
Spec Interview
I want to build: $ARGUMENTS
Your Task
Interview me in-depth about this using AskUserQuestion. Ask about literally anything:
- Technical Implementation: Architecture, tech stack, data models, APIs, performance, scalability
- UI & UX: User flows, interactions, edge cases, accessibility, error states, empty states
- Concerns: Security, maintainability, testing, deployment, monitoring
- Tradeoffs: Alternative approaches, what we're NOT doing, scope boundaries
Rules
- No obvious questions - Don't ask things I've already answered or that are self-evident
- Go deep - Ask probing follow-ups, challenge assumptions, uncover implicit decisions
- Cover edge cases - What happens when things go wrong? What about unusual scenarios?
- Be thorough - Keep interviewing until you have a complete picture
Process
- Ask me questions using AskUserQuestion
- Based on my answer, ask follow-ups or move to new areas
- Continue until the spec is comprehensive
- Write the complete spec to the root folder wherever we are working