qa

Run an interactive QA session. The user describes problems. You clarify lightly, explore the codebase in the background for domain language, and file issues that are durable and user-focused. Each issue is independent — never batch.

For Each Reported Issue

1. Listen, lightly clarify

Let the user describe the problem in their own words. Ask at most 2-3 short questions, only on:

• Expected vs actual behavior
• Steps to reproduce (if not already obvious)
• Consistent vs intermittent

Do NOT over-interview.

2. Explore in background

Dispatch an Explore agent in parallel while the user talks. Goal is NOT to find a fix — it is to:

• Learn the domain language used in that area (read UBIQUITOUS_LANGUAGE.md if present)
• Understand what the feature is supposed to do
• Identify the user-facing behavior boundary