working-backwards
Domain Context
This skill implements a proven product management framework. The approach combines best practices from industry leaders and is designed for practical application in day-to-day PM work.
Input Requirements
- Context about your product, feature, or problem
- Relevant data, research, or constraints (recommended but optional)
- Clear articulation of what you're trying to achieve
Working Backwards
What It Is
Working Backwards is Amazon's product development methodology. The core insight: start with the customer problem and work backward to the solution, not the other way around.
Most teams work forward: "We have this technology/capability/idea — what can we build with it?" Working Backwards inverts this: "What problem does the customer have? What would the ideal solution look like? Now, how do we build it?"
More from pmprompt/claude-plugin-product-management
prd-writer
Generate comprehensive product requirements documents. Use when starting a new feature or product initiative and need structured documentation.
521feature-prioritization-assistant
Calculate RICE scores and prioritize features systematically. Use when building your product roadmap and need to make data-driven prioritization decisions.
266thinking-in-bets
Use when asked to "thinking in bets", "make decisions under uncertainty", "think probabilistically", "avoid resulting", "separate decision quality from outcomes", or "reduce bias in decisions". Helps make explicit bets and evaluate decisions on process, not results. The Thinking in Bets framework (from Annie Duke) applies poker strategy to business and life decisions.
233product-led-growth
Use when asked about "product-led growth", "PLG strategy", "self-serve growth", "freemium model", "free trial design", "product-led sales", "PQL", or "bottoms-up growth". Helps design and optimize product-led growth motions where the product drives acquisition, activation, and monetization. Based on frameworks from Elena Verna and Hila Qu.
212user-feedback-synthesizer
Analyze collections of user feedback to identify patterns and themes. Use when you have user feedback from multiple sources that needs synthesis.
205shape-up
Use when asked to "shape up", "run a shaping session", "set an appetite", "scope a project without estimates", "betting table", or "ship in fixed cycles". Helps teams escape estimate-driven development and Scrum fatigue. The Shape Up method (created by Ryan Singer at Basecamp/37signals) uses fixed time boxes, variable scope, and collaborative shaping to ship meaningful work predictably.
194