# Wwas

Create product backlog items in Why-What-Acceptance format, independent, valuable...

- Repository: https://github.com/phuryn/pm-skills (27597 stars)
- Category: Writing
- License: MIT
- Last updated: 2026-10-29
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add phuryn/pm-skills --skill wwas -g -a claude-code -y`
Codex: `npx skills add phuryn/pm-skills --skill wwas -g -a codex -y`
Cursor: `npx skills add phuryn/pm-skills --skill wwas -g -a cursor -y`
Gemini CLI: `npx skills add phuryn/pm-skills --skill wwas -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add phuryn/pm-skills`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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.

The rest: https://github.com/phuryn/pm-skills/blob/HEAD/pm-execution/skills/wwas/SKILL.md