plan-interview

Gather software requirements through structured interviews before implementation.

273|45|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/pskoett/pskoett-ai-skills --skill plan-interview-pskoett
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-interview
Source: https://github.com/pskoett/pskoett-ai-skills/tree/main/skills/plan-interview
Command: npx skills add https://github.com/pskoett/pskoett-ai-skills --skill plan-interview-pskoett

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents building the wrong thing by ensuring clear requirements and alignment between the user and the AI before any implementation begins.

Core Features & Use Cases

  • Structured Requirements Gathering: Conducts a deep-dive interview covering technical constraints, scope, risks, and success criteria.
  • Dynamic Plan Generation: Creates detailed, actionable plans tailored to task complexity.
  • Use Case: Before starting a complex feature like implementing a new payment gateway, use /plan-interview to ensure all security, integration, and user experience requirements are explicitly defined and agreed upon.

Quick Start

Use the plan-interview skill to plan the implementation of the new user profile page.

Frequently Asked Questions about plan-interview

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why gather requirements before code generation in software development?

Structured requirements gathering interviews define technical constraints, scope boundaries, risk tolerance, and success criteria to generate actionable plans before any software development or code generation implementation begins.

How do I plan complex software features like a new payment gateway?

Facilitate a structured interview to define technical constraints, scope boundaries, and success criteria for complex features like a payment gateway, generating a dynamic, actionable plan tailored to the specific task complexity.

Can I handle edge cases and refine plans for high-risk software projects?

Handle edge cases for high-risk projects by leveraging the structured interview's iterative refinement capabilities, continuously adjusting technical constraints and scope boundaries to manage evolving risk tolerance and success criteria.

What's the best way to define scope boundaries and success criteria before implementation?

Conduct a deep-dive interview to establish explicit alignment on scope boundaries, risk tolerance, and success criteria, ensuring all parties agree on technical constraints before any software development implementation starts.

Does this requirements gathering approach work for iterative software development?

This requirements gathering approach works for iterative software development by supporting iterative refinement, allowing progressive definition and adjustment of technical constraints, scope boundaries, and success criteria throughout the project lifecycle.