wwas
Scannednpx machina-cli add skill phuryn/pm-skills/wwas --openclawWhy-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
- Define the strategic Why - Connect work to business and team objectives
- Describe the What - Keep descriptions concise, reference designs
- Write Acceptance Criteria - High-level, not detailed specifications
- Ensure independence - Items can be developed in any order
- Keep items negotiable - Invite team conversation, not constraints
- Make items valuable - Each delivers measurable user or business value
- Ensure testability - Outcomes are observable and verifiable
- 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
Source
git clone https://github.com/phuryn/pm-skills/blob/main/pm-execution/skills/wwas/SKILL.mdView on GitHub Overview
Why-What-Acceptance (WWA) is a backlog-item format that binds work to strategy by explicitly stating Why, What, and Acceptance Criteria. Items are independent, valuable, and testable, with strategic context to guide prioritization and design references. Use WWA to structure backlog items, break features into work items, or communicate strategic intent to teams.
How This Skill Works
WWA starts with a strategic Why, followed by a concise What that references designs, then high-level Acceptance Criteria. Each item should be independent, negotiable, valuable, and observable for testability. Size items to be deliverable in a single sprint and include a design link and assumptions when relevant.
When to Use It
- Writing structured backlog items for new features
- Creating product increments and breaking features into work items
- Communicating strategic intent to development teams
- Planning work that must be independent and reorderable
- Documenting design references and assumptions for future discussions
Quick Start
- Step 1: Define the Why—link to strategic objective and team goals
- Step 2: Write the What—short description plus design reference link
- Step 3: Draft Acceptance Criteria and confirm item is independent and testable
Best Practices
- Start with a clear strategic Why aligned to business objectives
- Keep What concise and reference linked designs (e.g., Figma, Miro)
- Ensure each item is independent and can be developed in any order
- Make Acceptance Criteria observable and testable
- Size items so they can be completed in one sprint and remain negotiable
Example Use Cases
- Implement Real-Time Spending Tracker
- Enable User Profile Avatar Upload with design reference
- Introduce Feature Flags to support A/B testing
- Create Centralized Notification Center for product increments
- Integrate Design System Tokens across new components
