pm-pr-faqlisted

# pm-pr-faq Write a future-state launch document as if the thing is already shipping. The discipline is what matters: by forcing yourself to write the press release first, you discover whether the customer benefit is real, whether the persona is recognizable, and whether the tradeoffs are admittable in public. If those are weak, the document tells you to *not build* — which is the highest-leverage version of this artifact. Two parts: 1. **Press Release (PR)** — 1 page, dated at the future launch date, in the voice and shape of a real press release. 2. **Internal FAQ** — 10-15 hard questions with honest answers, including the questions the team would rather not address. ## Arguments | Arg | Description | Default | |-----|-------------|---------| | **source** | File path (strategy memo, brief, conversation), `--from-conversation`, or thesis | *(required)* | | `--launch-date` | Future date the PR is dated at | ask | | `--audience` | Who reads it: `internal`, `investors`, `customers`, `mixed` | `internal` | | `--with-stress-test` | Run the adversarial stress-test pass | `true` | ## Workflow 5 steps. Don't skip Steps 3-4 — the adversarial FAQ generation and stress-test are where this artifact earns its keep. ### Step 1 — Context gather (5 questions, asked together) If `--from-conversation`, infer from context. Otherwise, ask: 1. **What's the future state?** Describe the launched thing in 2-3 sentences. What does the customer see, hear, experience after launch? 2. **Launch