wwas

Create Why-What-Acceptance backlog items with titles, criteria, and design references.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/martiraste-lgtm/claude-skills --skill wwas-martiraste-lgtm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wwas
Source: https://github.com/martiraste-lgtm/claude-skills/tree/main/pm-execution-wwas
Command: npx skills add https://github.com/martiraste-lgtm/claude-skills --skill wwas-martiraste-lgtm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Why-What-Acceptance (WWA) framework helps product teams convert vague ideas into structured, independent backlog items with strategic context and clear testable outcomes.

Core Features & Use Cases

  • Why-What-Acceptance: Formats backlog items to include Why, What, and Acceptance Criteria, promoting alignment and testability.
  • Independence & Value: Ensures items can be developed in any order and deliver measurable business value.
  • Output & References: Provides a consistent template with optional references to designs and design links to guide implementation.
  • Use Case: When breaking a feature into work items, create a backlog that is actionable in a single sprint with clear acceptance conditions.

Quick Start

Provide a product backlog item set for a new feature by giving product name, feature, design link, and assumptions.

Frequently Asked Questions about wwas

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

FAQPage Schema
How do I write agile backlog items with clear acceptance criteria?

Agile backlog items need structured context to be actionable. The WWA framework formats each item with a Title, Why, What, and Acceptance Criteria, ensuring independence, measurable value, and testability within a single sprint.

What is the Why-What-Acceptance framework for product management?

The Why-What-Acceptance framework is a product management method that converts vague ideas into structured backlog items. It separates strategic context from functional requirements and testable outcomes to promote team alignment.

How to break down a product feature into independent backlog items?

To break down a product feature into independent backlog items, apply the WWA framework to ensure each work item can be developed in any order. Provide the feature name, design link, and assumptions to generate a structured, actionable backlog.

Does the WWA framework work for features without finalized design files?

The WWA framework supports features without finalized design files by treating design references as optional. You can generate backlog items with clear acceptance criteria using only product assumptions and feature descriptions.

What is the best way to structure vague product ideas for sprint planning?

The best way to structure vague ideas for sprint planning is using the WWA template. It enforces independence and testability by requiring a Title, Why, What, and Acceptance Criteria, transforming abstract concepts into valuable, actionable work items.