wwas

1# Why-What-Acceptance (WWA)
2 
3Create product backlog items in Why-What-Acceptance format. Produces independent, valuable, testable items with strategic context.
4 
5**Use when:** Writing backlog items, creating product increments, breaking features into work items, or communicating strategic intent to teams.
6 
7**Arguments:**
8- `$PRODUCT`: The product or system name
9- `$FEATURE`: The new feature or capability
10- `$DESIGN`: Link to design files (Figma, Miro, etc.)
11- `$ASSUMPTIONS`: Key assumptions and strategic context
12 
13## Step-by-Step Process
14 
151. **Define the strategic Why** - Connect work to business and team objectives
162. **Describe the What** - Keep descriptions concise, reference designs
173. **Write Acceptance Criteria** - High-level, not detailed specifications
184. **Ensure independence** - Items can be developed in any order
195. **Keep items negotiable** - Invite team conversation, not constraints
206. **Make items valuable** - Each delivers measurable user or business value
217. **Ensure testability** - Outcomes are observable and verifiable
228. **Size appropriately** - Small enough for one sprint estimate
23 
24## Item Template
25 
26**Title:** [What will be delivered]
27 
28**Why:** [1-2 sentences connecting to strategic context and team objectives]
29 
30**What:** [Short description and design link. 1-2 paragraphs maximum. A reminder of discussion, not detailed specification.]
31 
32**Acceptance Criteria:**
33- [Observable outcome 1]
34- [Observable outcome 2]
35- [Observable outcome 3]
36…