interview

Formalize plan and design discussions into a testable spec with user stories.

135|25|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/jvm-skills/jvm-skills --skill interview-jvm-skills
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interview
Source: https://github.com/jvm-skills/jvm-skills/tree/main/.junie/skills/interview
Command: npx skills add https://github.com/jvm-skills/jvm-skills --skill interview-jvm-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interviewing stakeholders to establish shared understanding and produce a precise, testable specification with explicit user stories.

Core Features & Use Cases

  • Relentless, structured questioning to uncover decisions across entry points, journeys, roles, and edge cases.
  • Enforces mandatory topics and cross-cutting invariants to surface potential gaps and risks.
  • Outputs a complete spec with a final ## User Stories section that aligns stakeholders and development teams.

Quick Start

Initiate a focused interview session and iteratively ask questions until a complete spec with user stories is written.

Frequently Asked Questions about interview

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

FAQPage Schema
How do I gather product design requirements into a testable spec?

You can gather product design requirements into a testable spec by initiating a relentless interview process that formalizes discussions into structured user stories, capturing entry points, user journeys, and invariants.

What is the best way to conduct stakeholder interviews for feature planning?

The best way to conduct stakeholder interviews for feature planning is to apply structured, relentless questioning across multiple roles and edge cases, ensuring mandatory topics and cross-cutting invariants are covered to surface gaps and risks.

How does structured interviewing help uncover architecture decisions and edge cases?

Structured interviewing helps uncover architecture decisions and edge cases by enforcing relentless questioning that surfaces hidden gaps and risks, ultimately producing a complete specification with a final section of structured user stories.

Can I use this approach to generate user stories from product management discussions?

Yes, you can use this approach to generate user stories from product management discussions by iteratively asking targeted questions until a complete, shared specification with explicit user stories is written and aligned.

When do I need a relentless interview process for requirements gathering?

You need a relentless interview process for requirements gathering when you must establish shared understanding across stakeholders and translate design, architecture, or feature planning discussions into a precise, testable specification.

Does this specification method work for both architecture decisions and product design reviews?

Yes, this specification method works for both architecture decisions and product design reviews by applying structured questioning across multiple roles and edge cases to formalize plans into a shared, testable spec with user stories.