Agent skill
interview-mode
Ensures proper requirements clarification before implementing features. Activates when asked to implement, build, create, or add features during what appears to be an interview or timed coding exercise.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/interview-mode
SKILL.md
Interview Mode
When implementing features during an interview, ALWAYS clarify requirements BEFORE writing any code.
Before Writing Code
-
Identify Ambiguities
- What's explicitly in scope?
- What's explicitly out of scope?
- What edge cases need handling?
-
Ask Clarifying Questions Use AskUserQuestion with specific options:
- Empty states: How to display when no data?
- Error states: How to handle failures?
- Loading states: Show spinner, skeleton, or nothing?
- Validation: What rules apply to inputs?
- Success criteria: What defines "done"?
-
Confirm Understanding Before coding, summarize:
- What will be built
- What edge cases will be handled
- What is out of scope
Question Format
Use specific options, not open-ended questions:
Good:
How should empty state be handled?
- Show illustration with message
- Show text message only
- Hide the section
Bad:
What should happen when there's no data?
Why This Matters
- Shows communication skills
- Prevents wasted effort on wrong approach
- Demonstrates systematic thinking
- Catches misunderstandings early
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?