skills.rest
ThuHuynh1438
ThuHuynh1438COMMUNITY
Explore all skills by this author →
GitHub

interview

Interviews spec files to surface hidden requirements across technical, UX, and business dimensions.

Updated Apr 8, 2026
Search Tags:#requirements#interview#spec#edge-cases#prd#product-management#questioning
One-click install
npx skills add https://github.com/ThuHuynh1438/pm-kit --skill interview-thuhuynh1438
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: interview
Source: https://github.com/ThuHuynh1438/pm-kit/tree/main/.claude/skills/interview
Command: npx skills add https://github.com/ThuHuynh1438/pm-kit --skill interview-thuhuynh1438

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Interview skill helps product teams surface hidden requirements by guiding a focused, step-by-step discussion around a spec file, ensuring no critical details are missed.

Core Features & Use Cases

  • Probing framework: asks probing questions across technical, UI/UX, business, and risk dimensions to uncover edge cases and ambiguities.
  • Structured workflow: enforces one-question-at-a-time interrogation, captures notes, and tracks decisions and rationale.
  • Summarization: compiles finalized requirements into a complete, actionable spec document ready for review.

Quick Start

Begin a session by initiating the interview and providing the target spec file path for immediate, thorough requirement gathering.

Frequently Asked Questions about interview

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

FAQPage Schema
How do I surface hidden requirements and edge cases when reviewing a product spec?▼

To surface hidden requirements during a spec review, you can conduct a structured interview that probes technical, UX, and business dimensions. This method enforces one-question-at-a-time questioning to uncover ambiguities and capture edge cases.

What is the best way to brainstorm and clarify questions for a PRD?▼

The best way to brainstorm and clarify questions for a PRD is through a structured interrogation framework. It systematically probes technical, UI/UX, business, and risk dimensions, capturing decisions and rationale to finalize requirements.

How do I capture decisions and rationale during a requirements gathering session?▼

You can capture decisions and rationale during a requirements gathering session by using a structured workflow that records notes alongside each probing question. This ensures all finalized requirements are tracked and compiled into an actionable spec.

Can I use structured interviews to compile finalized requirements into a written spec document?▼

Yes, you can use structured interviews to compile finalized requirements into a written spec document. The process tracks decisions across technical and business dimensions, ultimately summarizing the finalized requirements into an actionable spec ready for review.

Does structured requirement interviewing work for capturing technical and business edge cases?▼

Yes, structured requirement interviewing works effectively for capturing technical and business edge cases. It applies a probing framework across technical, UI/UX, and risk dimensions to systematically uncover hidden ambiguities and edge cases in your spec.

Related Skills

Explore More Product & Management Skills→
GenerativeAgentsGenerativeAgents

prd-writing

Generate a review-ready PRD from initial-requirements.md using the PRD template.

Official
Advanced
zig-whatwgzig-whatwg
11

WHATWG Specification Implementation Skill

Translate WHATWG specifications into Zig implementations with numbered spec references.

Official
Advanced
product-on-purposeproduct-on-purpose
527

deliver-user-stories

Generate user stories and Given/When/Then acceptance criteria from product requirements.

Official
Basic
mori-shin-xmori-shin-x
12

speckit-clarify

Identify and resolve ambiguities in feature specifications through structured requirement analysis.

Community
Advanced