project-interview

A structured project interview is a guided discovery process to define project fundamentals by questioning stakeholders. You need it during early-stage planning and product discovery to reduce ambiguity and align scope before development begins.

Conduct a project definition interview by asking three to four broad questions per turn across vision, users, and functionality. Start broad, challenge vague answers, propose defaults, and summarize responses to capture precise stakeholder requirements.

The best way to document stakeholder requirements is to update a project definition file immediately after each interview turn. Capturing details proactively in docs/project.md ensures a repeatable structure for post-interview deliverables.

Yes, a structured interview protocol can cover technical constraints, scope, timeline, and risks. By applying vendor-like interview discipline, it guides discovery across all core project areas to ensure comprehensive scope alignment.

You should ask three to four questions per turn when interviewing stakeholders for project planning. This discipline enforces focused discovery, allowing you to start broad, propose defaults, and challenge vague answers effectively.

The project interview process updates project documentation by writing captured details to docs/project.md. After each interview response, the workflow proactively records the comprehensive project definition for repeatable post-interview deliverables.