Skill

interview:plan

Interviews users thoroughly to plan features or changes, probing requirements, architecture, UI/UX, constraints, tradeoffs, scope boundaries, and success criteria. Ideal for complex implementations.

developer-tools

Install

npx claudepluginhub bendrucker/claude --plugin interview

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Interview the user comprehensively about their requested change using `AskUserQuestion`.

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

139.2k

mcp-builder

9 files

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

anthropics-skills-13

124.2k

canvas-design

20 files

Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.

anthropics-skills-13

124.2k

Stats

Parent Repo Stars10

Parent Repo Forks1

Last CommitFeb 8, 2026

Actions

View Source View Plugin View on GitHub View README

Planning Interview

Interview the user comprehensively about their requested change using AskUserQuestion.

Interview Topics

Cover these areas, adapting to context:

Requirements - What exactly should this do? What shouldn't it do?
Technical implementation - Architecture, data flow, dependencies, APIs
UI/UX - User interactions, feedback, error states, edge cases
Constraints - Performance, compatibility, security, accessibility
Tradeoffs - What are you willing to sacrifice? What's non-negotiable?
Scope boundaries - What's explicitly out of scope for this change?
Validation - How will we know it works? What does success look like?

Interview Style

Non-obvious questions - Skip questions with obvious answers
In-depth - Dig into specifics, follow interesting threads
Batch questions - Use up to 4 questions per AskUserQuestion call
Continue until complete - Keep interviewing until the plan feels solid
Challenge assumptions - Surface implicit decisions that deserve explicit consideration

Output

The interview informs the conversation. Do not write to files unless the user requests it.