wwas
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.
npx skills add phuryn/pm-skills --skill wwas --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 t
- Step-by-Step Process
- Item Template
- Example WWA Item
- Output Deliverables
- Further Reading
What does the wwas skill do?
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.
How do I install it?
Run `npx skills add phuryn/pm-skills --skill wwas --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From phuryn/pm-skills, a repository with 24,843 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.