メニュー
Write an Amazon-style press release that defines customer value before building. Use when aligning stakeholders on a new product, feature, or strategic bet.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/deanpeters/Product-Manager-Skills --skill press-releaseコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Understand the PM-to-Director transition through altitude and horizon thinking. Use when diagnosing scope, time-horizon, or leadership-level gaps.
Create a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry work.
Plan a VP or CPO 30-60-90 day diagnostic onboarding path. Use when entering a new executive product role and avoiding premature change.
SOC 職業分類に基づく
SKILL.md を表示中
| name | press-release |
| argument-hint | [product or feature idea] |
| description | Write an Amazon-style press release that defines customer value before building. Use when aligning stakeholders on a new product, feature, or strategic bet. |
| intent | Create a visionary press release following Amazon's "Working Backwards" methodology to define and communicate a product or feature before building it. Use this to align stakeholders on the customer value proposition, clarify the problem being solved, and test if the product story resonates—treating the press release as a forcing function for clarity and customer-centricity. |
| type | component |
| theme | pm-artifacts |
| best_for | ["Defining customer value before a line of spec gets written","Aligning stakeholders on what a launch actually promises","Killing a weak idea early by trying to write its announcement"] |
| scenarios | ["We're about to build something big and I want to test whether the value is real","Stakeholders disagree about what this launch promises customers — write it as news"] |
| estimated_time | 30-45 min |
Create a visionary press release following Amazon's "Working Backwards" methodology to define and communicate a product or feature before building it. Use this to align stakeholders on the customer value proposition, clarify the problem being solved, and test if the product story resonates—treating the press release as a forcing function for clarity and customer-centricity.
This is not a marketing artifact for launch day—it's a planning tool that asks "If we shipped this perfectly, how would we explain it to the world?"
Works best with: The product or feature idea, plus who it's for. Also useful: The customer problem, the headline benefit, and an internal quote-worthy point of view.
Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended ARGUMENTS: line — counts as answers already given. Use it and skip whatever it covers; don't re-ask.
Arriving empty-handed? That works too. The skill asks who the customer is and what changes for them on launch day — the two things a working-backwards press release cannot fake.
Example invocation: Amazon-style press release: instant expense approval for field technicians, launching Q3.
Popularized by Amazon, the Working Backwards process starts with a press release and FAQ before any code is written. The press release must:
A standard press release follows this format:
Use template.md for the full fill-in structure.
Before drafting, ensure you have:
skills/proto-persona/SKILL.md)skills/problem-statement/SKILL.md)skills/positioning-statement/SKILL.md)If missing context: Run discovery, define the problem statement, or clarify positioning first.
Create a clear, benefit-focused headline:
"[Product/Feature Name] by [Company] Aims to [Main Benefit/Goal]"
Quality checks:
Examples:
[City], [State], [Country], [Date] —
Today, [Company], a [type of organization], announced [key news], a [brief description]. This [product/feature] is set to [main benefit], addressing [key customer problem].
Quality checks:
[Product/feature] solves [specific customer problem]. According to [source or customer insight], [supporting data or quote that validates the problem].
Quality checks:
[Product/feature] addresses this by [how it solves the problem—focus on outcomes]. [Quote from company leader]: "[Insert quote that emphasizes customer value, not features]."
Quality checks:
In addition to [key benefit], [product/feature] also [additional benefits]. According to [statistic or source], [supporting data].
Quality checks:
[Company], founded in [year], is a [type of company] known for [main products/services]. With a focus on [company mission or values], [Company] has [achievements or milestones].
For more information about [product/feature], visit [website] or contact [media contact name] at [contact info].
**Media Contact Information:**
[Name]
Title: [Title]
Phone: [Phone]
Email: [Email]
Ask these questions:
If any answer is "no," revise.
See examples/sample.md for full press release examples.
Mini example excerpt:
**Headline:** "Acme Launches SmartInvoice to Cut Processing Time by 60%"
**Problem:** Small businesses spend 8 hours/month on manual invoices
**Solution:** Automates extraction and approvals to save time
Symptom: "Includes AI, ML, OCR, NLP, and real-time sync"
Consequence: Customers don't care about features—they care about outcomes.
Fix: Translate features to benefits: "AI-powered automation reduces invoice processing time by 60%."
Symptom: "Solves inefficiency in workflows"
Consequence: No one recognizes themselves in this problem.
Fix: Be specific: "Small business owners spend 8 hours/month manually entering invoice data."
Symptom: "Leverages cutting-edge ML models to optimize enterprise-grade workflows"
Consequence: Customers can't understand what you're saying.
Fix: Write like you're explaining it to a friend: "Automatically handles invoices so you don't have to."
Symptom: "We're excited to bring innovation to market"
Consequence: Quote adds no value. Could apply to any product.
Fix: Make it customer-focused: "Business owners shouldn't spend weekends processing invoices—they should spend that time with family."
Symptom: "Customers will love this revolutionary new solution"
Consequence: Unsubstantiated claims = marketing fluff.
Fix: Add data: "Beta users saved an average of 5 hours per month" or "68% of SMBs cite invoice processing as their top admin burden."
skills/problem-statement/SKILL.md — Defines the customer problem the press release highlightsskills/positioning-statement/SKILL.md — Informs the differentiation and value propositionskills/proto-persona/SKILL.md — Defines the target customer mentioned in the press releaseskills/jobs-to-be-done/SKILL.md — Informs the customer benefits and outcomesprompts/visionary-press-release.md in the https://github.com/deanpeters/product-manager-prompts repo.Skill type: Component
Suggested filename: press-release.md
Suggested placement: /skills/components/
Dependencies: References skills/problem-statement/SKILL.md, skills/positioning-statement/SKILL.md, skills/proto-persona/SKILL.md, skills/jobs-to-be-done/SKILL.md