Interview
- 41 installs
- 9 repo stars
- Updated March 17, 2026
- enzed/skills
Create detailed specs by asking probing questions about requirements and product details.
About
Interview skill guides structured discovery of requirements through targeted questions about technical implementation, UI/UX, concerns, and design tradeoffs. Use during requirements gathering and feature specification.
- Probing questions for requirement discovery.
- Guides technical and UX tradeoff analysis.
Interview by the numbers
- 41 all-time installs (skills.sh)
- Ranked #1,717 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Jul 25, 2026 (Skillselion catalog sync)
npx skills add https://github.com/enzed/skills --skill interviewAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 41 |
|---|---|
| repo stars | ★ 9 |
| Last updated | March 17, 2026 |
| Repository | enzed/skills ↗ |
What it does
Create detailed specs by asking probing questions about requirements and product details.
Files
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>
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493k