interview

Guide structured pre-design interviews and generate a discovery.md brief.

7|Updated Feb 20, 2026

Search Tags:#design #requirements #discovery #interview #discovery brief

Ready to run

npx skills add https://github.com/skullninja/coco-workflow --skill interview-skullninja

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: interview
Source: https://github.com/skullninja/coco-workflow/tree/main/skills/interview
Command: npx skills add https://github.com/skullninja/coco-workflow --skill interview-skullninja

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured pre-design interviews are often ad-hoc and fail to capture deep user intent and constraints. This skill provides a guided approach to elicit the essential context and produces a discovery brief (discovery.md) that feeds the design skill.

Core Features & Use Cases

Guided interview flow that covers problem motivation, users, scope, functional requirements, technical context, and non-functional aspects.
Generates a discovery brief (discovery.md) that is consumed by the design skill to drive downstream work.
Supports iterative refinement by updating the discovery brief and preserving prior context for session continuity.

Quick Start

Ask Claude to start a discovery interview for a feature to generate a discovery.md.

Frequently Asked Questions about interview

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

FAQPage Schema

How do I conduct a structured pre-design interview for feature discovery?▼

A structured pre-design interview uses a guided flow to elicit user intent, constraints, and requirements. This approach covers problem motivation, scope, functional needs, and technical context to produce a discovery brief for planning.

What questions should I ask during product discovery to capture user requirements?▼

Product discovery interviews should ask about problem motivation, target users, scope, functional requirements, technical context, and non-functional aspects. Using a template-driven process ensures you capture deep intent and essential constraints before design work begins.

How do I create a discovery brief before starting software design?▼

To create a discovery brief, run a guided interview that gathers deep user intent and project constraints. The session outputs a discovery.md file that feeds directly into the design skill to drive downstream work.

Can I refine a discovery brief if requirements change after the initial interview?▼

Yes, the discovery brief supports iterative refinement. You can update the document while preserving prior context and session memory, ensuring continuity and capturing new requirements as the feature discovery process evolves.

When do I need a discovery brief for my feature planning?▼

You need a discovery brief during feature discovery and planning, specifically before design work begins. It captures essential context, deep user intent, and constraints that prevent ad-hoc requirements gathering from failing downstream design.

What is the best way to document non-functional requirements during user interviews?▼

The best way to document non-functional requirements is using a repeatable, template-driven interview flow. This ensures technical context and non-functional aspects are captured alongside functional needs in a structured discovery brief.