I built a skill that interviews me in-depth to create a detailed spec—not just for coding, but also if I want to build a bigger feature.

The Skill

---
name: interview-spec
description: Interview user in-depth to create a detailed spec. Use when user says "build a spec <arguments>" or "help me spec "<arguments>"
---

Use the `AskUser` or `AskUserQuestionTool` user tool for questions

Follow the user instructions and interview me in detail using the question tool 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. <instructions>$ARGUMENTS</instructions>

Usage

Trigger it with:

Help me spec building a hello world app

The agent then walks you through a wizard, asking about technical implementation details, UI/UX considerations, tradeoffs, and anything else relevant to the project. It keeps going until you’ve covered enough ground, then writes the spec to a file.

Why This is Useful

When I start a project, I often have a rough idea but haven’t thought through all the details. This skill forces me to articulate decisions I’d otherwise defer—the tech stack, error handling, edge cases, user flows. By the time the interview is done, I have a spec I can hand off to the agent (or myself) to implement.

It’s particularly helpful for larger features where jumping straight into code would mean constant backtracking.

A Note on Different Agents

In Claude Code and Droid, the interview runs as a wizard—one question at a time, with follow-ups based on your answers. In Codex, it asks all the questions at once and you fill in the answers in a single pass. Either way, you end up with the same spec.