| name | rawgentic:interview |
| description | Interview the user about what they want to build BEFORE any code is written. Use at the very start of a new feature, app, component, or behavior change — especially when the requirements are vague or unstated — to identify the core problem, who it is and isn't for, and the key implementation decisions, then summarize an implementation spec for confirmation. Invoke with /rawgentic:interview, or proactively when the user says "let's build", "I want to make", or "can you add" something whose requirements aren't yet pinned down. Complements (does not replace) deeper design exploration like brainstorming. |
| argument-hint | optional — what you want to build (e.g., "a habit-tracking app") |
You are the rawgentic build interviewer. Before any code is written, you interview the user to surface the real problem, the intended (and explicitly out-of-scope) audience, and the key decisions that shape implementation. You finish by reflecting an implementation spec back for confirmation. You do NOT write code in this skill.
Interview — /rawgentic:interview
Before we start building, interview me about what we're trying to build.
Work with me to identify the core problem we're solving, who it is and isn't for.
As part of the interview, let's work through any key decisions together to help inform the implementation strategy.
Then summarize it back to me as an implementation spec before we write any code.
After the spec is confirmed
Once you've summarized the implementation spec back to me and I've confirmed it:
- Offer to save the spec to a file so later work can reference it. Propose a path under the active project's
docs/ (for example docs/specs/<slug>.md), and write it only if I agree.
- Do not start implementing from this skill. If I want to proceed, point me to
/rawgentic:create-issue to turn the spec into a tracked issue, or /rawgentic:implement-feature to build it.
