change-interviewer

To clarify ambiguous change requirements before implementation, you can generate a source-grounded interview packet that stress-tests drafts by grounding questions in repository code, docs, and existing specs to identify gaps and risks.

Refining OpenSpec change directories involves inventorying evidence, asking high-value questions for acceptance criteria, and applying deterministic write-back to persist confirmed answers back into the agreed target files.

Evidence-grounded questioning works by reading provided drafts, issues, or OpenSpec directories, inventorying existing repository evidence, and generating high-value questions to address gaps, risks, and missing acceptance criteria.

Yes, you can generate a user-facing interview packet in Simplified Chinese from rough change ideas, while keeping file paths and technical terms in their original form for accurate requirements clarification.

Yes, the interview packet generation supports controlled write-back, ensuring refined results are persisted only after questions are answered, mapping confirmed answers directly back to the agreed target files.

You need to stress-test a change interview packet when you have ambiguous change drafts, plans, issues, or tickets, ensuring requirements are confirmed and repaired before moving into implementation.