spec-interview

Extract topic, context, and focus areas from prompts into a specification document.

Updated Jan 17, 2026
One-click install
npx skills add https://github.com/JayKim88/claude-ai-engineering --skill spec-interview-jaykim88
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-interview
Source: https://github.com/JayKim88/claude-ai-engineering/tree/main/plugins/spec-interview/skills/spec-interview
Command: npx skills add https://github.com/JayKim88/claude-ai-engineering --skill spec-interview-jaykim88

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates structured requirements gathering by extracting topic, context, and focus areas from user prompts.

Core Features & Use Cases

  • Structured interview rounds: 2-4 in-depth questions per round across categories (Technical Implementation, User Experience, Business Logic, Concerns & Risks, Trade-offs, and Non-functional Requirements) to uncover edge cases and constraints.
  • Round-based refinement: Guides users through successive rounds until core functionality, risks, and non-functional requirements are captured.
  • Automated spec generation: Produces a comprehensive technical specification document from collected answers, aligned to a standardized template.

Quick Start

Say interview me about [topic] to begin the interactive Q&A and generate a complete spec.

Frequently Asked Questions about spec-interview

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate requirements gathering for a technical specification?

Automating requirements gathering involves extracting topic and context from prompts, then running structured Q&A rounds across technical, business, and UX categories to produce a complete specification document.

What is AI-driven requirements interviewing for software projects?

AI-driven requirements interviewing uses interactive Q&A sessions to rotate through focus areas like technical implementation, user experience, and non-functional requirements, surfacing edge cases to generate precise specs.

How do I generate a standardized spec document from unstructured project ideas?

Generating a standardized spec document requires guiding users through successive interview rounds to capture core functionality, risks, and non-functional criteria, then compiling answers into an aligned technical specification.

Does automated requirements interviewing cover edge cases and trade-offs?

Automated requirements interviewing covers edge cases by applying structured questions across categories including concerns, risks, trade-offs, and non-functional requirements until all constraints are captured.

What's the best way to capture non-functional requirements during project planning?

The best way to capture non-functional requirements is through round-based interactive interviews that systematically probe technical implementation, business logic, and risk categories to refine project specifications.

When do I need structured requirements interviews for documentation?

Structured requirements interviews are needed when documenting complex projects where edge cases, constraints, and trade-offs must be surfaced through categorized Q&A before generating a comprehensive technical specification.