interview

Conduct structured interviews to generate MDX documents with YAML frontmatter.

9|1|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/Roxabi/roxabi-plugins --skill interview-roxabi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interview
Source: https://github.com/Roxabi/roxabi-plugins/tree/main/plugins/dev-core/skills/interview
Command: npx skills add https://github.com/Roxabi/roxabi-plugins --skill interview-roxabi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of gathering information for various documentation needs, ensuring comprehensive and structured output for brainstorming, analysis, and technical specifications.

Core Features & Use Cases

  • Structured Interviewing: Guides users through a series of questions tailored to the desired output type (brainstorm, analysis, spec).
  • Document Promotion: Can take existing documents and promote them to the next level of detail (e.g., a brainstorm to an analysis).
  • Use Case: When starting a new feature, use this Skill to conduct a structured interview to generate a detailed technical specification, ensuring all aspects from user needs to edge cases are considered.

Quick Start

Use the interview skill to start a new spec for the feature 'user authentication'.

Frequently Asked Questions about interview

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

FAQPage Schema
How do I gather requirements for technical specifications through an interview?

Requirements gathering through a structured interview systematically probes for context, scope, depth, and validation, outputting technical specifications in MDX format with YAML frontmatter.

What is the best way to turn a brainstorm document into a detailed analysis?

Document promotion takes existing brainstorms or analyses and elevates them to the next level of detail by conducting a follow-up interview that probes for missing scope and validation.

Can I generate MDX documentation with YAML frontmatter for software engineering specs?

Yes, structured interviewing generates software engineering documents in MDX format with YAML frontmatter, systematically probing context, scope, depth, and validation for technical specifications.

Does the interview process identify existing related documents to inform the current session?

Yes, the interview process identifies existing related documents to inform the current session, systematically probing for context, scope, depth, and validation to ensure comprehensive output.

When do I need a structured interview for brainstorming and analysis?

You need a structured interview for brainstorming and analysis when starting a new feature, ensuring all aspects from user needs to edge cases are considered before generating documentation.

What are the limitations of using automated interviews for generating technical specifications?

The interview process output is limited to MDX format with YAML frontmatter, focusing on tailored questions for brainstorming, analysis, or technical specifications rather than freeform documentation generation.