amazon-working-backwards
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 press release and dual FAQ (external customer questions, internal stakeholder questions)
- All substantive content writes directly to timestamped markdown files; feedback and iteration happen in chat
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.
More from robdefeo/agent-skills
para-second-brain
Use this skill when the user wants to organize, classify, or maintain a PARA-method second brain. Triggers include asking where to file something, distinguishing projects from areas, processing an inbox, setting up a new project, completing or archiving a project, running a monthly review, validating system structure, or finding stale/orphaned content.
322diataxis-documentation-guidance
Use this skill to classify, scope, split, draft, and review documentation with the Diataxis framework. Triggers include choosing tutorial/how-to/reference/explanation mode, resolving mixed-mode pages, rewriting docs into a target mode, and validating drafts with a checklist.
9pr-create
Use this skill whenever the user wants to create, open, or raise a new GitHub pull request from the current branch — including phrasings like \"open a PR\", \"raise a PR\", \"make a PR\", \"ship this\". Drafts a Conventional Commits title and a Summary body that explains *why* and *what*, respects `.github/pull_request_template.md` when present, auto-links referenced issues, waits for approval, then pushes and opens the PR. Assumes commits already exist. Requires `gh` CLI.
5pr-address-feedback
Use this skill whenever the user wants to address, respond to, work through, or handle GitHub PR review comments — including code review feedback, reviewer suggestions, bot comments, or requested changes — even if they don't say \"address\". Handles the full end-to-end workflow: fetch threads, plan fixes, commit, push, and reply. Requires `gh` CLI.
4