interview

Guide structured interviews to develop feature specification documents.

10|5|Updated Dec 12, 2025
One-click install
npx skills add https://github.com/ils15/pantheon --skill interview-ils15
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interview
Source: https://github.com/ils15/pantheon/tree/main/platform/windsurf/.windsurf/skills/interview
Command: npx skills add https://github.com/ils15/pantheon --skill interview-ils15

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the process of converting rough ideas into detailed specifications for features, saving time and reducing rework.

Core Features & Use Cases

  • Interview Protocol: Guides users through a structured conversation to capture feature requirements comprehensively.
  • Spec Output Format: Provides a clear template for feature specifications, including scope, goals, and technical requirements.
  • Use Case: When brainstorming a new feature for your project, use this Skill to facilitate a structured interview with stakeholders and create a well-defined spec document.

Quick Start

/sketch "Discuss and outline the user onboarding process."

Frequently Asked Questions about interview

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

FAQPage Schema
How do I create detailed feature specifications from rough project ideas?

Feature specification creation is streamlined through a structured interview process that guides stakeholders to comprehensively capture scope, users, constraints, and success criteria for software features. This reduces misalignment between stakeholders and development teams by converting rough ideas into actionable spec documents.

What is a structured interview for requirement gathering?

A structured interview for requirement gathering is a guided conversation protocol that systematically captures feature scope, goals, and technical requirements. It ensures comprehensive coverage of project planning needs by focusing on specific software feature dimensions, reducing rework and improving stakeholder communication.

How do I start gathering requirements for a new software feature?

To start gathering requirements, initiate a structured interview to discuss and outline the feature, such as a user onboarding process. The interview protocol guides you through capturing scope, users, constraints, and success criteria, ultimately producing a detailed spec document for development teams.

Can I use a structured interview to reduce misalignment between stakeholders and developers?

A structured interview reduces misalignment between stakeholders and development teams by facilitating a guided conversation that comprehensively captures feature requirements. It focuses on scope, users, constraints, and success criteria, ensuring all parties share a clear understanding before technical implementation begins.

What is the best way to document feature scope and technical requirements?

The best way to document feature scope and technical requirements is using a structured spec output format generated through an interview protocol. This template includes goals, scope, and technical requirements, converting rough ideas into detailed, actionable specification documents for development teams.

When should I use a structured interview for feature spec documentation instead of writing it directly?

Use a structured interview for feature spec documentation when you need to convert rough ideas into detailed specifications comprehensively. It is ideal when brainstorming new features, ensuring all scope, users, constraints, and success criteria are captured systematically to save time and reduce rework.