From auto-dev
Deep-dive technical discovery and requirement gathering before coding. Use when a task is broad, ambiguous, or requires architectural decisions.
How this agent operates — its isolation, permissions, and tool access model
Agent reference
auto-dev:skills/interview-skill/skillThe summary Claude sees when deciding whether to delegate to this agent
This skill forces a "slow down to speed up" workflow. Before writing implementation code, conduct a thorough technical interview to uncover hidden requirements and trade-offs. - Task description is vague or broad ("add auth to my app") - Multiple valid approaches exist - Architectural decisions are needed - User requirements may have hidden complexity - The task could be interpreted multiple waysThis skill forces a "slow down to speed up" workflow. Before writing implementation code, conduct a thorough technical interview to uncover hidden requirements and trade-offs.
Stop and Think - Do not start coding yet.
Interview Phase - Use the AskUserQuestion tool to gather requirements:
Ask Deep Questions - Challenge assumptions:
Iterate - If an answer reveals complexity, ask follow-up questions.
Spec Creation - Summarize findings into a specification document.
Confirmation - Get user approval before proceeding to implementation.
User: "I want to add auth to my app."
Interview Questions:
After the interview, create a spec document:
# Feature Specification: [Feature Name]
## Requirements
- Requirement 1
- Requirement 2
## Technical Approach
- Approach details
## Edge Cases
- Edge case 1
- Edge case 2
## Out of Scope
- Items explicitly excluded
## Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2
npx claudepluginhub seajhawk/cc-marketplaceConducts in-depth interviews via AskUserQuestion on technical implementation, UI/UX, concerns, and trade-offs. Analyzes codebase, writes plans to .claude/plans/, and executes implementations.
Socratic interviewer that probes vague requirements, new features, or unclear goals with targeted questions to surface hidden assumptions. Invoke proactively before coding or specs. Read-only tools.
Intent verification agent that researches code and web, then iteratively probes scope, users, success criteria, and trade-offs until intent is confirmed without new aspects. Use when requests are ambiguous or scope shifts.