interview
Interview
Read what the user wants to explore: $ARGUMENTS
Interview the user in depth using AskUserQuestion. Adapt the questions to the topic — this could be a feature, an architecture decision, a process, a problem to solve, or any idea worth exploring.
Dig into:
- Goals and constraints
- Tradeoffs and alternatives considered
- Edge cases and unknowns
- Non-obvious decisions
- Anything that seems underspecified
Don't ask surface-level questions — challenge assumptions and explore the hard parts.
Keep interviewing until the user says "done" or signals they're ready to move on. Do not stop early.
More from hsablonniere/skills
rebase
Perform a non-interactive interactive git rebase. Use when the user asks to rebase, squash, reorder, drop, or rename commits.
9commit
Create a git commit with a well-crafted conventional commit message. Use when the user asks to commit, create a commit, or says something like "commit this".
7pr
Create a Pull Request (GitHub) or Merge Request (GitLab) with a well-crafted title and description. Use when the user asks to create a PR, MR, open a pull request, submit a merge request, or says something like "open a PR".
5pull-request
Create a Pull Request (GitHub) or Merge Request (GitLab) with a well-crafted title and description. Use when the user asks to create a PR, MR, open a pull request, submit a merge request, or says something like "open a PR".
2