interview

Conduct structured product interviews and generate SPEC.md files.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/emirrtopaloglu/claude-code-virtuoso --skill interview-emirrtopaloglu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interview
Source: https://github.com/emirrtopaloglu/claude-code-virtuoso/tree/main/.claude/skills/interview
Command: npx skills add https://github.com/emirrtopaloglu/claude-code-virtuoso --skill interview-emirrtopaloglu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams turn vague product ideas into precise, actionable specifications by conducting a structured interview led by a Product Manager, ensuring all details are captured before drafting a spec.

Core Features & Use Cases

  • Structured interviews: Guided questioning to elicit edge cases, user flows, and limitations.
  • Monetization & feasibility checks: Integrates monetization assessment and optional technical feasibility review to validate viability.
  • SPEC generation: Produces a complete specification using the SPEC-TEMPLATE and saves it to the designated repository.
  • Spec storage & review: Writes the finished spec to .claude/docs/specs/[feature-name].md and presents a final summary for approval.

Quick Start

Provide your feature idea as $ARGUMENTS and let a product-manager lead the interview to generate a SPEC.md.

Frequently Asked Questions about interview

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

FAQPage Schema
How do I turn a vague product idea into a concrete specification document?

Turning a vague product idea into a concrete specification requires a structured PM-led interview to identify precise product requirements, assess monetization, and validate technical feasibility before drafting a spec.

What is the best way to conduct product discovery interviews for feature requirements?

Product discovery interviews for feature requirements work best when a product manager guides structured questioning to elicit user flows, edge cases, and limitations, ensuring all details are captured before drafting a specification.

How do I write a spec file that includes monetization and technical feasibility checks?

Writing a spec file with monetization and feasibility checks involves conducting a structured PM-led interview, validating viability during the workflow, and generating the final specification using a standardized template.

Can I automatically generate and save a SPEC.md file from a feature idea?

Yes, you can automatically generate and save a SPEC.md file by providing your feature idea as input, which triggers a structured interview and writes the completed specification to the designated repository path.

Does the spec generation process wait for user approval before finalizing the document?

Yes, the spec generation process awaits user approval by presenting a final summary for review after drafting the specification, ensuring the documented product requirements meet your expectations before saving.

What are the limitations of using automated interviews for spec writing?

Automated interviews for spec writing constrain outputs strictly to a predefined SPEC-TEMPLATE, meaning the generated specification relies entirely on the structured inputs provided during the initial product discovery questioning phase.