Guide ideas through Amazon's Working Backwards process, from 5 Questions to PR-FAQ.
Works with
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
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionamazon-working-backwardsExecute the skills CLI command in your project's root directory to begin installation:
Fetches amazon-working-backwards from robdefeo/agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate amazon-working-backwards. Access via /amazon-working-backwards in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
4
total installs
4
this week
2
GitHub stars
0
upvotes
Run in your terminal
4
installs
4
this week
2
stars
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.
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
Always write to a file from the start. Do not draft in chat.
YYYY-MM-DD - [Product Name] 5Q.mdYYYY-MM-DD - [Product Name] PR-FAQ.mddocx skill to produce a formatted documentWhen asking clarifying questions or presenting feedback, respond in chat. All substantive content (5Q answers, PR-FAQ drafts) goes to file.
The 5 Questions force clarity before any document writing begins:
When reviewing or verifying answers (user's own or previously drafted):
Once 5Q answers are solid, generate the PR-FAQ document.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
jezweb/claude-skills
Solid pick for teams standardizing on skills: amazon-working-backwards is focused, and the summary matches what you get after install.
I recommend amazon-working-backwards for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
amazon-working-backwards has been reliable in day-to-day use. Documentation quality is above average for community skills.
amazon-working-backwards reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: amazon-working-backwards is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend amazon-working-backwards for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added amazon-working-backwards from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: amazon-working-backwards is the kind of skill you can hand to a new teammate without a long onboarding doc.
amazon-working-backwards reduced setup friction for our internal harness; good balance of opinion and flexibility.
amazon-working-backwards fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 57