wwas

Generates backlog items in the Wish,What,Acceptance format.

25.0k|2.7k|Updated Mar 1, 2026

Search Tags:#product management #agile #user stories #backlog #feature breakdown #wwas

Ready to run

npx skills add https://github.com/phuryn/pm-skills --skill wwas-phuryn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wwas
Source: https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/wwas
Command: npx skills add https://github.com/phuryn/pm-skills --skill wwas-phuryn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation of product backlog items by ensuring they are well-defined, independent, valuable, and testable, complete with strategic context.

Core Features & Use Cases

Structured Item Creation: Generates backlog items in the Why-What-Acceptance (WWA) format.
Strategic Alignment: Ensures each item clearly links back to business and team objectives.
Use Case: When breaking down a large feature into smaller, manageable tasks for a development sprint, use this Skill to ensure each task is clearly defined with its purpose, description, and acceptance criteria.

Quick Start

Use the wwas skill to create a product backlog item for a new spending tracker feature, linking to Figma designs and providing 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 structured product backlog items for agile development?▼

Generate product backlog items using the Why-What-Acceptance (WWA) format to ensure each item is independent, valuable, and testable. This structure provides clear strategic context for development teams.

What is the WWA format for user stories?▼

The WWA format structures user stories into Why, What, and Acceptance criteria components. It ensures backlog items are well-defined, independent, valuable, testable, and aligned with strategic business objectives.

How do I break down a large feature into manageable work items for a sprint?▼

Break down large features into manageable sprint work items by generating each task using the WWA format. This ensures every decomposed work item has a clearly defined purpose, description, and acceptance criteria.

How to communicate strategic intent to a development team through backlog items?▼

Communicate strategic intent by formatting backlog items using the WWA template, explicitly linking the Why component to team and business objectives. This provides the development team with necessary strategic context.

Do I need specific dependencies to generate agile backlog items in this format?▼

No specific dependencies are required to generate agile backlog items in the WWA format. You only need to provide the feature context, key assumptions, and relevant references like design links for output generation.