---
name: bmad-prfaq
description: Explore a product concept through a proposed launch narrative and customer and delivery questions.
---

# PRFAQ

Load the [execution guide](../../shared/execution.md) and
[Miriam](analyst-agent.md). Test whether a product promise makes sense to a
customer and can be supported by a plausible delivery plan.

## Inputs

Use the product idea or brief, intended audience, desired outcome, scope and
known constraints. Read an existing PRFAQ before revising it. Identify which
claims describe today's product and which describe a possible future release.

## Procedure

1. State the decision this exercise should inform. Extract the customer's task,
   unmet need and current alternative from the supplied evidence.
2. Write a short proposed launch narrative: headline, audience, problem, outcome,
   how the first use works and availability assumptions. Label the narrative as
   a proposal. Do not invent a real launch date, shipped feature, customer quote
   or endorsement. Illustrative quotes, if useful, must be identified as such.
3. Write the customer FAQ from a skeptical user's perspective: who benefits,
   prerequisites, migration from the current approach, cost assumptions, data
   handling, limits, failure recovery and how to stop using the product. Include
   only topics relevant to the concept.
4. Write the delivery FAQ: smallest useful release, dependencies, effort and cost
   uncertainties, operational ownership, adoption obstacles and the strongest
   reason the proposal might fail. Distinguish estimated answers from measured
   evidence and record unresolved decisions.
5. Challenge material promises against the evidence. Verify external pricing,
   competitor behavior and feasibility claims using current primary sources
   where possible. Unsupported claims remain hypotheses in the document.
6. Revise the promise when the FAQs expose contradictions. Preserve unresolved
   tradeoffs instead of giving every objection an invented answer. Define the
   next observation or experiment that could accept or reject the concept.
7. Distill the result into potential requirements and explicit exclusions. Keep
   speculative features distinguishable from requirements supplied by the user.

## Output

Produce one report containing the proposed announcement, customer FAQ, delivery
FAQ, claim-to-evidence table, candidate requirements, exclusions and next
validation action. The claim table records the claim, its source or assumption,
confidence limitation and consequence if false.

## Acceptance and continuation

The core promise, first-use description and delivery scope must agree. Readers
must be able to distinguish proposed availability from an actual release.
This artifact does not authorize publication or customer contact.

On resume, compare changed claims and inputs, then revisit affected FAQ answers
before editing the narrative. A supported concept can feed
[Product brief](product-brief.md) or [PRD creation](../planning/create-prd.md).