spec-interview

Refining product specifications through structured interviews involves guided questioning to extract detailed technical, UI/UX, and risk requirements, updating the ticket with refined requirements, and creating downstream design tasks.

Extracting technical and UI/UX requirements from a ticket uses guided interviewing prompts to elicit details, reads the relevant requirements.md for context, and updates the ticket with the clarified specifications.

Starting a requirements interview with a ticket ID involves passing the identifier to the workflow, which reads the ticket's requirements.md to gather context and initiates structured questioning to resolve ambiguities.

Automating downstream design tasks after finalizing requirements is supported by the end-to-end task orchestration, which updates the ticket, regenerates knowledge references, and creates subsequent design work automatically.

Guided questioning works for resolving edge cases in product workflows by systematically interviewing users to uncover potential risks and ambiguities early, ensuring the updated specifications cover all constraints.

Updating ticket requirements during an interview operates strictly within a ticket-driven workflow, requiring a valid TICKET_ID or ticket selection to read the requirements.md and execute the specification refinement process.