wsbaser:interview

Interview users to extract feature requirements and generate a self-contained specification document.

1|Updated Feb 21, 2026

Search Tags:#planning #documentation #requirements #interview #spec #feature #product-management

Ready to run

npx skills add https://github.com/wsbaser/claude-plugins --skill wsbaser-interview

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wsbaser:interview
Source: https://github.com/wsbaser/claude-plugins/tree/main/plugins/wsbaser/skills/interview
Command: npx skills add https://github.com/wsbaser/claude-plugins --skill wsbaser-interview

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Interview skill guides an in-chat discovery session to extract feature requirements, capture constraints, and collect external references, then converts that context into a complete, self-contained specification document.

Core Features & Use Cases

Guides a structured interview flow to elicit feature name, scope, and constraints from the conversation.
Generates a self-contained spec that can drive implementation, testing, and planning.
Supports an implementation plan workflow and produces a reuse map to leverage existing primitives in the codebase.

Quick Start

Initiate an in-chat interview to extract a feature's requirements and generate a complete spec document.

Frequently Asked Questions about wsbaser:interview

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

FAQPage Schema

How do I write feature requirements through an interview process?▼

Feature requirements are written through an interview process by guiding an in-chat discovery session to extract scope and constraints, converting the gathered context into a complete specification document.

How do I generate a self-contained spec from a conversation?▼

You can generate a self-contained spec from a conversation by identifying feature requirements through an interview, applying findings to outline functional and non-functional requirements, design decisions, and acceptance criteria.

Can I create an implementation plan that reuses existing codebase patterns?▼

Yes, you can create an implementation plan that reuses existing codebase patterns by supporting a specific workflow that produces a reuse map to leverage existing primitives alongside the generated specification.

What is the best way to capture functional and non-functional requirements for product management?▼

The best way to capture functional and non-functional requirements for product management is conducting a structured interview to elicit constraints, embedding implementation-critical assumptions directly in the generated spec.

Does this interview-driven spec workflow work without external dependencies?▼

Yes, the interview-driven spec workflow operates without external dependencies, guiding the discovery session internally to collect context and external references before generating the specification document.