mcpField
P
plan-interview

plan-interview

github.com/secondskyDevelopment240400 installsUpdated 5w ago
Repository

About plan-interview

Plan Interview is a skill for turning rough plans and ideas into implementation-ready specifications through adaptive interviews. It adjusts question depth to plan complexity and includes an agent that reviews specifications for completeness, consistency, clarity, and edge cases.

Key features

  1. 01Adaptive interviews based on plan complexity
  2. 02Structured questions across six phases
  3. 03Specification generation with implementation details
  4. 04Automated review across four quality dimensions

Use cases

  1. 01Expand a feature idea into a detailed specification
  2. 02Surface requirements and assumptions before implementation
  3. 03Review a specification for contradictions and gaps
  4. 04Assess risks, edge cases, and operational needs

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/secondsky/claude-skills --skill plan-interview

After installing, type/plan-interviewin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
example-spec.md
interview-techniques.md
phase-1-clarifications.md
phase-2-technical.md
phase-3-ux.md
phase-4-risks.md

Details

From the project README

Plan Interview Skill

Transform rough plans into comprehensive, implementation-ready specifications through adaptive, structured interviews.

When to Use

  • Converting a plan or idea into a detailed specification
  • Gathering requirements through structured questioning
  • Transforming rough documentation into implementation-ready specs
  • Ensuring all edge cases, risks, and stakeholders are considered before implementation

Available Components

Command: /plan-interview:interview [plan-file]

Adaptive interview that calibrates depth based on plan complexity:

ComplexitySignalsQuestions
SimpleSingle feature, clear scope10-15
ModerateMulti-component, some integrations18-23
ComplexCross-system, many stakeholders22-28

Usage:

/plan-interview:interview docs/feature-plan.md
# Output: docs/feature-plan-spec.md
Agent: spec-reviewer

Autonomous quality analysis of specifications across 4 dimensions:

  • Completeness (25 pts) - All sections populated?
  • Consistency (25 pts) - No contradictions?
  • Clarity (25 pts) - No ambiguous language?
  • Edge Cases (25 pts) - Error handling defined?

Triggers when you say "review my spec" or "check specification quality".

Interview Phases

  1. Foundations & Scope - Stakeholders, success criteria, constraints, MVP scope
  2. Technical Deep-Dive - Architecture, data models, scalability, security
  3. User Experience - Personas, flows, cognitive load, error recovery
  4. Risks & Tradeoffs - Risk categorization, blast radius, contingency plans
  5. Operationalization - Testing, deployment, monitoring
  6. Wrap-Up (optional) - Only for complex plans with remaining gaps

Interview Philosophy

Core Principle: Depth over breadth. Better to deeply understand critical aspects than superficially cover everything.

Key Techniques:

  • Non-obvious questions - Skip what the plan already answers
  • Edge probing - What happens in unusual cases?
  • Assumption surfacing - Make implicit beliefs explicit
  • Contradiction detection - Flag when answers don't align
  • Adaptive depth - Probe deeper on complex areas, move faster on clear ones

Spec Output Structure

Generated specs include:

  • Overview (problem, solution, success criteria, stakeholders)
  • Functional and non-functional requirements
  • Technical design (architecture, data models, APIs, security)
  • User experience (personas, flows, states, edge cases)
  • Risks and mitigations (risk register, tradeoffs, contingency plans)
  • Implementation notes (key decisions, dependencies, migration)
  • Operationalization (testing, deployment, monitoring)
  • Open questions and out-of-scope items
  • Phasing (MVP vs future)

References

Load these for deeper guidance during interviews:

  • references/phase-1-clarifications.md - Foundations questions and pitfalls
  • references/phase-2-technical.md - Architecture discussion patterns
  • references/phase-3-ux.md - Persona development, UX patterns
  • references/phase-4-risks.md - Risk assessment frameworks
  • references/interview-techniques.md - Cross-cutting interview skills
  • references/example-spec.md - Annotated high-quality spec example

Comments

Markdown supported