wwas produces backlog items in the Why-What-Acceptance format. Each item has a title, a Why that ties the work to strategy and team objectives, a What that is a short description with a design link, and acceptance criteria written as observable outcomes.
Items are meant to be independent, negotiable, valuable, testable and small enough for one sprint estimate, and the What is a reminder of a team discussion, not a detailed specification.
What You Get
- A set of backlog items for the feature
- A Why section with strategic context for each
- A What section of one or two paragraphs with the design link
- High-level, observable acceptance criteria
- Items that can be built in any order and fit one sprint
Common Use Cases
- Communicating strategic intent to a team through backlog items
- Splitting a feature into independent work items
- Writing items that invite conversation
What Makes It Unique
The Why comes first, so every item carries its strategic reason, and the What is kept short on purpose so detailed specifications emerge from conversation. Acceptance criteria stay high-level.
Under The Hood
The skill is one SKILL.md of instructions with no scripts. It takes the product, feature, design link and assumptions as arguments and writes the items in its reply. The design link is placed in the item text and is not fetched.