Agent skill

Interview

by kv0906 in kv0906/pm-kit

Interview user about a spec file and write detailed requirements.

MITAuto-check passedAgent Workflows

Install Interview

skills CLI
$ npx skills add kv0906/pm-kit --skill interview -a claude-code

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

GitHub CLI
$ gh skill install kv0906/pm-kit 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/kv0906/pm-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/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
138
Token cost
~571 tokens
SKILL.md length
252 words
Files
1
Skills in repo
26
Repo updated
First seen
Licence
MIT

At a glance

Interview user about a spec file and write detailed requirements.

  • Works in 5 steps: Ask ONE focused question at a time → Wait for the user's response before… → Avoid obvious questions — dig into… → …
  • User asks to interview me about this spec
  • SKILL.md covers Input, Interview Process, Rules and Pipeline, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Interview is an agent skill from kv0906/pm-kit. Interview user about a spec file and write detailed requirements. Use when user asks to "interview me about this spec", "brainstorm this PRD", "review spec with questions", or wants structured requirements gathering for a document.

Its SKILL.md is about 570 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 Agent Workflows, covering Requirements gathering, Brainstorming and PRD writing. The repository describes itself as: AI-augmented PM workspace for Coding Agents — daily standups, decisions, blockers, docs, and sprint reviews as markdown skills. The licence is MIT.

When your agent uses it

  • User asks to interview me about this spec
  • Brainstorm this PRD
  • Review spec with questions
  • Wants structured requirements gathering for a document

Example prompts

  • “interview me about this spec”
  • “brainstorm this PRD”
  • “review spec with questions”
  • “/interview”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Ask ONE focused question at a time
  2. Wait for the user's response before asking the next question
  3. Avoid obvious questions — dig into specifics and edge cases
  4. Challenge assumptions and explore alternatives
  5. Take notes on key decisions and rationale throughout

What it can do on your machine

Read from SKILL.md and the folder at commit 2cb5d9f. 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.

    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 571 tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 252 words of instructions outside code blocks.

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

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 kv0906/pm-kit at commit 2cb5d9f, republished under its MIT licence (© kv0906). 252 words, ~571 tokens.

Download SKILL.mdSave it as .claude/skills/interview/SKILL.md (or your agent's skills folder).
name
interview
description
Interview user about a spec file and write detailed requirements. Use when user asks to "interview me about this spec", "brainstorm this PRD", "review spec with questions", or wants structured requirements gathering for a document.

Interview - Spec Brainstorming

You are an interviewer who conducts in-depth, structured interviews about spec files to surface hidden requirements, edge cases, and design decisions.

Think step by step. Before asking any questions, first analyze the spec thoroughly.

Input

The user will provide a path to a spec file. Read it fully before beginning.

Interview Process

Conduct an in-depth interview about the spec. Ask non-obvious, probing questions across these dimensions:

Technical Implementation
  • Architecture decisions and tradeoffs
  • Edge cases and failure modes
  • Performance implications
  • Security considerations
  • Integration points with existing systems
UI/UX
  • User mental models and expectations
  • Accessibility requirements
  • Error states and recovery flows
  • Progressive disclosure needs
Business & Product
  • Success metrics and validation criteria
  • Phased rollout considerations
  • Backwards compatibility requirements
Constraints & Tradeoffs
  • Time vs quality tradeoffs
  • Build vs buy decisions
  • Technical debt implications

Rules

  1. Ask ONE focused question at a time
  2. Wait for the user's response before asking the next question
  3. Avoid obvious questions — dig into specifics and edge cases
  4. Challenge assumptions and explore alternatives
  5. Take notes on key decisions and rationale throughout

Pipeline

READ SPEC → ANALYZE → INTERVIEW (one question at a time) → SUMMARIZE → WRITE BACK
PhaseAction
1. ReadRead the spec file the user provides
2. AnalyzeIdentify gaps, ambiguities, and areas needing depth
3. InterviewAsk probing questions one at a time, wait for answers
4. SummarizeCompile all decisions and requirements
5. WriteUpdate the spec file with finalized requirements

Completion

After the interview is complete:

  1. Summarize all decisions and requirements discovered during the interview
  2. Write the finalized, enriched spec back to the original file

© kv0906, MIT. 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 .claude/skills/interview of kv0906/pm-kit.

Open the folder on GitHubat commit 2cb5d9f

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 skillkv0906/pm-kit138—~571Automated safety check: PassMIT
CE BrainstormEveryInc/compound-engineering-plugin25k—~1.9kAutomated safety check: PassMIT
Foreman Grill DocsVisionForge-OU/foreman443—~1.6kAutomated safety check: PassCustom licence
Feature BrainstormVeryGoodOpenSource/vgv-wingspan109—~1.8kAutomated safety check: PassMIT
Product Managerstaruhub/ClaudeSkills727—~2.1kAutomated safety check: PassMIT
Daily Life Discoverymagnus919/agent-skills113—~2.5kAutomated safety check: PassMIT

Similar skills

  • CE Brainstorm

    EveryInc/compound-engineering-plugin

    Turns a vague or ambitious feature idea into a requirements-only plan through dialogue with you, sized to the work, before any code is written.

    25k GitHub stars~1.9k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Foreman Grill Docs

    VisionForge-OU/foreman

    Headless grilling pass that challenges an approved implementation plan against the existing codebase and domain model, then writes an ADR draft and a PRD draft into the Foreman feature directory.

    443 GitHub stars~1.6k tokensUpdated 3 mo ago
    Agent WorkflowsAuto-check passed
  • Feature Brainstorm

    VeryGoodOpenSource/vgv-wingspan

    Clarifies what to build before how, by asking one question at a time about a feature idea and then handing the result on to planning.

    109 GitHub stars~1.8k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Product Manager

    staruhub/ClaudeSkills

    资深产品经理助手,提供 PRD/MRD/BRD 创作与评审、产品策略、留存增长、竞品分析、功能优先级,以及 grill-me-to-doc 逐轮访谈。用户要求“逐个问我”“先把需求问清楚”“grill me”“把想法变成产品文档”时进入 grill-me-to-doc:先读仓库证据,每轮只问一个决策,给推荐答案与理由,记录决策和未决项,支持 resume,产出结构化…

    727 GitHub stars~2.1k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed
  • Daily Life Discovery

    magnus919/agent-skills

    Guide a consent-based conversation that helps a person discover how an AI agent could improve their day-to-day life: routines, friction, attention, decisions, relationships, learning, and small…

    113 GitHub stars~2.5k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Trellis Brainstorm

    anjiemo/SunnyBeach

    Guides collaborative requirements discovery before implementation.

    178 GitHub starsUsed in 7 repos~4k tokens
    Product & Project ManagementAuto-check passed

More from kv0906/pm-kit

All 26 skills in this repo
  • Mermaid Visualizer

    kv0906/pm-kit

    Transform text content into professional Mermaid diagrams for presentations and documentation.

    138 GitHub starsUsed in 2 repos~2.2k tokens
    Auto-check passed
  • Gws

    kv0906/pm-kit

    This skill should be used when the user asks to "set up gws", "install Google Workspace CLI", "connect Gmail to Claude", "manage Google Drive from terminal", "send email from CLI", "check my…

    138 GitHub stars~1.6k tokensUpdated 3 mo ago
    Auto-check passed
  • Jira

    kv0906/pm-kit

    Jira integration via acli CLI. An agent skill from kv0906/pm-kit.

    138 GitHub stars~4.2k tokensUpdated 3 mo ago
    Auto-check: notes
  • Professional Excalidraw diagram generation expert that creates complete, valid .excalidraw.json files based on user descriptions.

    138 GitHub stars~3k tokensUpdated 3 mo ago
    Auto-check passed
  • Ask

    kv0906/pm-kit

    Fast vault Q&A — quick lookups, decision history, blocker status, doc search.

    138 GitHub stars~781 tokensUpdated 3 mo ago
    Auto-check passed
  • Block

    kv0906/pm-kit

    Flag a blocker with severity, owner, and due date. An agent skill from kv0906/pm-kit.

    138 GitHub stars~466 tokensUpdated 3 mo ago
    Auto-check: notes

Questions about Interview

What does Interview do?

Interview user about a spec file and write detailed requirements. Interview is an agent skill from kv0906/pm-kit. Interview user about a spec file and write detailed requirements.

When should I use Interview?

Interview fits situations like: user asks to interview me about this spec; brainstorm this PRD; review spec with questions; wants structured requirements gathering for a document.

How do I install Interview in Claude Code?

Run `npx skills add kv0906/pm-kit --skill interview -a claude-code`. Or copy the skill folder (.claude/skills/interview in kv0906/pm-kit) 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 kv0906/pm-kit --skill interview -a codex`. Or copy the skill folder (.claude/skills/interview in kv0906/pm-kit) 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 kv0906/pm-kit --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 MIT 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 571 tokens (SKILL.md is roughly 2.3k 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: CE Brainstorm (EveryInc/compound-engineering-plugin, 25k stars), Foreman Grill Docs (VisionForge-OU/foreman, 443 stars), Feature Brainstorm (VeryGoodOpenSource/vgv-wingspan, 109 stars) and Product Manager (staruhub/ClaudeSkills, 727 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Interview?

kv0906 (a GitHub user) maintains it in kv0906/pm-kit, which has 138 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on June 29, 2026.

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