Wwas

From the author

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.

— the description by Pawel Huryn

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The wwas skill provides a structured framework for creating product backlog items that prioritize strategic alignment and clarity. By utilizing the Why-What-Acceptance (WWA) format, it ensures that every work item is independent, valuable, and testable. This approach helps product managers and teams communicate intent effectively, connecting technical tasks to broader business objectives while maintaining flexibility for team collaboration.

What it does

Generates backlog items structured with Why, What, and Acceptance Criteria sections.
Connects development tasks to strategic business and team objectives.
Integrates design references directly into the backlog item description.
Ensures items are sized appropriately for sprint-based estimation.
Promotes the creation of independent and testable work units.
Facilitates team communication by keeping descriptions negotiable.

When to use it

When writing new backlog items for a product or system.
When breaking down large features into smaller, manageable work items.
When you need to communicate strategic intent to a development team.
When creating product increments that require clear, observable outcomes.
When you want to move away from overly detailed specifications toward collaborative development.

Advantages

Improves team understanding of the strategic 'why' behind technical tasks.
Reduces ambiguity by providing clear, observable acceptance criteria.
Encourages team discussion rather than rigid, top-down specifications.
Ensures all backlog items deliver measurable user or business value.
Facilitates easier sprint planning through appropriately sized items.

Usage examples

“Create a WWA backlog item for a new user authentication feature for our mobile app.”: The agent generates a structured item including the strategic reason for the feature, a concise description with a placeholder for design links, and a list of observable acceptance criteria.
“Break down the 'Checkout Process' feature into WWA items for the team.”: The agent produces a set of independent, sprint-sized backlog items for the checkout flow, each containing the necessary Why, What, and Acceptance Criteria.

Install

Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/phuryn/wwas/download
Unzip it into the cross-client skills folder of your project:
```
mkdir -p .agents/skills && unzip wwas.zip -d .agents/skills
```

Documentation by Pawel Huryn

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

Define the strategic Why - Connect work to business and team objectives
Describe the What - Keep descriptions concise, reference designs
Write Acceptance Criteria - High-level, not detailed specifications
Ensure independence - Items can be developed in any order
Keep items negotiable - Invite team conversation, not constraints
Make items valuable - Each delivers measurable user or business value
Ensure testability - Outcomes are observable and verifiable
Size appropriately - Small enough for one sprint estimate

Item Template

Title: [What will be delivered]

Why: [1-2 sentences connecting to strategic context and team objectives]

What: [Short description and design link. 1-2 paragraphs maximum. A reminder of discussion, not detailed specification.]

Acceptance Criteria:

[Observable outcome 1]
[Observable outcome 2]
[Observable outcome 3]
[Observable outcome 4]

Example WWA Item

Title: Implement Real-Time Spending Tracker

Why: Users need immediate feedback on spending to make conscious budget decisions. This directly supports our goal to improve financial awareness and reduce overspending.

What: Add a real-time spending tracker that updates as users log expenses. The tracker displays their current week's spending against their set budget. Designs available in [Figma link]. This is a reminder of our discussions - detailed specifications will emerge during development conversations with the team.

Acceptance Criteria:

Spending totals update within 2 seconds of logging an expense
Budget progress is visually indicated with a progress bar
Users can see remaining budget amount at a glance
System handles multiple expense categories correctly

Output Deliverables

Complete set of backlog items for the feature
Each item includes Why, What, and Acceptance Criteria sections
Items are independent and deliverable in any order
Items are sized for estimation and completion in one sprint
Strategic context is clear for team decision-making
Design references are included for implementation guidance

Files

ATTRIBUTION.mdAdded by AutoGineer840 B
LICENSELicence file added by AutoGineer1.0 KiB
SKILL.md3.0 KiB

SKILL.md

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

Define the strategic Why - Connect work to business and team objectives
Describe the What - Keep descriptions concise, reference designs
Write Acceptance Criteria - High-level, not detailed specifications
Ensure independence - Items can be developed in any order
Keep items negotiable - Invite team conversation, not constraints
Make items valuable - Each delivers measurable user or business value
Ensure testability - Outcomes are observable and verifiable
Size appropriately - Small enough for one sprint estimate

Item Template

Title: [What will be delivered]

Why: [1-2 sentences connecting to strategic context and team objectives]

What: [Short description and design link. 1-2 paragraphs maximum. A reminder of discussion, not detailed specification.]

Acceptance Criteria:

[Observable outcome 1]
[Observable outcome 2]
[Observable outcome 3]
[Observable outcome 4]

Example WWA Item

Title: Implement Real-Time Spending Tracker

Why: Users need immediate feedback on spending to make conscious budget decisions. This directly supports our goal to improve financial awareness and reduce overspending.

What: Add a real-time spending tracker that updates as users log expenses. The tracker displays their current week's spending against their set budget. Designs available in [Figma link]. This is a reminder of our discussions - detailed specifications will emerge during development conversations with the team.

Acceptance Criteria:

Spending totals update within 2 seconds of logging an expense
Budget progress is visually indicated with a progress bar
Users can see remaining budget amount at a glance
System handles multiple expense categories correctly

Output Deliverables

Complete set of backlog items for the feature
Each item includes Why, What, and Acceptance Criteria sections
Items are independent and deliverable in any order
Items are sized for estimation and completion in one sprint
Strategic context is clear for team decision-making
Design references are included for implementation guidance

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Marketing Plan
Corey Haines· Community
Generates a comprehensive, executable 12-month marketing plan structured by the AARRR framework for fractional CMOs and founders.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 more
MITLow riskGitHub stars of the source repository59k
Revops
Corey Haines· Community
Expert guidance for designing and optimizing revenue operations, lead lifecycle management, and marketing-to-sales handoff processes.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository59k
Ab Testing
Corey Haines· Community
A comprehensive framework for planning, executing, and analyzing statistically rigorous A/B tests and growth experimentation programs.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository59k
Pricing
Corey Haines· Community
Expert guidance on SaaS pricing strategy, packaging, monetization, and auditing pricing pages for human and AI-agent readability.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository59k
Community Marketing
Corey Haines· Community
A strategic framework for building and managing online communities to drive product growth, brand loyalty, and user engagement.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository59k
Paywalls
Corey Haines· Community
Expert guidance for designing and optimizing in-app upgrade flows, paywalls, and feature gates to maximize conversion.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository59k

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download wwas.zip

From the author