interview
Plan Interview
Refine project plans through Socratic questioning to produce comprehensive specifications.
Workflow
- Read the provided plan file
- Interview the user in-depth using AskUserQuestion about:
- Technical implementation details
- UI & UX considerations
- Potential concerns and edge cases
- Tradeoffs and alternatives
- Ask non-obvious questions that probe assumptions
- Continue interviewing until the plan is complete
- Write the refined spec back to the file
Questioning Guidelines
- Ask about things not covered in the plan
- Challenge assumptions with "what if" scenarios
- Probe technical decisions: "Why this approach over X?"
- Explore edge cases: "What happens when Y fails?"
- Consider users: "How will Z affect the user experience?"
- Question scope: "Is A necessary for MVP?"
Interview Style
- One question at a time
- Use multiple choice when natural options exist
- Build on previous answers
- Go deep before going wide
- Stop when the plan is solid
Output
After the interview is complete, write the refined specification back to the original file, incorporating all insights gathered during the questioning.
More from aviflombaum/claude-code-in-avinyc
ux-ui
UX/UI design principles for clean, intuitive interfaces. Use when designing layouts, improving usability, planning information architecture, or ensuring accessibility. Triggers on "user experience", "usability", "information architecture", "accessibility", "interaction design".
12tailwind
Tailwind CSS patterns, utilities, and component styling for Rails. Use when styling with Tailwind, creating responsive layouts, or building UI components. Triggers on "tailwind", "style with", "css classes", "responsive layout".
9write
Write technical blog posts, tutorials, and documentation in Flatiron School's engaging style. Use for explaining code patterns, debugging stories, or turning complex topics into clear narratives. Triggers on "write a blog post", "tutorial about", "explain how", "technical writing".
8hotwire
Hotwire, Turbo, and Stimulus patterns for Rails. Use when implementing JavaScript interactions, Turbo Frames/Streams, or Stimulus controllers. Triggers on "stimulus controller", "turbo frame", "turbo stream", "hotwire", "rails javascript".
8write-test
Writes comprehensive RSpec tests for Rails applications. Use when writing model specs, request specs, system specs, job specs, mailer specs, channel specs, or storage specs. Triggers on "write tests for", "add specs to", "test the User model", "create request specs", "write RSpec", "add test coverage".
8analyze
Analyze completed development work to identify automation and systematization opportunities. Use after finishing features, fixing bugs, or completing code reviews. Triggers on "analyze for automation", "what can we automate", "compound opportunities", "systematize".
8