interview

Convert vague feature ideas into structured requirements and living documentation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides you through a structured interview process to turn vague feature ideas into a clear set of requirements and living documentation, enabling reliable handoffs to design and engineering.

Core Features & Use Cases

  • Structured requirement discovery: Ask targeted questions to surface goals, constraints, success criteria, and user needs.
  • Artifact generation: Produce three living documents in specs/<feature-name>/ (spec.md, plan.md, tasks.json) to guide implementation.
  • Ambiguity resolution: Proactively identify gaps and capture explicit decisions, reducing rework.
  • Iterative collaboration: Iterate with stakeholders to refine scope and maintain up-to-date documentation as requirements evolve.

Quick Start

Start by answering core prompts: What feature do you want to build? What problem does it solve? Who are the users and what’s their goal? What does success look like? I will generate the specs, plan, and actionable tasks and present them for review.

Frequently Asked Questions about interview

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

FAQPage Schema
How do I turn vague feature ideas into clear product requirements?

A structured spec interview helps convert vague feature ideas into clear requirements by asking targeted questions to surface goals, constraints, and user needs. It proactively identifies gaps and captures explicit decisions to reduce rework during product discovery.

What is the best way to document feature specs for engineering handoff?

The best way to document feature specs for engineering handoff is to generate living artifacts like spec.md, plan.md, and tasks.json. These documents capture explicit decisions and actionable tasks, ensuring reliable communication and iterative collaboration with stakeholders.

How do I start a spec interview for product discovery?

To start a spec interview for product discovery, answer core prompts about what feature you want to build, what problem it solves, who the users are, and what success looks like. The system then generates specs, plans, and actionable tasks for your review.

Can I maintain living documentation as requirements evolve over time?

Yes, you can maintain living documentation as requirements evolve by iterating with stakeholders to refine scope. The generated spec.md, plan.md, and tasks.json files are designed to be updated continuously, keeping your feature documentation current.

Does structured requirement discovery work for design discussions?

Structured requirement discovery works effectively for design discussions by enforcing targeted questioning to surface user needs and constraints. It helps identify gaps early and capture explicit decisions, aligning design and engineering on clear success metrics.