skills.rest
JochenYang
JochenYangCOMMUNITY
Explore all skills by this author →
GitHub

requirements-interview

Interview users to elicit requirements and generate SPEC.md, PRD.md, and PLAN.md.

21|3|Updated Jan 22, 2026
Search Tags:#planning#documentation#requirements#PRD#interview#SPEC#AskUserQuestionTool
One-click install
npx skills add https://github.com/JochenYang/Jochen-ai-rules --skill requirements-interview
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-interview
Source: https://github.com/JochenYang/Jochen-ai-rules/tree/main/.claude/skills/requirements-interview
Command: npx skills add https://github.com/JochenYang/Jochen-ai-rules --skill requirements-interview

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill conducts deep, multi-round interviews using AskUserQuestionTool to elicit complete requirements and translate them into an executable development plan while syncing SPEC and PRD.

Core Features & Use Cases

  • Guided interviews: conducts structured Q&A to fill gaps and eliminate ambiguity.
  • SPEC/PRD generation: automatically produces and updates SPEC.md, PRD.md, and PLAN.md as the conversation progresses.
  • Risk & scope management: records business goals, scope boundaries, and trade-offs to guide prioritization.

Quick Start

Initiate the interview by gathering goals and constraints, then run iterative questions, and ensure SPEC.md, PRD.md, and PLAN.md are created or updated after each round.

Frequently Asked Questions about requirements-interview

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

FAQPage Schema
How do I gather complete software requirements when the initial project brief is ambiguous?▼

Eliminate ambiguous requirements by conducting structured, multi-round interviews that iteratively question stakeholders, filling gaps to elicit complete business goals, user profiles, and scope boundaries.

How do I write a PRD and SPEC from an incomplete list of product features?▼

Generate a PRD and SPEC by iteratively questioning project constraints, then automatically translating the elicited answers into updated SPEC.md, PRD.md, and PLAN.md documents for executable planning.

What is the best way to turn rough product ideas into an executable development plan?▼

Turning rough ideas into an executable development plan requires iterative interviews to capture data flows, risks, and milestones, continuously syncing the outputs into actionable planning documents.

Can I use structured interviews to manage project scope and define acceptance criteria?▼

Yes, structured interviews effectively manage project scope by recording trade-offs and scope boundaries during the Q&A process, directly translating the elicited constraints into clear milestones and acceptance criteria.

Do I need existing documentation to start a requirements discovery interview?▼

No, you do not need existing documentation to start requirements discovery; the interview process is designed to gather goals and constraints first, then progressively create and update the necessary SPEC and PRD files.

Related Skills

Explore More Product & Management Skills→
OzeroHAXOzeroHAX
32

docs-project-brief

Define project context, problem statement, and MVP boundaries.

Community
Basic
RDCrystalLabRDCrystalLab

prd-to-plan

Convert product requirements documents into phased implementation plans with vertical slices.

Official
Advanced
Snowflake-LabsSnowflake-Labs
12

read-ors-configuration

A concise summary of your roleplay character: name,</name> personality, and/or behavior, formatted as a single string sentence. Typically不超过50字，此处省略

Official
Intermediate
brsblbrsbl
14

spec

Generates product specification drafts via collaborative interviews and web research.

Community
Advanced