Agent skill · pskoett
plan-interview
Ensures alignment between user and Claude during feature/spec planning through a structured interview process. Use this skill when the user invokes /plan-interview before implementing a new feature, refactoring, or any non-trivial implementation task. The skill runs an upfront interview to gather requirements across technical constraints, scope boundaries, risk tolerance, and success criteria before any codebase exploration. Do NOT use this skill for: pure research/exploration tasks, simple bug fixes, or when the user just wants standard planning without the interview process.
What it needs
About 8k tokens when loaded.
What this skill does
Plan Interview Skill Install Fallback using the Agent Skills CLI: Philosophy Every skill in this collection is built around a core philosophy — a principle that agents struggle to internalize on their own. This skill's philosophy: "Make the change easy, then make the change." Agents default to plowing straight through implementation, no matter how tangled the path. They rarely pause to ask: "Would a preparatory refactor make this change simple instead of hard?" Planning is where that question gets asked. During codebase exploration and plan generation, actively look for structural friction — code that makes the target change awkward, brittle, or overly complex. When you find it, the plan should propose a preparatory step: make the change easy first, then make the change itself. Two clean steps beat one heroic slog. Purpose Run a structured requirements interview before planning implementation. This ensures alignment between you and the user by gathering explicit requirements rather than making assumptions. When Invoked User calls /plan-interview <task description>. Skip this skill if the task is purely research/exploration (not implementation). Interview Process Phase 1: Upfront Interview (Before Exploration) Check for the host's structured question tool (askuser, AskUserQuestion, or an equivalent). Use it for focused questions that the user can answer before the next planning step. In hosts without a structured question tool, ask the same question directly in chat and pause for the response. Do not fall back to plain chat merely because the host uses a different tool name. Respect the host schema: if the tool accepts only one question per call, ask the domains sequentially rather than bundling them. Required Question Domains Cover ALL four domains before proceeding: 1. Technical Constraints Performance requirements Compatibility needs Existing patterns to follow Architecture understanding (if codebase is unfamiliar) 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills pskoett/plan-interview--449e25