wwas

Name: wwas
Author: phuryn

1.7kinstalls2.5kforks

How to install wwas?

phuryn/pm-skills/wwas

$npx -y skills add phuryn/pm-skills --skill wwas

Installs into the current project.

Summary

Create product backlog items in Why-What-Acceptance format — independent, valuable, testable items with strategic context. Use when writing structured backlog items, breaking features into work items, or using the WWA format.

Files · 1

View on GitHub

SKILL.md

1	# Why-What-Acceptance (WWA)
2
3	Create 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
15	1. Define the strategic Why - Connect work to business and team objectives
16	2. Describe the What - Keep descriptions concise, reference designs
17	3. Write Acceptance Criteria - High-level, not detailed specifications
18	4. Ensure independence - Items can be developed in any order
19	5. Keep items negotiable - Invite team conversation, not constraints
20	6. Make items valuable - Each delivers measurable user or business value
21	7. Ensure testability - Outcomes are observable and verifiable
22	8. 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	- [Observable outcome 4]
37
38	## Example WWA Item
39
40	Title: Implement Real-Time Spending Tracker
41
42	Why: Users need immediate feedback on spending to make conscious budget decisions. This directly supports our goal to improve financial awareness and reduce overspending.
43
44	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.
45
46	Acceptance Criteria:
47	- Spending totals update within 2 seconds of logging an expense
48	- Budget progress is visually indicated with a progress bar
49	- Users can see remaining budget amount at a glance
50	- System handles multiple expense categories correctly
51
52	## Output Deliverables
53
54	- Complete set of backlog items for the feature
55	- Each item includes Why, What, and Acceptance Criteria sections
56	- Items are independent and deliverable in any order
57	- Items are sized for estimation and completion in one sprint
58	- Strategic context is clear for team decision-making
59	- Design references are included for implementation guidance
60
61	---
62
63	### Further Reading
64
65	- [How to Write User Stories: The Ultimate Guide](https://www.productcompass.pm/p/how-to-write-user-stories)

People who liked this also viewed

6 picks

Type

wwas

1.7kinstalls2.5kforks

View on GitHub

How to install wwas?

phuryn/pm-skills/wwas

$npx -y skills add phuryn/pm-skills --skill wwas

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Why-What-Acceptance (WWA)
2
3	Create 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
15	1. Define the strategic Why - Connect work to business and team objectives
16	2. Describe the What - Keep descriptions concise, reference designs
17	3. Write Acceptance Criteria - High-level, not detailed specifications
18	4. Ensure independence - Items can be developed in any order
19	5. Keep items negotiable - Invite team conversation, not constraints
20	6. Make items valuable - Each delivers measurable user or business value
21	7. Ensure testability - Outcomes are observable and verifiable
22	8. 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	- [Observable outcome 4]
37
38	## Example WWA Item
39
40	Title: Implement Real-Time Spending Tracker
41
42	Why: Users need immediate feedback on spending to make conscious budget decisions. This directly supports our goal to improve financial awareness and reduce overspending.
43
44	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.
45
46	Acceptance Criteria:
47	- Spending totals update within 2 seconds of logging an expense
48	- Budget progress is visually indicated with a progress bar
49	- Users can see remaining budget amount at a glance
50	- System handles multiple expense categories correctly
51
52	## Output Deliverables
53
54	- Complete set of backlog items for the feature
55	- Each item includes Why, What, and Acceptance Criteria sections
56	- Items are independent and deliverable in any order
57	- Items are sized for estimation and completion in one sprint
58	- Strategic context is clear for team decision-making
59	- Design references are included for implementation guidance
60
61	---
62
63	### Further Reading
64
65	- [How to Write User Stories: The Ultimate Guide](https://www.productcompass.pm/p/how-to-write-user-stories)

People who liked this also viewed

6 picks

Type