interview

Drives guided Q&A interviews to generate a written spec file.

Updated Feb 4, 2026

Search Tags:#specification #requirements #interview #trade-offs #elicitation #structured questioning

Ready to run

npx skills add https://github.com/OpenAEC-Foundation/conventions --skill interview-openaec-foundation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: interview
Source: https://github.com/OpenAEC-Foundation/conventions/tree/main/.claude/skills/interview
Command: npx skills add https://github.com/OpenAEC-Foundation/conventions --skill interview-openaec-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interviewing for complex specs can be time-consuming and prone to missing critical requirements. This Skill guides you to perform a thorough, structured interview to surface all concerns and derive a complete spec.

Core Features & Use Cases

Guided, in-depth questioning using the AskUserQuestionTool to reveal requirements, constraints, and tradeoffs.
Converts interview results into a formal spec file for downstream implementation.
Use Case: When a project involves ambiguous, high-risk requirements, run a structured interview to extract all concerns and document the spec.

Quick Start

Ask the user a detailed set of questions to surface hidden requirements and document the results into a spec file.

Frequently Asked Questions about interview

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

FAQPage Schema

How do I elicit complete requirements for ambiguous software projects?▼

To elicit complete requirements for ambiguous software projects, use a structured interview process that surfaces hidden constraints and trade-offs. This approach uses guided questioning to drive a thorough Q&A workflow, ensuring all critical concerns are articulated before implementation begins.

What is the best way to document a formal spec from user interviews?▼

The best way to document a formal spec from user interviews is to run a guided Q&A workflow that captures elicitation results. This method converts structured questioning outputs directly into a written spec file for downstream implementation.

Can I use structured questioning to uncover trade-offs in product development?▼

Yes, you can use structured questioning to uncover trade-offs in product development. By performing an in-depth interview using targeted elicitation, you reveal project constraints and high-risk requirements, ensuring your specification captures all functional concerns.

When do I need to run a structured interview for requirements elicitation?▼

You need to run a structured interview for requirements elicitation when a project involves complex, novel, or ambiguous high-risk requirements. This ensures a thorough Q&A workflow is applied to surface all concerns and derive a complete specification.

How does guided questioning work for creating a written spec document?▼

Guided questioning for creating a written spec document works by applying a structured interview mechanism to identify user requirements. It drives a Q&A workflow using targeted questions, then automatically converts the articulated answers into a formal spec file.