skills.rest
JonnyCBB
JonnyCBBCOMMUNITY
Explore all skills by this author →
GitHub

interview

Facilitate structured interviews to elicit requirements and produce a formal requirements document.

1|Updated Dec 17, 2025
Search Tags:#planning#requirements#discovery#interview#acceptance-criteria#stakeholders
One-click install
npx skills add https://github.com/JonnyCBB/claude-code-config --skill interview-jonnycbb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: interview
Source: https://github.com/JonnyCBB/claude-code-config/tree/main/plugins/jbb-feature-dev/skills/interview
Command: npx skills add https://github.com/JonnyCBB/claude-code-config --skill interview-jonnycbb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gather human-only context through structured questioning before automated research begins. Only ask questions that codebase-explorer and /operational-context cannot answer.

Core Features & Use Cases

  • Structured requirement elicitation through guided questioning.
  • Supports premise challenge, scope mode selection, and acceptance criteria generation.
  • Produces a formal requirements document ready for downstream planning.

Quick Start

Start a structured interview to gather requirements for a new feature.

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 new feature discovery before starting research?▼

Structured requirement elicitation works by enforcing a protocol for premise challenge, scope mode selection, and mutual understanding to extract human-only context before automated research begins.

What is structured requirement elicitation and how does it work?▼

Structured requirement elicitation works by enforcing a protocol for premise challenge, scope mode selection, and mutual understanding to extract human-only context before automated research begins.

How do I define acceptance criteria and align scope with stakeholders for a product feature?▼

You should use structured requirement interviews to gather human-only context, specifically asking questions that codebase-explorer and operational-context tools cannot answer.

When do I need to use structured interviews for requirement gathering?▼

You should use structured requirement interviews to gather human-only context, specifically asking questions that codebase-explorer and operational-context tools cannot answer.

What questions should I ask stakeholders during product requirement discovery?▼

Structured requirement interviews apply to new feature discovery, scope alignment, and acceptance criteria definition across product, engineering, and design contexts to produce formal requirements documents.

Can I use structured interviews for scope alignment across engineering and design contexts?▼

Structured requirement interviews apply to new feature discovery, scope alignment, and acceptance criteria definition across product, engineering, and design contexts to produce formal requirements documents.

Related Skills

Explore More Product & Management Skills→
shafibabarshafibabar
1

system-context-diagram

Creates a C4 Level 1 System Context Diagram identifying human actors and external system dependencies.

Community
Intermediate
AgLyx3AgLyx3

agile-product-owner

Generate user stories and acceptance criteria for agile backlog management.

Community
Advanced
BrennonTWilliamsBrennonTWilliams
7

ll-refine-issue

Refine software issue documentation via codebase research and gap analysis.

Community
Intermediate
Leep-GHLeep-GH

prd-intake

Translate non-technical PRDs into architecture decisions and a Build Plan.

Community
Intermediate