How do I install the Plan Interview skill?

Run npx get-skill add tomevault-io/plan-interview in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Plan Interview safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Plan Interview?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Plan Interview free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Plan Interview?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Plan Interview by tomevault-io — Agent Skill

Name: Plan Interview
Author: tomevault-io

Plan Interview

Adaptive interview-driven spec generation. Use when converting rough plans into comprehensive specifications, needing structured requirements gathering, or transforming ideas into implementation-ready documentation. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

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:

Complexity	Signals	Questions
Simple	Single feature, clear scope	10-15
Moderate	Multi-component, some integrations	18-23
Complex	Cross-system, many stakeholders	22-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

Foundations & Scope - Stakeholders, success criteria, constraints, MVP scope
Technical Deep-Dive - Architecture, data models, scalability, security
User Experience - Personas, flows, cognitive load, error recovery
Risks & Tradeoffs - Risk categorization, blast radius, contingency plans
Operationalization - Testing, deployment, monitoring
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

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: plan-interviewdescription: Adaptive interview-driven spec generation. Use when converting rough plans into comprehensive specifications, needing structured requirements gathering, or transforming ideas into implementation-ready documentation. Use when this capability is needed.---# Plan Interview SkillTransform 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:| Complexity | Signals | Questions ||------------|---------|-----------|| **Simple** | Single feature, clear scope | 10-15 || **Moderate** | Multi-component, some integrations | 18-23 || **Complex** | Cross-system, many stakeholders | 22-28 |**Usage:**```bash/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 Phases1. **Foundations & Scope** - Stakeholders, success criteria, constraints, MVP scope2. **Technical Deep-Dive** - Architecture, data models, scalability, security3. **User Experience** - Personas, flows, cognitive load, error recovery4. **Risks & Tradeoffs** - Risk categorization, blast radius, contingency plans5. **Operationalization** - Testing, deployment, monitoring6. **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 StructureGenerated 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)## ReferencesLoad 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---> Converted and distributed by [TomeVault](https://tomevault.io/claim/secondsky) — claim your Tome and manage your conversions.

Frequently asked questions