bug-capture

Turn a conversation into an issue that still reads correctly after a major refactor.

Flow

1. Listen, then clarify minimally

Let the user describe the problem in their own words. Ask at most two short clarifying questions, drawn from:

• Expected behavior vs. actual behavior.
• Concrete reproduction steps if not already implied.
• Frequency: deterministic, intermittent, or one-off.

If the description already answers these, skip straight to filing. Over- interviewing is a tax the reporter pays for your uncertainty.