domain-discovery-brief

name	Domain Discovery Brief
description	Produce concise domain context and constraints without taking over product or technical ownership.
when-to-use	Use when the team needs external/domain context, comparable products, standards, regulations, or benchmark references.
user-invocable	false
context	inline

Research supports decisions; it does not replace PRD ownership, UX design, or technical plans.

Brief structure:

• Question being answered.
• Sources or local evidence consulted.
• Constraints and assumptions that affect product requirements.
• Comparable patterns, standards, or risks.
• Recommendations with confidence level.
• Open questions requiring user or stakeholder input.
• Impact on PRD, UX, frontend, backend, QA, or Reviewer work.

Quality bar:

• Keep findings concise and attributable.
• Distinguish evidence from inference.
• Do not invent stack choices or implementation details.
• When facts may have changed recently, use current primary sources or state uncertainty.