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 pitfallsreferences/phase-2-technical.md - Architecture discussion patternsreferences/phase-3-ux.md - Persona development, UX patternsreferences/phase-4-risks.md - Risk assessment frameworksreferences/interview-techniques.md - Cross-cutting interview skillsreferences/example-spec.md - Annotated high-quality spec example
1---2name: plan-interview3description: Adaptive interview-driven spec generation. Use when converting rough plans into comprehensive specifications, needing structured requirements gathering, or transforming ideas into implementation-ready documentation.4license: MIT5---67# Plan Interview Skill89Transform rough plans into comprehensive, implementation-ready specifications through adaptive, structured interviews.1011## When to Use1213- Converting a plan or idea into a detailed specification14- Gathering requirements through structured questioning15- Transforming rough documentation into implementation-ready specs16- Ensuring all edge cases, risks, and stakeholders are considered before implementation1718## Available Components1920### Command: `/plan-interview:interview [plan-file]`2122Adaptive interview that calibrates depth based on plan complexity:2324| Complexity | Signals | Questions |25|------------|---------|-----------|26| **Simple** | Single feature, clear scope | 10-15 |27| **Moderate** | Multi-component, some integrations | 18-23 |28| **Complex** | Cross-system, many stakeholders | 22-28 |2930**Usage:**31```bash32/plan-interview:interview docs/feature-plan.md33# Output: docs/feature-plan-spec.md34```3536### Agent: `spec-reviewer`3738Autonomous quality analysis of specifications across 4 dimensions:39- **Completeness** (25 pts) - All sections populated?40- **Consistency** (25 pts) - No contradictions?41- **Clarity** (25 pts) - No ambiguous language?42- **Edge Cases** (25 pts) - Error handling defined?4344Triggers when you say "review my spec" or "check specification quality".4546## Interview Phases47481. **Foundations & Scope** - Stakeholders, success criteria, constraints, MVP scope492. **Technical Deep-Dive** - Architecture, data models, scalability, security503. **User Experience** - Personas, flows, cognitive load, error recovery514. **Risks & Tradeoffs** - Risk categorization, blast radius, contingency plans525. **Operationalization** - Testing, deployment, monitoring536. **Wrap-Up** (optional) - Only for complex plans with remaining gaps5455## Interview Philosophy5657**Core Principle**: Depth over breadth. Better to deeply understand critical aspects than superficially cover everything.5859**Key Techniques**:60- Non-obvious questions - Skip what the plan already answers61- Edge probing - What happens in unusual cases?62- Assumption surfacing - Make implicit beliefs explicit63- Contradiction detection - Flag when answers don't align64- Adaptive depth - Probe deeper on complex areas, move faster on clear ones6566## Spec Output Structure6768Generated specs include:69- Overview (problem, solution, success criteria, stakeholders)70- Functional and non-functional requirements71- Technical design (architecture, data models, APIs, security)72- User experience (personas, flows, states, edge cases)73- Risks and mitigations (risk register, tradeoffs, contingency plans)74- Implementation notes (key decisions, dependencies, migration)75- Operationalization (testing, deployment, monitoring)76- Open questions and out-of-scope items77- Phasing (MVP vs future)7879## References8081Load these for deeper guidance during interviews:82- `references/phase-1-clarifications.md` - Foundations questions and pitfalls83- `references/phase-2-technical.md` - Architecture discussion patterns84- `references/phase-3-ux.md` - Persona development, UX patterns85- `references/phase-4-risks.md` - Risk assessment frameworks86- `references/interview-techniques.md` - Cross-cutting interview skills87- `references/example-spec.md` - Annotated high-quality spec example
secondsky