concept

Amazon Concept Definition Skill

Use this skill when creating concise, customer-obsessed concept documents that transform product ideas into structured, actionable definitions following Amazon's proven format.

Template: See docs/templates/concept-template.md for the authoritative template structure.

When to Use This Skill

• When formalizing a product idea into a structured document
• When creating a concept document for leadership review
• When translating feature ideas into customer-focused narratives
• When preparing the initial document before a full PRFAQ

Document Structure Summary

Create a 600-800 word document (~1 page) with these sections:

1. Title - Customer-focused product/feature name
2. Overview (1-2 paragraphs) - What it is, who it's for, why it matters
3. Customer Problem (2-3 paragraphs) - Pain points, workarounds, cost of inaction
4. Proposed Solution (2-3 paragraphs) - How it works, mechanisms, scope
5. Customer Benefit (1-2 paragraphs) - Tangible value, quantified outcomes
6. Tenets (3-5 principles) - Guiding principles with tradeoffs
7. Next Steps - Validation activities, key questions

Writing Style

Quality Checklist

• Title is customer-focused, not technical
• Overview is under 100 words
• Customer Problem doesn't mention the solution
• Solution includes clear scope and tradeoffs
• Benefits are quantified where possible
• Tenets are actionable and specific
• Next Steps are concrete
• Total word count: 600-800 words

Pre-Writing Questions

If input lacks detail, gather:

1. Who is the target customer?
2. What specific problem are they facing?
3. What are current alternatives/workarounds?
4. What makes this approach different?
5. What's explicitly out of scope?

Output Location

docs/concepts/[product-name]-concept.md