spec-interview

Conduct structured interviews to identify requirement gaps and generate SPEC.md.

2|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/kangminhyuk1111/agents --skill spec-interview-kangminhyuk1111
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-interview
Source: https://github.com/kangminhyuk1111/agents/tree/main/skills/spec-interview
Command: npx skills add https://github.com/kangminhyuk1111/agents --skill spec-interview-kangminhyuk1111

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams convert vague or incomplete requirements into a concrete, actionable specification by guiding a structured multi-round interview that surfaces gaps, decisions, and risks.

Core Features & Use Cases

  • Reads existing requirement documents (SPEC.md, PRD.md, REQUIREMENTS.md, README.md with requirements) to anchor the interview and identify gaps.
  • Conducts rigorous multi-round questioning using the AskUserQuestion tool to surface unknowns, trade-offs, and edge cases.
  • Outputs a complete SPEC.md that details functional, technical, UX, and rollout considerations, with traceability to source questions and answers for future audits.
  • Use case: You have unclear user stories; run this skill to generate a comprehensive SPEC.md for design and engineering handoff.

Quick Start

Initiate the multi-round spec interview on the target project to generate SPEC.md.

Frequently Asked Questions about spec-interview

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

FAQPage Schema
How do I turn vague project requirements into a clear specification document?

To turn vague requirements into a clear specification, this Skill conducts a structured, multi-round interview that surfaces gaps and decisions, outputting a complete SPEC.md with functional, technical, and UX considerations for engineering handoff.

How do I identify ambiguities and edge cases in existing requirement documents?

To identify ambiguities in existing requirement documents, the Skill reads files like SPEC.md, PRD.md, and REQUIREMENTS.md to anchor an interview, revealing unknowns, trade-offs, and edge cases through rigorous multi-round questioning.

What is the best way to gather requirements and generate a SPEC.md for engineering handoff?

The best way to gather requirements for a SPEC.md is running a structured spec workflow interview that asks targeted questions, captures answers with traceability, and produces acceptance criteria and risk considerations for design and engineering teams.

Can I use existing PRD or README files to anchor the requirements gathering interview?

Yes, you can use existing PRD.md, SPEC.md, REQUIREMENTS.md, or README files to anchor the requirements gathering interview, allowing the Skill to analyze current documentation and immediately identify missing functional and technical details.

Does the generated specification include acceptance criteria and risk considerations?

Yes, the generated specification includes acceptance criteria and risk considerations, detailing functional, technical, UX, and rollout aspects with traceability to source questions for future audits.

Why does my requirements gathering process miss critical edge cases during product management?

Your requirements gathering process may miss edge cases without a structured spec workflow that conducts rigorous multi-round questioning, directly addressing incomplete user stories by forcing explicit decisions on unknowns and trade-offs.