Write an Amazon-style PR/FAQ — the launch press release for a product that doesn't exist yet, plus the customer FAQ and internal FAQ that force the hard questions before engineering starts. Use when the user wants a PRFAQ, a working-backwards document, a "write the press release first" exercise, or needs to align stakeholders on what a product must be before committing a team to build it.
Pack product-managerTier standardJob Decide what to buildv0.1.2
In Claude Code, with the product-manager plugin installed, invoke it as:
/product-manager:prfaq
Try it
A realistic prompt from the skill's acceptance evals:
Write a PRFAQ for an AI-powered contract review tool aimed at in-house legal teams at mid-market companies. The problem: legal teams spend 60% of their time on low-complexity contract review that blocks deal closure.
What a good result looks like
The problem paragraph is in the customer's words. If it contains a term the customer wouldn't say out loud, it fails.
The first-success event is behavioral and observable — you could watch a session recording and mark the moment it happened.
The solution names a mechanism, not a category. "Uses AI" describes a decade of products; what does *this one* do differently?
At least one customer-FAQ answer concedes a trade-off. Honesty in the FAQ is what separates a forcing function from a pitch.
The internal-FAQ success metric counts the first-success event — not sign-ups, not launches, not page views.
The kill condition is named. A PRFAQ that can't say what failure looks like hasn't confronted the riskiest assumption.
No spec content. Zero API shapes, acceptance criteria, or backlog items — those belong downstream in prd-draft.
How it's checked
Measured against plain Claude Code (2026-10-23): it met 79% of its checks, against 62% without it, and a blind judge preferred the agent without it. How skills are checked
27 assertions across 4 acceptance evals, and 10 trigger queries. Every skill's checks
What the output must do
Press release contains all blocks: headline, sub-headline, problem paragraph, solution paragraph, leadership quote, customer quote, call to action
The headline names the product and a customer benefit — not a category claim like 'launches AI-powered platform'
The problem paragraph is in the customer's words with no industry jargon
The solution paragraph names a mechanism, not just 'uses AI'
The leadership quote is attributed to a role (not a placeholder name) and states a strategic rationale
An adoption hypothesis names a first-success event that is a customer action, observable within a session — not 'signs up', 'completes onboarding', or a team action like 'launch'
A repeat-value behavior is named
Customer FAQ has 3-5 questions and at least one answer concedes a real trade-off
Internal FAQ names the riskiest assumption with a test, the hardest technical problem, a concrete acquisition path, and a kill condition
The internal-FAQ success metric counts the first-success event, not a vanity metric
No acceptance criteria, API shapes, or backlog items appear anywhere
The output ends with a hand-off pointing to prd-draft or business-case
No press release is fabricated — with no customer, problem, or differentiator derivable, the output is a BLOCKED response
The BLOCKED output names the missing anchors (customer, problem, differentiator) and what to rerun with
No invented product, customer segment, or problem statement appears
Does not claim that 72% of members want the service; reflects that only 58 of 410 members responded
Catches that the per-acre costs add up to $12.00, not $10.20, so the margin at $14 is about 14%, not 27%
Does not promise members they can book a drone for any field; addresses the 50 m waterway rule affecting about 35% of member acreage
Flags that an April 2027 launch conflicts with a 9–12 month certification process that has not started, rather than writing as if spring is achievable without comment
The press release is under 400 words
Does not invent data (member counts, prices, dates, yields) not in the notes; any new figure is labelled as an assumption
Delivers a press release and FAQs without stopping to ask questions first
The press release is about half a page (no more than roughly 300 words) and there are only a few FAQs (no more than about 8)
Written as an announcement of the carpool matching as if it exists, with the benefit to families stated plainly
The FAQs take on at least one hard practical question a parent or the league would ask, such as driver vetting and child safety, insurance or liability, or what happens when a driver cancels
Does not invent statistics, sponsors, or partner organisations presented as fact (for example 'cuts driving by 40%')
Plain language suited to parents in a volunteer-run league, without corporate or tech jargon
When it should and shouldn't activate
Should activate:
Write a PRFAQ for our new product idea
I want to write the press release before the product exists
Help me do an Amazon-style working-backwards doc for this concept
We need to align stakeholders on what this product actually is before engineering starts
Write the press release and FAQ for this idea and tell me if it survives its own hard questions
Should leave to another skill:
Draft the product requirements doc for the new feature
Write a business case for building vs buying this tool
Write the marketing copy for our launch homepage
Run a SWOT analysis on our product line
Write release notes for what we shipped this sprint