wwas
This Claude Code skill creates structured product backlog items using the Why-What-Acceptance format, which connects strategic business context to concrete deliverables and testable outcomes. Use it when drafting backlog items, decomposing features into sprint-ready work, or ensuring teams understand both the reasoning and acceptance criteria for development tasks.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/wwas && cp -r /tmp/wwas/pm-execution/skills/wwas ~/.claude/skills/wwasSKILL.md
# Why-What-Acceptance (WWA) Create product backlog items in Why-What-Acceptance format. Produces independent, valuable, testable items with strategic context. **Use when:** Writing backlog items, creating product increments, breaking features into work items, or communicating strategic intent to teams. **Arguments:** - `$PRODUCT`: The product or system name - `$FEATURE`: The new feature or capability - `$DESIGN`: Link to design files (Figma, Miro, etc.) - `$ASSUMPTIONS`: Key assumptions and strategic context ## Step-by-Step Process 1. **Define the strategic Why** - Connect work to business and team objectives 2. **Describe the What** - Keep descriptions concise, reference designs 3. **Write Acceptance Criteria** - High-level, not detailed specifications 4. **Ensure independence** - Items can be developed in any order 5. **Keep items negotiable** - Invite team conversation, not constraints 6. **Make items valuable** - Each delivers measurable user or business value 7. **Ensure testability** - Outcomes are observable and verifiable 8. **Size appropriately** - Small enough for one sprint estimate ## Item Template **Title:** [What will be delivered] **Why:** [1-2 sentences connecting to strategic context and team objectives] **What:** [Short description and design link. 1-2 paragraphs maximum. A reminder of discussion, not detailed specification.] **Acceptance Criteria:** - [Observable outcome 1] - [Observable outcome 2] - [Observable outcome 3] - [Observable outcome 4] ## Example WWA Item **Title:** Implement Real-Time Spending Tracker **Why:** Users need immediate feedback on spending to make conscious budget decisions. This directly supports our goal to improve financial awareness and reduce overspending. **What:** Add a real-time spending tracker that updates as users log expenses. The tracker displays their current week's spending against their set budget. Designs available in [Figma link]. This is a reminder of our discussions - detailed specifications will emerge during development conversations with the team. **Acceptance Criteria:** - Spending totals update within 2 seconds of logging an expense - Budget progress is visually indicated with a progress bar - Users can see remaining budget amount at a glance - System handles multiple expense categories correctly ## Output Deliverables - Complete set of backlog items for the feature - Each item includes Why, What, and Acceptance Criteria sections - Items are independent and deliverable in any order - Items are sized for estimation and completion in one sprint - Strategic context is clear for team decision-making - Design references are included for implementation guidance --- ### Further Reading - [How to Write User Stories: The Ultimate Guide](https://www.productcompass.pm/p/how-to-write-user-stories)
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.
Identify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.
Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
Design lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.
Brainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.
Brainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.