interview

Conduct structured feature interviews and output a formal specification document.

Updated May 24, 2025

Search Tags:#specification #requirements #discovery #interview #product-management #stakeholders

Ready to run

npx skills add https://github.com/lemeb/python-library-cookiecutter --skill interview-lemeb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: interview
Source: https://github.com/lemeb/python-library-cookiecutter/tree/main/%7B%7Bcookiecutter.project_slug%7D%7D/.claude/skills/interview
Command: npx skills add https://github.com/lemeb/python-library-cookiecutter --skill interview-lemeb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured feature interviews help teams gather clear requirements before coding, surfacing hidden assumptions early and guiding design decisions.

Core Features & Use Cases

Structured questioning across phases to uncover scope, risks, and acceptance criteria.
Multi-mode interview: default rigorous, quick, and first-principles to fit different knowledge levels and needs.
Outputs a formal specification document ready for implementation.

Quick Start

Describe a feature idea and initiate the interview session to begin gathering requirements.

Frequently Asked Questions about interview

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

FAQPage Schema

How do I conduct structured requirement discovery interviews for product management?▼

Structured requirement discovery interviews use multi-phase questioning to probe scope, UX, technical design, and edge cases. This process surfaces hidden assumptions early and guides design decisions for complex cross-functional features.

What is the best way to gather clear feature specifications before coding?▼

The best way to gather clear feature specifications is through a structured interview that questions stakeholders across multiple phases. This rigorous discovery process outputs a formal specification document ready for implementation.

Can I use different interview modes to clarify ambiguous product requirements?▼

Yes, you can clarify ambiguous product requirements using multi-mode interviews. Default rigorous, quick, and first-principles modes adapt the requirement gathering process to fit different stakeholder knowledge levels and project needs.

When do I need to run a formal stakeholder interview for feature implementation?▼

You need a formal stakeholder interview for feature implementation when facing ambiguous requirements, complex features, or cross-functional collaborations. It enforces structured questioning to uncover scope, risks, and acceptance criteria.

How do I start a requirement gathering session for complex cross-functional features?▼

To start a requirement gathering session, describe a feature idea and initiate the interview. The structured questioning process will then guide you through phases to uncover technical design, scope, and edge cases.

What limitations exist when using quick mode versus rigorous mode for requirement discovery?▼

Quick mode limits requirement discovery depth compared to the default rigorous mode. Use quick mode for familiar features with known scope, while rigorous mode ensures thorough probing of edge cases and technical design for complex features.