About interview
interview is a skill that conducts an in-depth interview about a project and writes the resulting specification to a Markdown file in the project's `.plans/` directory. It covers implementation, UI/UX, concerns, and tradeoffs.
Key features
- 01Interview across project topics
- 02Ask detailed, non-obvious questions
- 03Continue until the interview is complete
- 04Write a specification to Markdown
- 05Save the file in the project `.plans/` directory
Use cases
- 01Gather requirements for a feature
- 02Explore implementation tradeoffs
- 03Document UI/UX decisions
- 04Create a project specification
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ 23jmo/ jmo-skills --skill interviewAfter installing, type/interviewin Claude Code to confirm it loaded.
Details
From the project READMEFollow the user instructions and interview me in detail using the AskUserQuestionTool about literally anything: technical implementation, UI & UX, concerns, tradeoffs, etc. but make sure the questions are not obvious. be very in-depth and continue interviewing me continually until it's complete. then, write the spec to a file.
Save location: <cwd>/.plans/<relevant-name>.md
<cwd>= the current working directory — the project you are actually working in. Specs live with the code they describe so they are easy to find, open in an editor, and commit alongside the work.<relevant-name>= a short kebab-case slug describing the spec topic, ending in-spec.md(e.g.friends-tab-redesign-spec.md).- Create the
.plans/directory if it does not exist — the Write tool creates parent directories automatically. - Always resolve and write the absolute path, and state the path you wrote to in your reply.
- Do not save specs under
~/.claude/— they become impossible to find there.
$ARGUMENTS
Comments
Markdown supported