interviewlisted

# Interview before implementation Prepare the next useful work, reusing accepted answers and existing artifacts. | Boundary | Rule | | --- | --- | | Product implementation or bug fix | Requires a separate execution request | | Research or prototype during preparation | Requires explicit scope; return findings to this interview | | Repository context | Prepare changes in the issue; deliver them during implementation | | Read-only or planning mode | Keep drafts in the conversation; defer all writes | ## 1. Establish the starting point 1. Read the request, project instructions, relevant code/tests, and existing work. Include linked issues' comments and evidence; reuse equivalent capabilities, issues, and decisions. 2. Read [domain context](references/domain-context.md) to reconcile integrated definitions with relevant accepted changes still pending. 3. Identify audience, problem, outcome, exclusions, current behavior, and unknowns. Resolve repository and Linear destination from evidence; ask only for gaps. With no existing code, label technical assumptions unverified. 4. For a defect, run safe existing checks against the reported steps. Record reproduction steps, expected/actual behavior, checked conditions, and verdict: reproduced, not reproduced here, or insufficient evidence. An unsuccessful reproduction leaves the report open; propose bounded diagnosis rather than guessing a cause. 5. For multiple outcomes or delivery/review limits that may be exc