Use prfaq

Write an Amazon-style PR/FAQ

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.

Reach for it 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.

Install it

npx skilldrop-cli install prfaq                 # Claude Code, your user folder
npx skilldrop-cli install prfaq --project       # Claude Code, this repo
npx skilldrop-cli install prfaq --ide cursor    # or kiro, codex, antigravity, copilot

It is part of the Product manager pack: --pack product-manager installs it with its neighbours.

Ask for it

Say it the way you would to a colleague. Requests like these route to it:

• "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"

Requests like these belong to a different skill, so it shouldn't answer them:

• "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"

If another skill answers instead, ask for this one by name: "use prfaq".

Check what you get

A good result:

• 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.

Use something else when

• The product is committed and needs requirements — that's prd-draft
• The question is invest/defer with costed options — that's business-case
• Real launch marketing copy for a product that exists — this is a thinking tool, not copywriting
• Org-level strategy or portfolio questions — strategy-analysis

Next

• SKILL.md, the instructions the agent reads
• Its page on the site
• Related: business-case, prd-draft, strategy-analysis

Edit this page on GitHub · View source