wwas

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

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/runchr-com/pm-skills-gemini --skill wwas-runchr-com
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wwas
Source: https://github.com/runchr-com/pm-skills-gemini/tree/main/.gemini/skills/wwas
Command: npx skills add https://github.com/runchr-com/pm-skills-gemini --skill wwas-runchr-com

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, valuable, and strategically aligned, reducing ambiguity for development teams.

Core Features & Use Cases

  • Structured Item Creation: Generates backlog items in the Why-What-Acceptance (WWA) format.
  • Strategic Alignment: Ensures each item clearly links to business objectives.
  • Developer Clarity: Provides concise descriptions and testable acceptance criteria.
  • Use Case: When breaking down a new feature like "User Profile Redesign" into manageable tasks, use this Skill to create WWA items for "Update profile picture functionality" and "Implement editable bio section."

Quick Start

Create a WWA item for the feature 'Real-Time Spending Tracker' for the product 'BudgetApp', linking to Figma designs and noting 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?

To write structured product backlog items, generate them in the Why-What-Acceptance format to ensure each item is independent, valuable, and testable with clear strategic context for development teams.

What is the Why-What-Acceptance format for user stories?

The Why-What-Acceptance format for user stories breaks down features by defining the strategic business rationale, the specific functional requirements, and the clear testable acceptance criteria for developers.

What information do I need to generate backlog items in the WWA format?

To generate WWA backlog items, you need to provide the product name, a feature description, design links, and key assumptions to produce structured and strategically aligned output.

How do I break down a product feature into actionable user stories?

Break down a product feature into actionable user stories by feeding the feature description and design links into a WWA generator to output independent, testable work items for the development backlog.

Does this approach to requirements generation support agile product management workflows?

Yes, WWA backlog item generation supports agile product management by taking feature assumptions and designs to produce concise, testable requirements that reduce ambiguity for development teams.

What is the best way to ensure backlog items are testable and strategically aligned?

The best way to ensure backlog items are testable and strategically aligned is to structure them using the Why-What-Acceptance format, linking each actionable work item directly to business objectives.