wwas
phuryn/pm-skills
Create structured product backlog items in Why-What-Acceptance format with strategic context and testable outcomes.
What is wwas?
The WWA skill generates independent, valuable backlog items that connect work to business objectives while remaining negotiable and testable. Use it when writing structured backlog items, breaking features into work items, or communicating strategic intent to development teams.
- Define strategic Why statements connecting work to business and team objectives
- Describe concise What sections with design references and implementation context
- Write observable Acceptance Criteria that are testable and verifiable
- Ensure backlog items are independent and deliverable in any order
- Keep items appropriately sized for single-sprint estimation and completion
- Make each item valuable with measurable user or business outcomes
How to install wwas
npx skills add https://github.com/phuryn/pm-skills --skill wwasHow to use wwas
- 1.Gather the product name, feature description, design links, and key strategic assumptions
- 2.Define the Why by connecting the work to business objectives and team goals
- 3.Write a concise What description referencing design files and implementation context
- 4.List 3-4 observable Acceptance Criteria that are testable and verifiable
- 5.Review items for independence—ensure they can be developed in any order
- 6.Verify each item is sized appropriately for one sprint and delivers measurable value
- 7.Share items with the team as conversation starters, not final specifications
Use cases
- Breaking down a new feature into independent backlog items ready for team estimation
- Creating product increments that connect tactical work to strategic business goals
- Writing backlog items for a design handoff with clear acceptance criteria
- Communicating feature scope to stakeholders with strategic context and design references
- Structuring work items that can be developed in parallel by multiple team members
- Product managers writing and refining backlog items
- Development teams breaking down features into sprintable work
- Product owners communicating strategic intent to engineering teams
- Teams adopting or improving user story and backlog practices
wwas FAQ
WWA format emphasizes strategic context (Why), keeps descriptions as reminders rather than specifications (What), and focuses on observable outcomes (Acceptance Criteria). It's designed to be more negotiable and team-collaborative than rigid requirement specifications.
Keep it to 1-2 paragraphs maximum. Include design links and key context, but treat it as a reminder of discussions, not a detailed specification. Detailed specifications should emerge during team conversations.
Yes. Each item should be independent and deliver measurable value on its own. This allows teams to prioritize and parallelize work without blocking dependencies.
Typically 3-4 observable outcomes. They should be testable and verifiable, not detailed technical specifications. Focus on what success looks like from a user or business perspective.
Connect the work to business objectives and team goals in 1-2 sentences. Explain why this work matters strategically, not just what it does functionally.
Full instructions (SKILL.md)
Source of truth, from phuryn/pm-skills.
name: wwas description: "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."
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
Further Reading
Related skills
More from phuryn/pm-skills and the wider catalog.
ab-test-analysis
Analyze A/B test results with statistical significance, confidence intervals, and ship/extend/stop recommendations.
analyze-feature-requests
Analyze and prioritize feature requests by theme, alignment, impact, effort, and risk.
ansoff-matrix
Map growth strategies across market penetration, development, product innovation, and diversification.
beachhead-segment
Identify your first winning market segment using burning pain, willingness to pay, winnability, and referral potential.
app-sizzle
>
app-store-screens
>