skills.rest
Choi-Keith
Choi-KeithCOMMUNITY
Explore all skills by this author →
GitHub

wwas

Creates product backlog items in Why-What-Acceptance format with strategic context.

Updated Aug 10, 2026
Search Tags:#product management#acceptance criteria#agile#sprint planning#user stories#backlog#wwa
One-click install
npx skills add https://github.com/Choi-Keith/skill-arsenal-ultra --skill wwas-choi-keith
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wwas
Source: https://github.com/Choi-Keith/skill-arsenal-ultra/tree/main/plugins/pm-skills/pm-execution/skills/wwas
Command: npx skills add https://github.com/Choi-Keith/skill-arsenal-ultra --skill wwas-choi-keith

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams often write backlog items that lack strategic context, are too vague to test, or are so interdependent they cannot be scheduled independently. This Skill structures work items using the Why-What-Acceptance (WWA) format so every item is independent, valuable, and testable. ## Core Features & Use Cases - Structured WWA Template: Produces work items with a clear Why (strategic rationale), What (concise description with design links), and Acceptance Criteria (observable outcomes). - INVEST-Style Quality Checks: Guides you to keep items independent, negotiable, valuable, testable, and sized to fit within a single sprint. - Use Case: When breaking a new feature like a real-time spending tracker into sprint-ready work, use this Skill to generate a complete backlog where each item links to business goals, references Figma designs, and lists verifiable acceptance criteria. ## Quick Start Ask the AI to create a WWA backlog for your product and feature, providing the product name, feature description, design links, and key assumptions.

Frequently Asked Questions about wwas

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a product backlog item with acceptance criteria?▼

Use the Why-What-Acceptance format: state the strategic Why in one or two sentences, describe the What briefly with design links, then list observable acceptance criteria. Keep the item independent and small enough to estimate within one sprint.

What is the WWA format for user stories?▼

WWA stands for Why-What-Acceptance, a backlog item structure that connects work to business goals (Why), summarizes the deliverable with design references (What), and defines high-level observable outcomes (Acceptance) rather than detailed specifications.

How detailed should acceptance criteria be in a backlog item?▼

Acceptance criteria should stay high-level and describe observable, verifiable outcomes rather than detailed specifications. Detailed specs emerge through team conversation during development, keeping the item negotiable.

When should I split a feature into multiple work items?▼

Split a feature when items cannot be completed within a single sprint or when parts can be delivered independently. Each resulting item should still deliver measurable user or business value on its own.

What is the difference between WWA items and traditional user stories?▼

WWA items emphasize strategic context through an explicit Why section and keep the What section as a discussion memo rather than a full specification. Traditional user stories often focus on the role-goal-benefit phrasing without mandatory acceptance criteria.

Related Skills

Explore More Product & Management Skills→
clovernguyen1010-ship-itclovernguyen1010-ship-it

bmad-agent-pm

Guide user interviews and requirements discovery to draft PRDs.

Community
Intermediate
adawadaw

fabric-sprint

Generate a sprint plan from a prioritized backlog with WIP limits and capacity.

Community
Advanced
runchr-comrunchr-com

wwas

Generate product backlog items in the Why-What-Acceptance format.

Official
Intermediate
jupitermoneyjupitermoney

prd-to-epics

Convert PRDs into Jira-ready Epics and Stories with acceptance criteria.

Official
Intermediate