aped-prfaq

A working backwards PRFAQ is a press release and FAQ document used to validate a product concept by clarifying the customer, problem, stakes, and solution before deeper planning. You need it to stress-test pitches and replace vague proposals with disciplined customer validation.

To create a press release first, provide a customer persona, a concrete problem, the stakes, and a rough solution concept. The draft generates a customer-facing press release and FAQ, enforcing stage-gated validation to prevent weak assumptions from propagating, then writes the artifact to the output directory.

Yes, you can use a PRFAQ approach to stress-test a concept before writing a PRD. It forces customer and problem clarity by drafting a press release and generating tough customer objections alongside stakeholder feasibility questions, ensuring your assumptions are validated before deeper product requirement documentation.

Yes, the PRFAQ workflow supports optional headless autonomous drafting when provided concrete inputs. It processes your customer persona, problem, stakes, and solution concept to automatically generate the press release and FAQ artifacts, strictly enforcing quality bars that eliminate jargon and weasel words.

The best way to prevent weak assumptions from propagating during product discovery is to use a stage-gated PRFAQ workflow. It requires explicit user validation between drafting stages, ensuring that customer objections, stakeholder questions, and solution clarity meet quality bars before deeper analysis begins.