
Wwas
Turns product requirements into structured backlog items with Why, What, and Acceptance Criteria sections. You feed it a product name, feature description, design links, and assumptions, and it breaks everything down into sprint-sized work items that connect to business goals. The format keeps stories independent and testable while avoiding the trap of over-specifying implementation details upfront. Honestly most useful when you're tired of backlog items that either say too much or too little. The emphasis on strategic context in the Why section helps teams understand what they're building instead of just following orders.
- skills.sh installs
- 2.8K
- GitHub stars
- 27.8K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add phuryn/pm-skills --skill wwas --agent claude-codeInstalls into .claude/skills of the current project.
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
- 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]
Sponsors
Details
- Repository
- github.com/phuryn/pm-skills
- Categories
- Documentation, Code Review & Quality
- First seen
- May 16, 2026
More from phuryn/pm-skills
All 68- Retro2.8K
- Draft Nda2.8K
- Intended Vs Implemented1.9K
- Shipping Artifacts1.8K
- Create Prd11.1K
- Pre Mortem10.5K
- Prioritization Frameworks10.2K
- Outcome Roadmap10.1K
- Strategy Red Team9.5K
- Competitor Analysis4.1K
- Business Model3.9K
- Privacy Policy3.7K
- Brainstorm Ideas New3.5K
- User Stories3.4K
- Startup Canvas3.4K
- Gtm Strategy3.3K
- Product Name3.3K
- Product Strategy3.3K
- Monetization Strategy3.3K
- Value Proposition3.3K
- Sentiment Analysis3.2K
- Customer Journey Map3.2K
- Summarize Meeting3.2K
- Brainstorm Ideas Existing3.2K