What is the purpose of the Interview skill?

It helps Claude understand the root problem (the WHY) behind a request to ensure the final solution aligns perfectly with your actual needs and constraints.

When should I use the /interview command?

Use it for complex tasks, when you need recommendations, during brainstorming sessions, or whenever a request is ambiguous and might be misunderstood.

How does this skill prevent errors?

It explicitly surfaces hidden assumptions and requires a mutual agreement on both the problem and the solution before Claude takes any action.

Can I use this for non-coding tasks?

Yes, the discovery framework is context-agnostic and works for documentation, automation design, and strategic brainstorming.

Strategic Intent Discovery

Name: Strategic Intent Discovery
Author: alijilani-dev

byalijilani-dev

Productividad y Flujo de Trabajo

Uncovers the underlying intent and validates assumptions through structured discovery conversations to ensure AI-generated solutions match user needs.

Acerca de

The Interview skill acts as a bridge between surface-level requests and meaningful results by facilitating a deep-dive discovery process. It employs techniques like laddering and assumption surfacing to prevent Claude from proceeding on incorrect premises. This skill is essential for high-stakes development, complex brainstorming, or any scenario where alignment is more important than immediate output, ensuring that the 'WHY' is fully understood before the 'WHAT' is built.

Características Principales

Explicit assumption surfacing and validation to prevent misalignment
Interactive '5 Whys' and laddering techniques for deep exploration
Collaborative solution exploration with informed trade-off analysis
Structured understanding summaries to reach mutual agreement before acting
Systematic 'WHY + WHAT' discovery framework to uncover root needs
0 GitHub stars

Casos de Uso

Gathering requirements and brainstorming architecture for new software projects
Validating technical assumptions during high-stakes refactoring or migrations
Clarifying ambiguous or multi-part feature requests before implementation

Acerca de

Características Principales

Explicit assumption surfacing and validation to prevent misalignment
Interactive '5 Whys' and laddering techniques for deep exploration
Collaborative solution exploration with informed trade-off analysis
Structured understanding summaries to reach mutual agreement before acting
Systematic 'WHY + WHAT' discovery framework to uncover root needs
0 GitHub stars

Casos de Uso

Gathering requirements and brainstorming architecture for new software projects
Validating technical assumptions during high-stakes refactoring or migrations
Clarifying ambiguous or multi-part feature requests before implementation