Skip to main content
affpapa.org
RU EN
skill CX Codex

plan-interview · pskoett — Claude Code skill: what it does, how to install

This skill interviews the user before feature planning or refactoring. It clarifies constraints, scope, risk, and acceptance criteria before code exploration.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add pskoett/pskoett-ai-skills --skill plan-interview -a claude-code
Open on GitHub

What plan-interview does

plan-interview starts with a requirements interview before the agent examines the repository. It covers technical constraints, scope limits, risk preferences, and the conditions that define a finished result. Questions are tailored to the task and arranged in small thematic groups.

Once the answers are collected, the skill guides repository exploration: relevant patterns, affected files, integration points, and structural friction. It also audits the source of knowledge behind each implementation step. When a required detail cannot be reached from the codebase, the conversation, or established technical knowledge, the agent is told to ask for it instead of guessing.

The workflow targets feature work, refactoring, and other non-trivial implementation tasks. Pure research and simple bug fixes are outside its intended use.

What it helps with

  • collect requirements before implementing a feature
  • draw a clear boundary around the MVP
  • surface acceptable tradeoffs and breaking changes
  • define completion and validation criteria
  • spot preparatory refactoring before the main change

Example prompts for the agent

  • Run /plan-interview for a new data import feature and interview me before exploring the repository.
  • Use /plan-interview before refactoring the authentication module; ask about constraints and acceptance criteria.
  • Start /plan-interview for this multi-file change, then build the plan around its risks and open questions.

How to install plan-interview

1Skills CLI (Vercel)

npx skills add pskoett/pskoett-ai-skills --skill plan-interview -a claude-code

2Manually: put the files in place

~/.claude/skills/plan-interview/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/plan-interview/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about plan-interview

How do I install plan-interview in Claude Code?

Run npx skills add pskoett/pskoett-ai-skills --skill plan-interview -a claude-code, then check ~/.claude/skills/plan-interview/SKILL.md.

What does plan-interview do?

It runs a structured requirements interview before implementation planning. The process clarifies constraints, scope, risk tolerance, and the definition of done.

When should I use plan-interview?

Use it for new features, refactoring, and other non-trivial implementation work. Pure exploration and simple bug fixes are outside its intended workflow.

Similar skills

All skills for Agent setup: memory, context, orchestration →

plan-interview by other authors comes first.

plan-interview secondsky Turns a rough plan into an implementation-ready spec through an adaptive interview. Useful when the idea exists but the requirements don't. CX Codex +1 395installs setup-matt-pocock-skills Matt Pocock This skill configures a repository for Matt Pocock's engineering skills by setting its issue tracker, triage labels, and domain docs layout. Run it before using the other skills. 1,052,851installs ask-matt Matt Pocock Routes you to the right Matt Pocock skill or flow for the task at hand. Use it when you need a starting point for a feature, prototype, incoming issue, or hard bug. 766,587installs to-tickets Matt Pocock Turns a plan, spec, or conversation into small end-to-end tickets with explicit blockers. Use it to agree on the work breakdown before tickets go to a tracker. 711,230installs writing-plans Jesse Vincent This skill turns requirements for a multi-step task into an implementation plan before code changes begin. It helps when another engineer needs exact files, interfaces, and checks. CX Codex 282,859installs caveman-review JuliusBrussee Turns code review comments into one line per finding: location, problem, fix. Useful when a diff or PR needs a fast pass without the filler. CX Codex +1 411,800installs caveman-compress JuliusBrussee Compresses CLAUDE.md, todo lists, and other prose files into a shorter format while retaining a readable backup. CX Codex +1 411,500installs

From the same set7

self-improvement Keeps your corrections, failed commands and feature asks in markdown files so the agent can turn repeated lessons into project rules. CX Codex +1 2,000installs self-improvement-ci A CI-only skill that groups recurring pull request check failures and proposes rules so the same breakage stops coming back. CX Codex +1 545installs simplify-and-harden A post-completion self-review pass: simplify, harden, re-verify and micro-document the code while the agent still remembers why it changed. CX Codex +1 535installs intent-framed-agent This skill writes down what a coding session is supposed to achieve before edits start, then watches for work that wanders off. Handy on long refactors and feature builds. CX Codex +1 435installs simplify-and-harden-ci A skill that reviews pull requests inside CI: it scans changed files, posts findings, and can stop a merge. CX Codex +1 389installs pskoett-ai-skills A pipeline of skills and subagents that puts checks into the agent's workflow: plan agreement, context control, code audit and saved lessons. ★ 323repo stars

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor