Agent skill

Interview

by jvm-skills in jvm-skills/jvm-skills

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree.

Apache-2.0Auto-check passedProduct & Project Management

Install Interview

skills CLI
$ npx skills add jvm-skills/jvm-skills --skill interview -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jvm-skills/jvm-skills interview --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jvm-skills/jvm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.junie/skills/interview .claude/skills/interview && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
interview
GitHub stars
140
Token cost
~804 tokens
SKILL.md length
416 words
Files
1
Skills in repo
16
Repo updated
First seen
Licence
Apache-2.0

At a glance

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree.

  • Tasks that involve User stories
  • SKILL.md covers Mandatory interview topics, Output format and Project Customization
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Interview is an agent skill from jvm-skills/jvm-skills. Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Outputs a spec with user stories.

Its SKILL.md is about 800 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering User stories. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve User stories

Example prompts

  • “/interview”

What it can do on your machine

Read from SKILL.md and the folder at commit c6d477f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Interview loads about 804 tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 416 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~45
When it runs · the whole SKILL.md, loaded when a task matches
~804

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jvm-skills/jvm-skills at commit c6d477f, republished under its Apache-2.0 licence (© jvm-skills). 416 words, ~804 tokens.

Download SKILL.mdSave it as .claude/skills/interview/SKILL.md (or your agent's skills folder).
name
interview
description
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Outputs a spec with user stories.

Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one.

Use the AskUserQuestionTool to ask about literally anything: technical implementation, UI & UX, concerns, tradeoffs, etc. — but make sure the questions are not obvious.

If a question can be answered by exploring the codebase, explore the codebase instead.

Mandatory interview topics

Beyond the feature's core mechanics, you MUST explicitly probe these areas:

  • Entry points: Where does the user navigate FROM to reach this feature? What existing page/nav/button needs to change?
  • User journey start-to-finish: Walk through the complete flow from "user is on an existing page" → "user discovers feature" → "user completes the feature" → "user returns to where they were"
  • Roles: Which user roles interact with this feature? Check references/project.md for the project's role list; otherwise infer from the codebase.
  • Edge cases: What happens on error, concurrent access, mobile vs desktop?
  • State transitions across roles: For each state change, which roles see it and how (real-time — SSE/websockets, polling, manual refresh)? What does each role's screen show before and after?
  • Terminal states & dead ends: For every end-state, what's the forward action? What URL params, cookies, or tokens does the entry point URL need?

Cross-cutting invariants (MANDATORY): Check references/project.md for the project's invariants document. If one exists, read it and for each invariant ask the "Spec-time question" section during the interview. Every invariant covers a bug class the team has shipped before. The spec must capture the decision for each one — do not leave them implicit.

Show full SKILL.md (157 more words)Show less

Output format

Be very in-depth and continue interviewing me continually until it's complete, then write the spec to the file.

The spec MUST end with a structured ## User Stories section. Derive these from the interview — every agreed-upon behavior becomes a story:

markdown
## User Stories

- **US-1**: As a [role], I [action] so that [outcome].
- **US-2**: As a [role], I [action] so that [outcome].
...

Rules for user stories:

  • Every user role that interacts with the feature must have at least one story
  • Navigation/entry point stories come FIRST (e.g. "As a manager, I see a game button on my dashboard so that I can start a ranking game")
  • Cover the happy path, key error states, and edge cases
  • Stories must be specific enough to verify — "I can use the feature" is too vague
  • Number them (US-1, US-2, ...) so the plan can reference them

Project Customization

Read references/project.md in this skill's directory if it exists. It provides project-specific context:

  • User roles and their permissions
  • Path to a cross-cutting invariants document (if any)
  • Real-time transport preference (SSE, websockets, polling)
  • Any other project-specific patterns

© jvm-skills, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .junie/skills/interview of jvm-skills/jvm-skills.

Open the folder on GitHubat commit c6d477f

Compare with similar skills

Interview next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Interview compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Interview this skilljvm-skills/jvm-skills140—~804Automated safety check: PassApache-2.0
User Story Writerdeanpeters/Product-Manager-Skills7.2k2 repos~2.9kAutomated safety check: PassCustom licence
Ralph Tui Create Beadssubsy/ralph-tui2.5k1 repos~2.6kAutomated safety check: PassMIT
Agile Product Owneralirezarezvani/claude-skills28k3 repos~3.2kAutomated safety check: PassMIT
Ralph Tui Create Beads Rustsubsy/ralph-tui2.5k1 repos~2.8kAutomated safety check: PassMIT
To Specbestofjs/bestofjs3.1k22 repos~757Automated safety check: PassMIT

Similar skills

  • User Story Writer

    deanpeters/Product-Manager-Skills

    Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.

    7.2k GitHub starsUsed in 2 repos~2.9k tokens
    Product & Project ManagementAuto-check passed
  • Ralph Tui Create Beads

    subsy/ralph-tui

    Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.

    2.5k GitHub starsUsed in 1 repo~2.6k tokens
    Product & Project ManagementAuto-check passed
  • Agile Product Owner

    alirezarezvani/claude-skills

    Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.

    28k GitHub starsUsed in 3 repos~3.2k tokens
    Product & Project ManagementAuto-check passed
  • Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).

    2.5k GitHub starsUsed in 1 repo~2.8k tokens
    Product & Project ManagementAuto-check passed
  • To Spec

    bestofjs/bestofjs

    Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

    3.1k GitHub starsUsed in 22 repos~757 tokens
    Product & Project ManagementAuto-check passed
  • Ralph Tui Create JSON

    subsy/ralph-tui

    Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.

    2.5k GitHub starsUsed in 1 repo~2.6k tokens
    Product & Project ManagementAuto-check passed

More from jvm-skills/jvm-skills

All 16 skills in this repo
  • Mutation Testing

    jvm-skills/jvm-skills

    Bootstrap pitest via the info.solidsoft.pitest Gradle plugin with Kotlin-sane defaults, run mutation tests scoped to changed classes, interpret surviving mutants from mutations.xml, triage…

    140 GitHub stars~6.7k tokensUpdated 1 mo ago
    Auto-check passed
  • Ralph Coverage

    jvm-skills/jvm-skills

    Run Ralph in coverage mode — iteratively write tests for untested classes until coverage targets are met.

    140 GitHub stars~683 tokensUpdated 1 mo ago
    Auto-check passed
  • Skill Scout

    jvm-skills/jvm-skills

    Run the skill-scout loop — scan the next batch of unscanned JVM-conference rosters for speaker-created AI skills and apply results to the CSV store via the overnight Workflow.

    140 GitHub stars~727 tokensUpdated 1 mo ago
    Auto-check passed
  • Spec

    jvm-skills/jvm-skills

    Generate a feature spec with user stories directly from conversation context and codebase exploration — no interview needed.

    140 GitHub stars~832 tokensUpdated 1 mo ago
    Auto-check passed
  • UI Review

    jvm-skills/jvm-skills

    Verify UI/UX by running Playwright tests and reviewing screenshots.

    140 GitHub stars~545 tokensUpdated 1 mo ago
    Auto-check passed
  • Kotest

    jvm-skills/jvm-skills

    Write a new Kotlin test, or modernize an existing one, using Kotest matchers and idiomatic Kotlin test style — backticked names, apply/assertSoftly blocks, and existing object mothers and helpers.

    140 GitHub stars~2.6k tokensUpdated 1 mo ago
    Auto-check passed

Questions about Interview

What does Interview do?

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Interview is an agent skill from jvm-skills/jvm-skills. Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree.

When should I use Interview?

Interview fits situations like: tasks that involve User stories.

How do I install Interview in Claude Code?

Run `npx skills add jvm-skills/jvm-skills --skill interview -a claude-code`. Or copy the skill folder (.junie/skills/interview in jvm-skills/jvm-skills) into .claude/skills/interview in your project. Claude Code loads it when a task matches its description.

How do I install Interview in Codex?

Run `npx skills add jvm-skills/jvm-skills --skill interview -a codex`. Or copy the skill folder (.junie/skills/interview in jvm-skills/jvm-skills) into .agents/skills/interview in your project. Codex loads it when a task matches its description.

Can I use Interview in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jvm-skills/jvm-skills --skill interview -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/interview, .gemini/skills/interview, .github/skills/interview and .opencode/skills/interview in your project.

What does Interview need to run?

SKILL.md names no scripts, command-line tools or credentials: Interview is instructions for the agent only.

Does Interview access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Interview safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Interview use?

Interview is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Interview use?

About 804 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Interview?

Skills that share tags, products or a category with Interview: User Story Writer (deanpeters/Product-Manager-Skills, 7.2k stars), Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Agile Product Owner (alirezarezvani/claude-skills, 28k stars) and Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Interview?

jvm-skills (a GitHub organization) maintains it in jvm-skills/jvm-skills, which has 140 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on August 31, 2026.

Source: jvm-skills/jvm-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.