Proactive requirements gathering through structured user interview
Conducts structured interviews to gather requirements before implementation begins.
/plugin marketplace add lerianstudio/ring/plugin install ring-default@ring[topic]Surface ambiguities and gather requirements BEFORE implementation begins. This command inverts the typical flow: instead of you anticipating what Claude might misunderstand, Claude proactively interviews you to build a complete picture.
/interview-me [topic]
| Argument | Required | Description |
|---|---|---|
topic | No | The feature, task, or area to gather requirements for. If omitted, Claude analyzes current context. |
/interview-me user notifications
Claude interviews you about notification types, delivery channels, preferences, etc.
/interview-me
Claude analyzes the current conversation and surfaces its uncertainties.
/interview-me database migration strategy
Claude gathers constraints, timelines, compatibility requirements, etc.
After the interview, Claude presents:
## Validated Understanding
### What We're Building
[1-2 sentence summary]
### Key Decisions Made
| Decision | Choice | Rationale |
|----------|--------|-----------|
### Constraints Confirmed
- [List of constraints]
### Out of Scope (Explicit)
- [Things we're NOT doing]
You must explicitly confirm this before Claude proceeds.
| Scenario | Use /interview-me? |
|---|---|
| Starting a new feature with vague requirements | ✅ Yes |
| Claude made wrong assumptions previously | ✅ Yes |
| Multiple valid approaches, unclear which to pick | ✅ Yes |
| Architecture decisions without clear direction | ✅ Yes |
| Simple bug fix with clear reproduction | ❌ No |
| Following an existing detailed plan | ❌ No |
| Single clarifying question needed | ❌ No (just ask) |
| Command/Skill | Relationship |
|---|---|
doubt-triggered-questions pattern | For single questions during work |
/brainstorm | Use AFTER interview to explore solutions |
/write-plan | Use AFTER interview to create implementation plan |
Claude should explore the codebase before asking. If you're being bombarded with questions, tell Claude to "explore first, then ask only what you can't figure out."
Good questions have 2-4 concrete options with descriptions. If you're getting open-ended questions, ask Claude to "provide specific options."
Remind Claude to re-read the conversation. The interview should build on what's already known, not repeat it.
Say "use your judgment" or "pick whatever fits best." Claude will make a choice and document the assumption.
This command MUST load the skill for complete workflow execution.
Use Skill tool: interviewing-user
The skill contains the complete workflow with: