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.
npx skills add https://github.com/phuryn/pm-skills --skill wwas