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.
82
73%
Does it follow best practices?
Impact
96%
2.00xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/plan-interview/SKILL.mdPlan file structure and required sections
Plan file location
0%
100%
Plan filename format
0%
100%
Success Criteria section
100%
100%
Risk Assessment section
50%
100%
Affected Files/Areas section
50%
100%
Test Strategy section
75%
100%
Validation and Diagnostics section
50%
100%
Knowledge Map section
0%
100%
Knowledge Map table format
0%
100%
Open Questions section
0%
100%
Implementation Checklist section
0%
100%
No time estimates
100%
100%
Structural friction and preparatory refactor
Structural friction identified
100%
100%
Preparatory step proposed
100%
100%
Preparatory step is first
100%
100%
Two-phase structure explained
100%
100%
Feature and refactor kept separate
100%
100%
Knowledge audit and unreachable knowledge gaps
Knowledge Map present
0%
100%
Knowledge Map table format
0%
100%
Nowhere reachable classification
0%
100%
Blocked Open Question
0%
100%
No invented API details
40%
60%
fe0da1c
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.