Help us improve
Share bugs, ideas, or general feedback.
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.
npx claudepluginhub bendrucker/claude --plugin interviewHow 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`.
Conducts 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 users about a plan or PRD to surface ambiguities before coding. Asks one non-obvious question at a time until all gaps in requirements are resolved.
Runs structured interview to align on technical constraints, scope boundaries, risk tolerance, and success criteria before feature implementation, refactoring, or non-trivial tasks via /plan-interview.
Share bugs, ideas, or general feedback.
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.