plan-interview
/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.
- Author
- secondsky ↗
- Repository
- claude-skills ↗
- Licence
- MIT
- Last repository change
- 26.09.2026
Assessment and security
- Files in this package
- 7
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Adaptive interview-driven spec generation. Use when converting rough plans into comprehensive specifications, needing structured requirements gathering, or transforming ideas into implementation-ready documentation.
Original author description
Adaptive interview-driven spec generation. Use when converting rough plans into comprehensive specifications, needing structured requirements gathering, or transforming ideas into implementation-ready documentation.
How it works
- When to Use
- Available Components
- Interview Phases
- Interview Philosophy
- Spec Output Structure
- References
SKILL.md preview
--- name: plan-interview description: Adaptive interview-driven spec generation. Use when converting rough plans into comprehensive specifications, needing structured requirements gathering, or transforming ideas into implementation-ready documentation. license: MIT --- # 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:** ```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 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
Files in this package (7)
- SKILL.md 3 KB
- references/example-spec.md 11 KB
- references/interview-techniques.md 6 KB
- references/phase-1-clarifications.md 5 KB
- references/phase-2-technical.md 5 KB
- references/phase-3-ux.md 5 KB
- references/phase-4-risks.md 6 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · secondsky/claude-skills | 100 | MIT |
| pskoett/measuring-ai-proficiency | 100 | MIT |
| pskoett/measuring-ai-proficiency | 100 | MIT |
Database snapshot: 13.11.2026 · package version 66174deb9725 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100interview-me
Conduct an adaptive interactive interview on any topic and produce a structured markdown report, summary, or implementation plan. Use when the user says "interview me", "interview me about", "run an interview on", "help me think through", or wants guided discovery on any… - 90interview
Conduct a structured interview about a feature or topic to gather requirements and produce a specification. This skill should be used when users want to think through a feature, clarify requirements, or create an implementation plan before coding. - 95create-spec
Create a new specification through an adaptive interview process with proactive recommendations and optional research. Use when user says "create spec", "new spec", "generate spec", or wants to start a specification document. - 100ralph-plan
Structured PRD generation with interview, research, and approval workflow. Triggers on: '/ralph-plan <topic>', 'create prd', 'generate prd', 'plan this'. Creates comprehensive Product Requirements Document via interview and research. - 85spec-interview
Refine a rough SPEC.md into an implementation-ready specification through a multi-round interview, then break it into ordered tasks. Use when starting a new feature or turning a rough idea into something a developer can build without asking questions. - 100requirements-interview
Conduct deep multi-round requirements interviews to produce executable SPEC, PRD, and PLAN drafts. Use when user says "clarify requirements", "采访需求", "extract requirements", "define scope", "analyze needs", or when requirements are ambiguous and need interactive clarification.…