Menu
Run a discovery interview to gather requirements before planning a feature
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Stages and commits changes while checking for repo location and branch safety.
Run all code quality checks for the current project including linting, formatting, and type checking. Supports Node.js, Python, Go, and Rust.
Address, fix, and resolve PR review comments. Auto-fixes "claude fix" comments, handles actionable feedback, summarizes discussions.
Ship changes by committing, pushing, and creating a PR to main.
Comprehensive UI design system and principles for building polished, professional interfaces. Use this skill whenever building or styling frontend components, pages, layouts, dashboards, forms, cards, navigation, tables, modals, buttons, or any user-facing HTML/CSS/React/Tailwind. Triggers include: creating new UI, reviewing or improving existing UI, choosing colors, spacing, typography, shadows, or layout strategies, fixing designs that look "off", and building design systems or component libraries. Apply these principles by default when generating any frontend code.
| name | interview |
| description | Run a discovery interview to gather requirements before planning a feature |
| disable-model-invocation | true |
| user-invocable | true |
| argument-hint | [feature description] |
| allowed-tools | AskUserQuestion, Read, Glob, Grep, WebSearch, WebFetch |
You are conducting a discovery interview to gather requirements before implementation planning.
The user wants to implement: $ARGUMENTS
Before asking questions, explore the codebase thoroughly to understand the existing architecture, patterns, and relevant code areas. If the feature involves external libraries, APIs, or concepts you need more context on, run web searches to inform your questions.
Use the AskUserQuestion tool to ask focused questions. Ask 2-3 questions at a time to keep momentum while gathering thorough information. Cover these areas:
After gathering answers, provide a structured requirements summary formatted like this:
## Requirements Summary
### Overview
[One paragraph summary of the feature]
### Must-Have Requirements
- [ ] Requirement 1
- [ ] Requirement 2
### Nice-to-Have Requirements
- [ ] Requirement 1
### Technical Decisions
- Pattern: [chosen pattern]
- Libraries: [any specific libraries]
- Files affected: [list of files/areas]
### Edge Cases to Handle
- Case 1: [how to handle]
### Testing Strategy
- [testing approach]
### Open Questions
- [any unresolved questions]
Do NOT start implementing or enter plan mode. Only gather requirements and produce the summary. The user will then use this summary to enter plan mode.