mcpField
I
interview

interview

github.com/enzedDevelopment1044 installsUpdated 7w ago
Repository

About interview

interview is a specification-writing skill for developers planning changes to an existing codebase. It first explores the implementation, then conducts a detailed requirements interview and writes a specification.

Key features

  1. 01Parallel codebase exploration
  2. 02Exhaustive system and file summary
  3. 03Informed requirements interview
  4. 04Specification written to a file

Use cases

  1. 01Understanding an existing feature before changing it
  2. 02Gathering implementation and UX requirements
  3. 03Documenting an agreed software specification

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/enzed/skills --skill interview

After installing, type/interviewin Claude Code to confirm it loaded.

Details

From the project README

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.

$ARGUMENTS

Comments

Markdown supported