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)
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
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.
Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.
Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded diagrams or documentation. Use when writing SQL, building data reports, exploring databases, or translating business questions into queries.
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.