interview

Conducts interactive requirements interviews for software features and analyzes existing specifications.

19|4|Updated Jan 4, 2026

Search Tags:#planning #specification #clarification #interview #requirements gathering #elicitation

Ready to run

npx skills add https://github.com/wunki/amplify --skill interview-wunki

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: interview
Source: https://github.com/wunki/amplify/tree/main/skills/interview
Command: npx skills add https://github.com/wunki/amplify --skill interview-wunki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of incomplete or vague requirements by conducting thorough, structured interviews to elicit all necessary details before implementation begins.

Core Features & Use Cases

Exhaustive Questioning: Covers purpose, technical, UI/UX, edge cases, tradeoffs, security, testing, and rollout.
Context-Aware: Reads existing SPEC.md and codebase to avoid redundant questions.
Structured Output: Gathers information to hand off to create-spec or create-plan.
Use Case: When starting a new, complex feature, use this skill to ensure all potential issues and requirements are identified and documented upfront, preventing costly rework later.

Quick Start

Use the interview skill to gather requirements for the new user authentication system.

Frequently Asked Questions about interview

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

FAQPage Schema

How do I gather complete requirements for a complex software feature before implementation?▼

To gather complete requirements for a complex software feature, conduct an exhaustive requirements interview covering technical constraints, UI/UX, edge cases, security, and rollout considerations to prevent costly rework.

What is the best way to identify gaps in existing software specifications?▼

The best way to identify gaps in existing software specifications is to analyze the current SPEC.md and codebase contextually, then probe missing details regarding tradeoffs, testing, and edge cases interactively.

Can I use interactive questioning to elicit UI/UX and security requirements for new features?▼

Yes, you can use interactive questioning to elicit UI/UX and security requirements, as structured requirements gathering covers purpose, technical details, edge cases, tradeoffs, security, testing, and rollout considerations.

How do I structure gathered requirements for spec writing and planning?▼

Structure gathered requirements for spec writing by consolidating interview answers into a structured output format designed for direct handoff to specification creation or feature planning workflows.

Does requirements gathering work with an existing codebase to avoid redundant questions?▼

Yes, requirements gathering works with an existing codebase by reading existing specification files and code to understand current context, ensuring the interactive questioning avoids asking redundant or already answered questions.