question

To clarify product intent and scope before research, interrogate existing documentation and code to map evidence, then grill stakeholders on missing tradeoffs, domain facts, and edge cases to resolve vocabulary and boundaries.

Identifying edge cases and design tradeoffs early involves branch-by-branch design grilling across user behavior, persistence, and failure scenarios, updating the decision tree after each answer to capture explicit non-goals.

Avoid misaligned implementation by grounding feature requirements in an evidence map from existing artifacts, asking humans only for missing intent and priorities, and producing a structured Question Summary handoff.

Yes, you can use existing documentation to resolve missing domain facts by searching and reading relevant vault artifacts and inspecting code for current behavior, asking humans only for unresolved tradeoffs or preferences.

During requirements scoping, isolate unresolved blocking questions by labeling uncertainty explicitly and compiling them into a Question Summary handoff with recommended defaults, rather than moving into implementation prematurely.

You should not use intent clarification when vocabulary, scope, edge cases, defaults, and user preferences are already fully resolved, or when creating artifacts and moving into downstream design and implementation phases in the same turn.