harness-product-brief

Validating assumptions in a product brief requires a discovery-first coaching approach to surface unknowns through structured conversation, ensuring stakeholder alignment before downstream PRD workflows.

Create a product brief by iteratively extracting project purpose and constraints, then maintaining a canonical decision log to preserve audit traceability and right-sized artifact generation for stakeholders.

Yes, you can update an existing product brief by applying guided discovery to reconcile changes, capturing user-contributed depth in an addendum to preserve context for later architecture workflows.

Product discovery coaching supports both early ideation and internal pitch preparation by pressure-testing the brief against its stated purpose, halting with a clear blocked reason if intent is ambiguous.

In headless mode, product brief generation runs without prompting but halts automatically with a clear blocked reason if intent is ambiguous, requiring YAML frontmatter compliance to resume artifact generation.