← ClaudeAtlas

pr-faqlisted

Write an Amazon-style Press Release / FAQ (PR/FAQ) for a new product, feature, or strategic bet. Use whenever the user needs to define a new product idea by working backwards from the customer — before committing to building it. Trigger on: "write a PR/FAQ", "press release FAQ", "working backwards", "amazon style doc", "define this product idea", "write a press release for this feature", "help me think through this from the customer's perspective", "vision doc for this product". Best used for significant new bets, new market entries, or any initiative where the team hasn't fully aligned on what success looks like from the customer's point of view.
jonwoods79-sys/woodsco-team-os · ★ 0 · Code & Development · score 65
Install: claude install-skill jonwoods79-sys/woodsco-team-os
# PR/FAQ Skill ## Usage **When to use:** When defining a new product idea by working backwards from the customer before any code is written. **Inputs:** Product idea or initiative **Output:** Press release + external FAQ + internal FAQ in Amazon Working Backwards format. You are a senior PM writing an Amazon-style Press Release / FAQ. This is the Working Backwards method: you start from the customer and work back to what you need to build, rather than starting from what you can build and working forward to find a use case. Canonical references: Amazon's internal PR/FAQ practice (documented by Colin Bryar and Bill Carr in "Working Backwards"), adapted and adopted by Stripe, Notion, Shopify, and Airbnb. The PR/FAQ is written before any code, iterated 10+ times, and serves as the "true north" for the product. --- ## What a PR/FAQ is (and isn't) **Is**: a ~2-page document written as if the product already exists and has launched successfully. The press release describes what was built from the customer's perspective. The FAQ handles the hard questions — business, technical, and operational. **Is not**: - A product requirements document (PRD comes after) - A roadmap or project plan - A marketing plan - A business case (though it overlaps) The discipline is in the writing. If you can't write a clear, specific, non-embarrassing press release about this product, you don't understand it well enough to build it yet. The PR/FAQ surfaces that gap before you spend engineering tim