interview
Interview user in-depth to create a detailed spec. Use when user wants to define requirements, spec out a feature, or needs help articulating product details.
- Installs
- 44
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/enzed/skills --skill interview- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads interview automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Interview for Specification
Phase 1: Exploration
Before asking any questions, use the Task tool with subagent_type=Explore to do a deep-dive on the codebase and understand how the topic in the instructions works. Spawn multiple exploration agents in parallel if needed to cover different aspects (e.g., data flow, UI components, state management, related systems).
Once the exploration is complete, present a full exhaustive summary to the user covering:
- How the feature/system currently works
- Key files and their responsibilities
- Data flow and state management
- Dependencies and integrations with other systems
- Any existing patterns or conventions used
Phase 2: Interview
After presenting the summary, interview me in detail using the AskUserQuestion tool about literally anything: technical implementation, UI & UX, concerns, tradeoffs, etc. but make sure the questions are not obvious. Leverage your exploration findings to ask informed, specific questions rather than generic ones. Be very in-depth and continue interviewing me continually until it's complete.
Phase 3: Specification
Once the interview is complete, write the spec to a file.
<instructions>$ARGUMENTS</instructions>
FAQ
What does the interview skill do?
Interview user in-depth to create a detailed spec. Use when user wants to define requirements, spec out a feature, or needs help articulating product details.
How do I install interview?
Run npx skills add https://github.com/enzed/skills --skill interview in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/interview/ (personal) or .claude/skills/interview/ (project).
Which AI agents can use interview?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is interview safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains interview?
It is published by enzed in enzed/skills. It has 44 recorded installs.
More from enzed/skills
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.