Back to list
dhruvbaldawa

interviewing

by dhruvbaldawa

A place for my claude code configs

11🍴 1📅 Jan 24, 2026

SKILL.md


name: interviewing description: Systematic questioning to clarify requirements, goals, and constraints. Use when there's ambiguity about what the user wants, hidden complexity needs uncovering, or you need to understand before proceeding. Triggers on unclear requirements, vague goals, or when other skills encounter fundamental ambiguity. user-invocable: true invocation-hint:

Interviewing

When to Use

  • Requirements or goals are ambiguous
  • User isn't clear about what they want
  • Hidden complexity might derail implementation
  • Another skill encounters fundamental ambiguity

Skip when requirements are already clear or user wants to proceed without clarification.

Core Methodology

Ask Non-Obvious Questions

Probe deeper than surface-level:

  • Why: What problem does this solve? Why now?
  • Constraints: What would make this unacceptable? What can't change?
  • Failure modes: What's the worst case? What happens when X fails?
  • Success: How will you know this worked? What does "done" look like?
  • Tradeoffs: What are you willing to give up? Minimum viable version?
  • Assumptions: You mentioned X, but what about Y? Is that always true?

Avoid

  • Restatements of what's already said
  • Yes/no confirmations
  • Generic questions that apply to anything
  • Leading questions

Follow the Thread

Dig deeper when answers reveal complexity. Don't jump topics when current one has unexplored depth.

Batch Questions

Use AskUserQuestion with questions array for 2-4 related questions exploring different angles of the same area.

Saturation

Stop when:

  • Answers stop revealing new information
  • You could explain requirements to someone else
  • User expresses readiness to proceed

Output

Summarize what you've learned:

**Clarified Requirements:**
- **Goal**: [specific goal]
- **Constraints**: [hard limits]
- **Success criteria**: [how we'll know it worked]
- **Key tradeoffs**: [prioritizing vs deprioritizing]
- **Open questions**: [if any]

Integration

SkillWhen to use interviewing first
BrainstormingUser unclear about what they want (not just how)
Technical PlanningRequirements too vague to plan
DebuggingProblem description unclear
Blog WritingTopic or purpose unclear

For writing, also ask: What's the core message? Who's the audience? What triggered this?

Examples

See reference/examples.md for project and writing interview flows.

Score

Total Score

50/100

Based on repository quality metrics

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

0/10
説明文

100文字以上の説明がある

0/10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

0/5

Reviews

💬

Reviews coming soon