interview

Guide five-phase discovery interviews to produce purpose statements and JTBD maps.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/haabe/tic-tac-toe --skill interview-haabe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interview
Source: https://github.com/haabe/tic-tac-toe/tree/main/.claude/skills/interview
Command: npx skills add https://github.com/haabe/tic-tac-toe --skill interview-haabe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Progressive onboarding through structured discovery conversations to clarify purpose, vision, and strategy for a product or project.

Core Features & Use Cases

  • Five-phase interview framework (Purpose & Vision, Users & Jobs, North Star & Metrics, Landscape & Strategy, Current State) to guide conversations.
  • Outputs include a purpose statement, JTBD maps per user type, a north-star framework, strategic context, and initial opportunity areas.
  • Ideal for onboarding new teams, refreshing context after major changes, and aligning stakeholders across functions.

Quick Start

Initiate a structured discovery interview with a key stakeholder to capture purpose, user needs, success metrics, and strategic priorities, then document the outputs.

Frequently Asked Questions about interview

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

FAQPage Schema
What is a structured discovery interview for product management onboarding?

A structured discovery interview for product management onboarding is a facilitator-driven conversation that clarifies purpose, user needs, and success metrics. It uses a five-phase framework to align stakeholders and document artifacts like JTBD maps and north-star metrics.

How do I conduct a stakeholder alignment interview for a new product initiative?

To conduct a stakeholder alignment interview, guide the conversation through five phases: Purpose & Vision, Users & Jobs, North Star & Metrics, Landscape & Strategy, and Current State. Document the outputs to generate purpose statements and initial opportunity areas.

Can this structured discovery process help align stakeholders after major scope changes?

Yes, this structured discovery process helps align stakeholders after major scope changes by refreshing context. It captures updated strategic priorities, user needs, and success metrics to ensure cross-functional teams remain aligned on the revised project purpose.

What's the best way to map user jobs and define north-star metrics during product discovery?

The best way to map user jobs and define north-star metrics is through a guided discovery framework that interviews key stakeholders. This process generates JTBD maps per user type and establishes a north-star framework to measure product success.

When do I need a facilitator-driven discovery conversation instead of standard product documentation?

You need a facilitator-driven discovery conversation when onboarding new teams, refreshing context after major changes, or aligning stakeholders across functions. It solves context gaps that standard documentation cannot by capturing strategic context and opportunity areas.

Are there limitations to using a five-phase interview framework for stakeholder alignment?

A limitation of the five-phase interview framework is that it requires a defined facilitator to drive the workflow and active stakeholder participation. It is designed for significant scope changes or new initiatives, not minor feature updates or solo planning.