Description
wwas is an agent skill that writes product backlog items in the Why, What, Acceptance format. Each item gives the strategic reason for the work, the thing being built, and the acceptance criteria that show it is done, and the items are meant to be independent, valuable and testable. It is useful when writing backlog items, creating product increments, breaking a feature into work items, or passing strategic intent to a development team. You provide the product name, the feature, design links and key assumptions with their strategic context, and the skill writes the items. Keeping the why next to the what helps a team see when a piece of work no longer serves the goal. The skill is part of the pm-skills collection by phuryn and is listed on skills.sh as free.…
Highlights
- Backlog items in the Why, What, Acceptance format
- Items are independent, valuable and testable
- Keeps the strategic reason next to the work
- Breaks features into work items for teams
Ratings & Reviews
No ratings yet
Be the first to rate wwas.
People also visit
prioritize-features
Prioritize a backlog of feature ideas based on impact, effort, risk
feature-forge
Conducts structured requirements workshops to produce feature specifications
dev-team
Simulate a collaborative dev team session where multiple role-based personas
wwas FAQ
What format does wwas use?
Why the work matters, what is being built, and the acceptance criteria.
What makes an item good?
The skill aims for items that are independent, valuable and testable.
What do I provide?
The product, the feature, design links and key assumptions.
Who is it for?
Product managers and owners writing backlog items for development teams.
How do I install it?
Run npx skills add https://github.com/phuryn/pm-skills --skill wwas in your terminal.
Is it free?
The listing shows the skill as free.
What are the best wwas alternatives?
Popular alternatives to wwas include user-stories, bmad-create-epics-and-stories and job-stories. See all wwas alternatives