Create product backlog items in Why-What-Acceptance format with strategic context and testable criteria.
npx skills add https://github.com/moonzff/Codex_up --skill wwas-moonzff
Please help me install this Agent Skill. Skill: wwas Source: https://github.com/moonzff/Codex_up/tree/main/skills/global-installed/wwas Command: npx skills add https://github.com/moonzff/Codex_up --skill wwas-moonzff
High-intent search queries and answers about installing and using this skill.
Provide the product name, feature description, design reference link, and strategic context. The output is a set of items each containing a Why section tied to business objectives, a concise What section, and observable acceptance criteria.
WWA stands for Why-What-Acceptance, a backlog item structure where Why connects work to strategy, What briefly describes the deliverable with design links, and Acceptance Criteria list observable outcomes rather than detailed specifications.
Acceptance criteria should be high-level observable outcomes, not detailed specifications. Typically 3-4 criteria per item, such as measurable response times or visible UI states, leaving detailed decisions to team conversations during development.
WWA is less suitable for purely technical tasks, bugs, or spikes with no user-facing value, since the Why section assumes strategic or business context. It also requires design references and strategic inputs to produce meaningful items.
Yes, the format explicitly requires independence, meaning each item can be developed and delivered in any order. Items are also sized to be estimable and completable within a single sprint.
marcocelloGather authoritative external evidence to resolve product, domain, library, or API uncertainties.
OntoLedgyPlan executable sprints by ordering prioritized tickets into dependency-aware waves.
nesnilnehcMap backlog items to strategic anchors and generate a Backlog Alignment Report.
SmidigStormGenerate Gherkin Given-When-Then scenarios and feature files for BDD.
