amazon-working-backwards▌
robdefeo/agent-skills · updated Apr 8, 2026
Guide ideas through Amazon's Working Backwards process, from 5 Questions to PR-FAQ.
- ›Supports six entry points: drafting 5Q answers from a rough idea, refining existing answers, verifying answers with probing questions, generating a PR-FAQ document, reviewing an existing PR-FAQ, or clarifying any process element
- ›The 5 Questions phase forces clarity on customer, problem, benefit, validation, and experience before any document writing
- ›The PR-FAQ phase transforms solid 5Q answers into a
Amazon Working Backwards
The Working Backwards process moves from idea to PR-FAQ in two phases: first answer the 5 Questions to force clarity of thinking, then write a PR-FAQ document that brings the idea to life for readers.
Workflow
Determine the entry point based on what the user provides:
Starting from a rough idea or proposal? → Follow the "5 Questions Phase" below Have 5Q answers to refine/verify? → Read references/five-questions-guide.md and apply the verification checklist Ready to write a PR-FAQ? → Follow the "PR-FAQ Phase" below Have a PR-FAQ to review? → Read references/prfaq-template.md and evaluate against the writing standards and common rejection reasons Want to clarify a specific element? → Read the relevant reference file for that phase
Output Convention
Always write to a file from the start. Do not draft in chat.
- 5Q answers: Write to
YYYY-MM-DD - [Product Name] 5Q.md - PR-FAQ: Write to
YYYY-MM-DD - [Product Name] PR-FAQ.md - Iterations: Edit the file in place; summarize changes in chat
- Word format: If the user requests .docx, use the
docxskill to produce a formatted document
When asking clarifying questions or presenting feedback, respond in chat. All substantive content (5Q answers, PR-FAQ drafts) goes to file.
5 Questions Phase
The 5 Questions force clarity before any document writing begins:
- Who is the customer?
- What is the customer problem or opportunity?
- What is the most important customer benefit?
- How do we know what the customer needs or wants?
- What does the customer experience look like?
Drafting 5Q Answers
- Read references/five-questions-guide.md for the quality bar and pitfalls for each question
- Read references/examples.md to see a worked example from idea through 5Q to PR-FAQ
- Ask clarifying questions if the user's idea is too vague to answer any question well — ask one question at a time
- Draft all 5 answers, following the "What a strong answer looks like" guidance for each
- Write answers to the 5Q file; summarize in chat and ask for feedback; iterate by editing the file
Verifying 5Q Answers
When reviewing or verifying answers (user's own or previously drafted):
- Read references/five-questions-guide.md
- Apply the verification checklist (coherence, specificity, customer obsession, intellectual honesty)
- Use the probing questions from the guide to challenge weak areas
- Present specific, actionable feedback — not generic praise
PR-FAQ Phase
Once 5Q answers are solid, generate the PR-FAQ document.
- Read references/prfaq-template.md for the exact structure and quality bar
- Read references/examples.md if not already loaded
- Write the Press Release section, mapping: Q2 → problem paragraph, Q3 → solution paragraph, Q5 → experience paragraph, Q1 → customer quote persona
- Write External FAQ (5-10 customer questions)
- Write Internal FAQ (5-10 stakeholder questions)
- Write to the PR-FAQ file; summarize in chat and ask for feedback; iterate by editing the file
Reviewing an Existing PR-FAQ
- Read references/prfaq-template.md, paying attention to the "Common Rejection Reasons" section
- Evaluate each section of the PR-FAQ against the writing standards
- Check that the PR-FAQ is internally consistent (problem → benefit → experience alignment)
- Provide specific, section-by-section feedback with concrete suggestions for improvement
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★57 reviews- ★★★★★Ganesh Mohane· Dec 24, 2024
Solid pick for teams standardizing on skills: amazon-working-backwards is focused, and the summary matches what you get after install.
- ★★★★★Kwame Choi· Dec 16, 2024
I recommend amazon-working-backwards for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Lucas Singh· Dec 12, 2024
amazon-working-backwards has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Shikha Mishra· Dec 4, 2024
amazon-working-backwards reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Mia Gupta· Dec 4, 2024
Keeps context tight: amazon-working-backwards is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Lucas Sanchez· Nov 23, 2024
I recommend amazon-working-backwards for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Sakshi Patil· Nov 15, 2024
We added amazon-working-backwards from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Lucas Shah· Nov 7, 2024
Keeps context tight: amazon-working-backwards is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Henry Agarwal· Nov 7, 2024
amazon-working-backwards reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Hana Ghosh· Nov 3, 2024
amazon-working-backwards fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 57