interview

Conduct structured interviews to document requirements and compose implementation specs.

25|10|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/neuron-one/GODMODE --skill interview-neuron-one
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interview
Source: https://github.com/neuron-one/GODMODE/tree/main/skills/workflow/interview
Command: npx skills add https://github.com/neuron-one/GODMODE --skill interview-neuron-one

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conducts a deep interview before building features or projects, asking 20-50 questions across business, product, technical, security, and marketing blocks to surface critical requirements and assumptions.

Core Features & Use Cases

  • Multi-block interview across BUSINESS, PRODUCT, TECHNICAL, SECURITY, LAUNCH, and MARKETING to surface requirements and constraints.
  • Guided question flow that challenges assumptions, uncovers non-obvious risks, and clarifies success criteria.
  • Output-ready results that translate interview findings into a final spec for implementation and alignment.

Quick Start

Initiate the interview workflow and continue until all questions are answered and assumptions clarified, then synthesize the final spec.

Frequently Asked Questions about interview

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I gather complete product requirements before building a new feature?

Conduct a structured requirements interview across business, product, technical, security, launch, and marketing blocks to surface constraints, success criteria, and risks before development. This guided process asks 20-50 questions to clarify all assumptions and produce a final implementation spec.

What is a structured requirements interview for product management?

A structured requirements interview is a deep questioning process across business, product, technical, security, launch, and marketing blocks to uncover non-obvious risks and clarify success criteria. It challenges assumptions through a guided question flow until all constraints are documented for implementation alignment.

How do I identify technical and security constraints for a go-to-market launch?

Identify technical and security constraints by running a multi-block interview that specifically targets architecture, security requirements, and launch criteria. This surfaces hidden risks and documents necessary constraints before any major project or architectural decision is finalized.

When do I need to conduct a deep interview before an architectural decision?

Apply a deep interview before any major feature, project, or architectural decision to surface critical constraints, success criteria, and risks. It is necessary when you need to clarify assumptions across business, technical, security, and marketing domains before committing to implementation.

Can I use a guided interview to translate user assumptions into an implementation spec?

Yes, a guided interview translates user assumptions into an implementation spec by continuing to ask questions across all relevant blocks until every assumption is clarified. The output-ready results synthesize findings directly into a final spec for the implementation workflow.

Does the requirements interview process work for risk assessment and project planning?

Yes, the requirements interview works for risk assessment and project planning by systematically uncovering non-obvious risks across technical, security, and launch blocks. It ensures all business and product assumptions are clarified and documented before finalizing your project architecture.