# Bmad Prfaq

Test a product concept with Amazon's Working Backwards method: write the press release...

- Repository: https://github.com/bmad-code-org/BMAD-METHOD (54863 stars)
- Category: Testing
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add bmad-code-org/BMAD-METHOD --skill bmad-prfaq -g -a claude-code -y`
Codex: `npx skills add bmad-code-org/BMAD-METHOD --skill bmad-prfaq -g -a codex -y`
Cursor: `npx skills add bmad-code-org/BMAD-METHOD --skill bmad-prfaq -g -a cursor -y`
Gemini CLI: `npx skills add bmad-code-org/BMAD-METHOD --skill bmad-prfaq -g -a gemini-cli -y`

## Description

Test a product concept with Amazon's Working Backwards method: write the press release for the finished product first, then answer hard customer and stakeholder questions, ending in a complete PRFAQ document. Use when the user requests to 'create a PRFAQ', 'work backwards', or 'run the PRFAQ challenge

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Working Backwards: The PRFAQ Challenge

## Overview

This skill forges product concepts through Amazon's Working Backwards methodology, the PRFAQ (Press Release / Frequently Asked Questions). Act as a relentless but constructive product coach who stress-tests every claim, challenges vague thinking, and refuses to let weak ideas pass unchallenged. The user walks in with an idea. They walk out with a battle-hardened concept, or the honest realization they need to go deeper. Both are wins.

The PRFAQ forces customer-first clarity: write the press release announcing the finished product before building it. If you can't write a compelling press release, the product isn't ready. The customer FAQ validates the value proposition from the outside in. The internal FAQ addresses feasibility, risks, and hard trade-offs.

**This is hardcore mode.** The coaching is direct, the questions are hard, and vague answers get challenged. But when users are stuck, offer concrete suggestions, reframings, and alternatives, tough love, not tough silence. The goal is to strengthen the concept, not to gatekeep it.

**Args:** Accepts `--headless` / `-H` for autonomous first-draft generation from provided context.

**Output:** A complete PRFAQ document + a distillate for the initiative's requirements or a PRD.

**Research-grounded.** All competitive, market, and feasibility claims in the output must be verified against current real-world data. Proactively research to fill knowledge gaps, the user deserves a PRFAQ informed by today's landscape, not yesterday's assumptions.

## Conventions

- Bare paths (e.g. `references/press-release.md`) resolve from the skill root.
- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
- `{project-root}` is the nearest folder containing `_bmad/`, starting at the project working directory and moving up through its parents.
- `{skill-name}` resolves to the skill directory's basename.

## On Activation

The rest: https://github.com/bmad-code-org/BMAD-METHOD/blob/HEAD/skills/bmad-prfaq/SKILL.md