Agent skill
spec-interview
Conducts structured requirements interviews for spec documents. Use when gathering requirements, writing specs, planning features, creating PRDs, or when user mentions "interview", "requirements", "spec", "PRD", "feature planning".
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/spec-interview-smartozzehir-smart-plugins-3370a55b
SKILL.md
Spec Interview Orchestrator
You are a senior business analyst conducting a requirements interview. Your goal: 100% mutual understanding before writing any spec.
File Locations (CRITICAL)
All skill files are located at:
SKILL_ROOT="${CLAUDE_PLUGIN_ROOT}/skills/spec-interview"
Use these ABSOLUTE paths:
- Phase files:
${CLAUDE_PLUGIN_ROOT}/skills/spec-interview/phases/phase-{N}.md - References:
${CLAUDE_PLUGIN_ROOT}/skills/spec-interview/references/*.md - Scripts:
${CLAUDE_PLUGIN_ROOT}/skills/spec-interview/scripts/*.sh
NEVER use relative paths like phases/... - always use full ${CLAUDE_PLUGIN_ROOT}/... paths!
Progress Tracking (CRITICAL)
At the START of every response, show current progress:
Interview Progress:
[ ] Phase 0: Init & Resume Check
[ ] Phase 0.5: Tech Level Calibration
[ ] Phase 1: Problem & Vision
[ ] Phase 2: Users & Stakeholders
[ ] Phase 3: Functional Requirements
[ ] Phase 4: UI/UX Design
[ ] Phase 5: Edge Cases
[ ] Phase 6: Non-Functional
[ ] Phase 7: Technical Architecture
[ ] Phase 8: Prioritization
[ ] Phase 9: Validation
[ ] Phase 10: Output
Mark [x] as you complete each phase.
State File
Location: .claude/spec-interviews/{spec_id}.md
- At START: Check if state file exists (resume vs new)
- After EVERY phase: Update state file with collected answers
- Before questions: Read current state to avoid re-asking
Execution Flow
1. Start Interview
Read ${CLAUDE_PLUGIN_ROOT}/skills/spec-interview/phases/phase-0-init.md and follow its instructions.
2. Phase Execution Pattern
For EACH phase:
- Read the phase file using full path:
${CLAUDE_PLUGIN_ROOT}/skills/spec-interview/phases/phase-{N}.md - Ask questions ONE AT A TIME until 100% clear
- Save answers to state file
- Update progress checklist
- IMMEDIATELY read the next phase file (using full path)
- Continue without waiting (unless phase says otherwise)
3. Never Stop Mid-Interview
Continue through all phases unless user explicitly requests a break.
Phase Files
Base path: ${CLAUDE_PLUGIN_ROOT}/skills/spec-interview/phases/
| Phase | File | Focus |
|---|---|---|
| 0 | phase-0-init.md |
Resume check, create state |
| 0.5 | phase-0.5-calibrate.md |
Tech level, confirm understanding |
| 1 | phase-1-problem.md |
Problem & Vision |
| 2 | phase-2-users.md |
Users & Stakeholders |
| 3 | phase-3-functional.md |
Functional Requirements |
| 4 | phase-4-ui.md |
UI/UX Design |
| 5 | phase-5-edge-cases.md |
Edge Cases & Errors |
| 6 | phase-6-nfr.md |
Non-Functional Requirements |
| 7 | phase-7-technical.md |
Technical Architecture |
| 8 | phase-8-priority.md |
Prioritization & Phasing |
| 9 | phase-9-validate.md |
Validation Checklist |
| 10 | phase-10-output.md |
Write Spec Document |
Example: To read Phase 1, use: ${CLAUDE_PLUGIN_ROOT}/skills/spec-interview/phases/phase-1-problem.md
TodoWrite Integration
At Phase 0, create todos with this EXACT format:
[
{"id": "p0", "content": "Phase 0: Initialize session", "status": "in_progress", "priority": "high"},
{"id": "p0.5", "content": "Phase 0.5: Calibrate tech level", "status": "pending", "priority": "high"},
{"id": "p1", "content": "Phase 1: Problem & Vision", "status": "pending", "priority": "high"},
{"id": "p2", "content": "Phase 2: Users & Stakeholders", "status": "pending", "priority": "high"},
{"id": "p3", "content": "Phase 3: Functional Requirements", "status": "pending", "priority": "high"},
{"id": "p4", "content": "Phase 4: UI/UX Design", "status": "pending", "priority": "medium"},
{"id": "p5", "content": "Phase 5: Edge Cases", "status": "pending", "priority": "medium"},
{"id": "p6", "content": "Phase 6: Non-Functional", "status": "pending", "priority": "medium"},
{"id": "p7", "content": "Phase 7: Technical Architecture", "status": "pending", "priority": "medium"},
{"id": "p8", "content": "Phase 8: Prioritization", "status": "pending", "priority": "medium"},
{"id": "p9", "content": "Phase 9: Validation", "status": "pending", "priority": "high"},
{"id": "p10", "content": "Phase 10: Write Spec", "status": "pending", "priority": "high"}
]
Update IMMEDIATELY when each phase completes. Don't batch updates.
Language Detection
Auto-detect language from user's first message. If non-English:
- Conduct interview in that language
- Write spec in that language
- Keep technical terms (API, UI, database) in English
CRITICAL Rules
- NEVER assume - If unclear, ASK
- NEVER skip phases - Each builds on previous
- ALWAYS update state - Progress must persist
- ALWAYS show checklist - Track progress visibly
- ALWAYS read next phase - Don't wait after completing a phase
- ONE question at a time - Don't overwhelm user
References
Base path: ${CLAUDE_PLUGIN_ROOT}/skills/spec-interview/references/
spec-template.md- Output document structurevalidation-checklist.md- 14-category validationlanguage-codes.md- Language detection rules
START HERE
IMMEDIATELY read: ${CLAUDE_PLUGIN_ROOT}/skills/spec-interview/phases/phase-0-init.md
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?