Wwas
- 1.9k installs
- 24.9k repo stars
- Updated July 3, 2026
- phuryn/pm-skills
The wwas skill from phuryn pm-skills creates product backlog items using Why-What-Acceptance structure linking strategic rationale, deliverable scope, and testable acceptance criteria.
About
The wwas skill from phuryn pm-skills creates product backlog items using Why-What-Acceptance structure linking strategic rationale, deliverable scope, and testable acceptance criteria. Each item must stand alone with clear user or business value, explicit outcomes, and verifiable conditions rather than task lists. Agents help translate vague feature requests into WWA items suitable for sprint planning and stakeholder review. The format preserves context for why work matters while keeping acceptance testable for QA and engineering. Use when writing structured backlog entries, breaking features into work items, or standardizing item quality before estimation sessions. Why-What-Acceptance format for backlog items. Emphasizes independent, valuable, testable slices. Captures strategic why before what and acceptance. Converts vague requests into sprint-ready items. Supports estimation and stakeholder review quality. Write backlog items in Why-What-Acceptance format as independent, valuable, testable units with strategic context.
- Why-What-Acceptance format for backlog items.
- Emphasizes independent, valuable, testable slices.
- Captures strategic why before what and acceptance.
- Converts vague requests into sprint-ready items.
- Supports estimation and stakeholder review quality.
Wwas by the numbers
- 1,861 all-time installs (skills.sh)
- +80 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #273 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
wwas capabilities & compatibility
- Capabilities
- why what acceptance format for backlog items. · emphasizes independent, valuable, testable slice · captures strategic why before what and acceptanc · converts vague requests into sprint ready items.
- Use cases
- planning · project management
What wwas says it does
Create product backlog items in Why-What-Acceptance format — independent, valuable, testable items with strategic context.
npx skills add https://github.com/phuryn/pm-skills --skill wwasAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.9k |
|---|---|
| repo stars | ★ 24.9k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 3, 2026 |
| Repository | phuryn/pm-skills ↗ |
How do I apply wwas for the workflow described in SKILL.md?
Write backlog items in Why-What-Acceptance format as independent, valuable, testable units with strategic context.
Who is it for?
Teams using wwas as documented in the skill repository.
Skip if: Tasks outside the wwas scope defined in SKILL.md.
When should I use this skill?
User mentions wwas or related skill triggers from the description.
What you get
Structured deliverables and steps from the wwas skill workflow.
- WWA backlog items
By the numbers
- WWA format uses 3 sections: Why, What, Acceptance
Files
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
1. Define the strategic Why - Connect work to business and team objectives 2. Describe the What - Keep descriptions concise, reference designs 3. Write Acceptance Criteria - High-level, not detailed specifications 4. Ensure independence - Items can be developed in any order 5. Keep items negotiable - Invite team conversation, not constraints 6. Make items valuable - Each delivers measurable user or business value 7. Ensure testability - Outcomes are observable and verifiable 8. 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
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kFAQ
What does wwas do?
Write backlog items in Why-What-Acceptance format as independent, valuable, testable units with strategic context.
When should I invoke wwas?
Use when you need Write backlog items in Why-What-Acceptance format as independent, valuable, testable units with strategic context.
What outcome does wwas produce?
The wwas skill from phuryn pm-skills creates product backlog items using Why-What-Acceptance structure linking strategic rationale, deliverable scope, and testable acceptance criteria.
Is Wwas safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.