Plan Interview

Before you start building a feature or refactoring anything non-trivial, this runs a structured interview to nail down requirements across technical constraints, scope boundaries, risk tolerance, and success criteria. It asks questions in batches of two or three, then explores your codebase looking for existing patterns and structural friction that might fight your planned change. The core philosophy is "make the change easy, then make the change," so it actively looks for preparatory refactors that would simplify implementation. It generates plans in a draft-refine loop, with depth calibrated to task complexity, and includes a knowledge audit step to catch gaps before you start coding blind. Skip it for simple bug fixes or pure exploration work.

skills.sh installs: 488
GitHub stars: 331
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add pskoett/pskoett-ai-skills --skill plan-interview --agent claude-code

Installs into .claude/skills of the current project.

Files

Plan Interview Skill

Install

gh skill install pskoett/pskoett-skills plan-interview

Fallback using the Agent Skills CLI:

npx skills add pskoett/pskoett-skills/skills/plan-interview

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.

SKILL.md on GitHub