Use when writing narrative memos, 6-pagers, 1-pagers, press releases, or PRFAQs in Amazon style. Applies Amazon's no-PowerPoint writing standards with data over adjectives, active voice, and the "so what" test.
Rewrites content into Amazon-style narrative memos using data-driven writing. Applies Amazon's no-PowerPoint standards—replacing adjectives with metrics, converting to active voice, and enforcing the "so what" test for executive documents.
/plugin marketplace add pproenca/dot-claude-old/plugin install doc@dot-claudeThis skill is limited to using the following tools:
references/one-pager.mdreferences/press-release.mdreferences/prfaq.mdreferences/six-pager.mdAmazon has a distinctive "no PowerPoint" culture that emphasizes narrative memos and clear, data-driven communication. This skill provides guidelines for rewriting content following Amazon's internal writing standards.
Apply these six principles to all Amazon-style documents:
Write in complete narrative form with logical flow from beginning to middle to end. No bullet points or slide-style formatting. The document tells a complete story where all information connects logically. Each paragraph builds on the previous one, leading to a coherent and persuasive argument.
Use simple, straightforward language. Avoid jargon and acronyms unless spelled out on first use. Keep sentences under 30 words when possible. If specialized terms are necessary, provide brief explanations. The reader should understand the topic without needing supporting documents.
Replace vague qualifiers with specific, quantifiable data and metrics:
| Avoid | Use Instead |
|---|---|
| "significantly increased" | "increased 47%" |
| "many customers" | "1,247 customers" or "73% of customers" |
| "very fast" | "completes in 2.3 seconds" |
| "substantial savings" | "$2.4M annual savings" |
| "recently" | "on March 15, 2024" |
Every claim requires evidence, not assumptions.
Write in active voice for clearer, more concise, and more confident text:
| Passive (Avoid) | Active (Use) |
|---|---|
| "The feature was developed by the team" | "The team developed the feature" |
| "Customers were surveyed" | "We surveyed customers" |
| "The decision was made" | "Leadership decided" |
Every sentence must add value and have a clear purpose. The reader should immediately understand why each piece of information matters. If a sentence doesn't pass the "so what" test, remove it or rewrite it to show relevance.
Present the most important information clearly and early. Eliminate "clutter" words that don't add meaning. Executives should immediately understand why they should care within the first page.
Amazon uses four primary document formats. Load the appropriate reference file based on document type:
| Document Type | When to Use | Reference File |
|---|---|---|
| Press Release | New product/feature announcements | references/press-release.md |
| 6-Pager | Complex strategic topics, detailed analysis | references/six-pager.md |
| 1-Pager | Straightforward topics, quick decisions | references/one-pager.md |
| PRFAQ | Product innovation, working backwards | references/prfaq.md |
When rewriting content to Amazon style:
Use a scratchpad to analyze before rewriting:
Read the appropriate reference file for the target document type to understand required sections and format.
Transform the content following:
Check the rewritten content against:
A well-written Amazon document demonstrates:
The great memos are written and re-written, shared with colleagues for improvement, set aside for a couple of days, and then edited again with a fresh mind.
For detailed document-specific guidelines:
references/press-release.md - Press release format and sectionsreferences/six-pager.md - 6-pager memo structurereferences/one-pager.md - 1-pager memo formatreferences/prfaq.md - PRFAQ structure with FAQ guidelines