Interview Methodology Skill

You can turn user interviews into implementation-ready feature documentation by using a structured four-pass methodology that incrementally builds a mental model and enforces checkpoints to eliminate ambiguous requirements.

Gathering technical requirements through a progressive questioning process with decision forcing and quality gates removes TBDs, surfaces blind spots, and records rationale in a decisions log for downstream planning.

Structuring an interview with a four-pass methodology (Shape, Flow, Detail, Completeness) captures stage-level specifications and error handling by enforcing checkpoints before advancing through the discovery session.

Yes, you can generate a canonical Markdown documentation file directly from technical requirements gathering sessions, placing the output at documentation/<prefix>_<feature_name>_documentation.md for execution.

Yes, this interview methodology works for pre-implementation planning and developer handoffs by producing a single, implementation-ready feature document suitable for execution.

You start a guided interview for feature discovery by running the /interview command with the feature name, such as /interview batch video annotation pipeline, to begin the four-pass process.