interview

Guide teams to extract concrete product intents via one-question-at-a-time interviews.

4|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/leocosta/octopus --skill interview-leocosta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interview
Source: https://github.com/leocosta/octopus/tree/main/skills/interview
Command: npx skills add https://github.com/leocosta/octopus --skill interview-leocosta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This interview process helps teams convert vague ideas into a concrete, shareable feature intent by guiding stakeholders through a focused, one-question-at-a-time discovery session.

Core Features & Use Cases

  • Interactive, adaptive questioning that converges on a clear root goal.
  • Produces a confirmed intent summary ready for downstream work (doc-align, doc-prd, or implement).
  • Tracks progress and surfaces unresolved branches to keep discovery focused.

Quick Start

Begin by restating the user's goal, then ask one focused question at a time to converge on a concrete intent.

Frequently Asked Questions about interview

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

FAQPage Schema
How do I convert vague product ideas into a concrete feature scope?

Conducting discovery interviews involves restating the user's goal, then asking one focused question at a time to converge on a concrete intent, tracking progress and resolving branches to shape a ticket-sized scope.

When should I use stakeholder interviews for product discovery?

Stakeholder interviews for product discovery are best used during early phases when no plan exists, helping teams align stakeholders and extract concrete product intents from vague ideas before shaping downstream tasks.

Can I use a decision tree to align teams during requirements discovery?

Yes, using a dynamic decision tree with a root anchor during requirements discovery tracks progress and surfaces unresolved branches, keeping the interview focused on converging toward a clear root goal.

What is the best way to extract concrete product intents from stakeholders?

The best way to extract concrete product intents is through an adaptive, one-question-at-a-time interview that converges vague ideas into a confirmed intent summary ready for downstream work.

What to do after extracting a confirmed feature intent summary?

After extracting a confirmed feature intent summary, teams can pass the ticket-sized scope to downstream tasks like doc-align, doc-prd, or implement to continue the development workflow.