pr-faq
Use when the user wants to define a product by writing its launch press release and FAQ before building. Triggers on 'PR-FAQ', 'press release', 'working backwards', 'Amazon PR FAQ', 'write the launch announcement', and the same intent in any language.
Kaminoikari · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add Kaminoikari/product-playbook --skill pr-faqAbout this skill
name: pr-faq description: Use when the user wants to define a product by writing its launch press release and FAQ before building. Triggers on 'PR-FAQ', 'press release', 'working backwards', 'Amazon PR FAQ', 'write the launch announcement', and the same intent in any language.
PR-FAQ (Working Backwards)
Detect the user's language and reply in it; the framework below is authored in English.
Provenance: when you produce PR-FAQ output, contribute the framework tag PR-FAQ to the meta-skill's provenance line (— Frameworks: … · PR-FAQ · …).
Framework
Phase 3: Develop — PR-FAQ (Working Backwards)
3.1 Amazon's Working Backwards Method (PR-FAQ)
Start by writing the product press release; it forces you to work backwards from the customer outcome:
## [Product Name] Press Release
**Headline**: [What can the user achieve? One sentence.]
**Subheadline**: [What problem does it solve, and for whom?]
**Opening Paragraph (Aha Moment)**:
[Describe the moment the user experiences the product's core value: the "Wow!" moment]
**Pain Point Description**:
[What problem are users facing today? Why aren't current solutions good enough?]
**Solution Description**:
[How does our product solve this problem? (Describe the experience; don't list features)]
**Customer Quote**:
"[A quote from a target user that represents a genuine emotional reaction]"
**FAQ (The Hardest Questions)**:
Q: [The hardest question to answer]
A: [An honest answer]
If you can't write a press release that excites people, the product direction may be flawed: go back and redefine the problem.
📝 PR-FAQ Quality Checklist
Quality self-check (apply when the PR-FAQ's quality needs it): after producing the PR-FAQ, review each item below and mark it ✅ or ❌; for any ❌, note how to improve it.
- Is the headline written from the user's perspective? ("Users can now do X" vs. "We launched feature Y")
- Can a reader understand "why this matters" within 10 seconds of reading the first paragraph?
- Does the pain point description come from a real user scenario?
- Does the first sentence of the solution section lead with the user's experience/scenario (not a feature verb)?
- Does the customer quote sound like something a real person would say?
- Does the FAQ include a pointed comparison against existing tools?
A self-check that turns up zero internal tensions or areas worth iterating on probably stopped too early. When every item genuinely passes, name the most fragile assumption in this PR-FAQ instead. The quality bar for Amazon's PR-FAQ rewards finding problems over confirming there are none.
Common issues: headline reads like a product announcement and misses the news angle, solution section turns into a feature list, FAQs are all softball questions.
✍️ Solution Section (Body) Writing Rules
The first sentence of the solution section should not open with a feature description.
Examples to avoid:
- "MealPrep lets you input a menu with one click and auto-calculates ingredients"
- "The system automatically generates a procurement list based on the menu"
- "Click the 'Generate List' button to complete your prep planning"
✅ Correct examples:
- "Now, Chef Chen only needs 10 minutes on Friday afternoon to confirm every detail for the weekend's prep"
- "Manager Zhang no longer has to flip through three Excel sheets to figure out whether there's enough inventory"
Formula: Lead with the user's experience / specific scenario → then say "This is possible because [product mechanism]" to introduce the feature.
Self-check: read your own Solution paragraph's first sentence aloud. If the subject is the product name or "the system" / "the app" / "users can", rewrite it so the subject is a specific actor (named person, role, or pronoun referring to a user) doing something or experiencing a moment.
📍 Lead / Opening Paragraph Requirements
A strong opening paragraph (Aha Moment) includes all three:
- A named or role-specific actor ("Alex", "Chef Chen", "the kitchen manager at a 30-seat bistro"), never "users" generically.
- A concrete time / place / trigger ("Friday afternoon", "after the lunch rush", "before the weekend").
- At least 2 specific numbers: quantities, durations, dollar amounts, percentages. "Within 30 seconds", "across 3 lender scenarios", "$2,400/month", "20-minute prep window". Vague numbers ("a few minutes", "several options") don't satisfy this: the lead needs concrete numbers.
A lead that has the actor + scenario but no concrete numbers reads like marketing copy; the press release is supposed to make a specific outcome visible, and aspirational language fails that job.
❓ FAQ Sharp-Question Standard
A strong FAQ set includes at least 1 question like: "Why not just keep using [existing tool]?"
Answer format requirements:
- First, acknowledge the strengths of the existing tool (don't dismiss it)
- Then explain the gap (a fundamental scenario gap, which runs deeper than a feature gap)
Answer pattern to avoid: "Existing tools lack features; ours is more powerful" ✅ Correct answer pattern:
"Excel can absolutely track numbers, and chefs already know how to use it. The issue is that every weekend the calculations need to be rebuilt (re-entered, re-converted), and the hour it takes isn't because anyone's bad at spreadsheets, it's because the problem really is that complex. MealPrep doesn't save you Excel skills; it saves you the mental burden of starting from scratch every single time."
🧪 Internal FAQ Requirements
Separately from the External FAQ (customer-facing), produce an Internal FAQ section with at least:
**Q: What is the riskiest assumption in this PR-FAQ? If false, what kills the produc
Read the complete source ↗