From interview
Interviews users thoroughly to plan features or changes, probing requirements, architecture, UI/UX, constraints, tradeoffs, scope boundaries, and success criteria. Ideal for complex implementations.
How this skill is triggered — by the user, by Claude, or both
Slash command
/interview:planThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Interview the user comprehensively about their requested change using `AskUserQuestion`.
Interview the user comprehensively about their requested change using AskUserQuestion.
Cover these areas, adapting to context:
AskUserQuestion callThe interview informs the conversation. Do not write to files unless the user requests it.
npx claudepluginhub bendrucker/claude --plugin interviewConducts structured requirements-gathering interviews for software features/systems. Reads SPEC.md and context, asks numbered questions on purpose, technical design, UI/UX, edge cases, security, rollout. For deep requirement elicitation before specs/plans.
Interviews the user one question at a time to resolve ambiguity before implementation. Use when planning is done but unknowns remain, or when asked to be interviewed.
Runs a structured requirements interview before planning implementation to ensure alignment on technical constraints, scope, risk tolerance, and success criteria.