spec-interview

Guide iterative user interviews to generate complete feature specification documents.

11|2|Updated May 29, 2025

Search Tags:#workflow #templates #documentation #specification #requirements #interview

Ready to run

npx skills add https://github.com/yulonglin/dotfiles --skill spec-interview-yulonglin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-interview
Source: https://github.com/yulonglin/dotfiles/tree/main/claude/skills/spec-interview
Command: npx skills add https://github.com/yulonglin/dotfiles --skill spec-interview-yulonglin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Iterative interviews help teams uncover and crystallize requirements before implementation, reducing misalignment and rework.

Core Features & Use Cases

Interview-driven spec creation: Guides users through focused questions to surface requirements, constraints, and acceptance criteria.
Template-backed output: Generates a complete SPEC.md by integrating with reference templates (spec-template.md) and context.
Context reuse and handoff: Reads existing context or specs to drive incremental refinement across sessions.

Quick Start

Start a new session with the spec-interview workflow to generate specs in specs/ for a large feature.

Frequently Asked Questions about spec-interview

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

FAQPage Schema

How do I write complete feature specifications before implementation?▼

You craft complete feature specifications through guided user interviews that surface requirements, constraints, and acceptance criteria. This iterative questioning approach uncovers UX concerns, risks, and tradeoffs to produce a structured spec document.

What is the best way to gather product requirements for large features?▼

The best way to gather product requirements for large features is through iterative interviews that systematically explore context, constraints, and tradeoffs. This structured approach ensures alignment across product, design, and engineering workflows before development starts.

How do I create a spec template from existing context?▼

Creating a spec from existing context involves reading current specs to drive incremental refinement across sessions. The interview workflow integrates this context with reference templates to output a finalized specification document.

Can I use iterative interviews to refine specifications across multiple sessions?▼

Yes, iterative interviews support refining specifications across multiple sessions by reading existing context or specs to drive incremental updates. This allows teams to continuously crystallize requirements and update the output document as the feature evolves.

Does structured requirement gathering work for engineering and design workflows?▼

Structured requirement gathering works for engineering and design workflows by asking focused questions that address specific functional requirements, UX concerns, and technical tradeoffs. It applies to large features requiring cross-functional alignment.

Why does requirement gathering miss critical risks and tradeoffs?▼

Requirement gathering misses critical risks and tradeoffs when it lacks structured questioning to surface constraints. An interview-driven specification process forces teams to explicitly uncover and document these edge cases before finalizing the implementation.