What problem does it solve? Requirements often degrade into task lists disguised as user stories, like "Add login feature" or "As a user, I want a button," which describe what to build instead of who needs what and why. This Skill frames stories around real personas and validated needs so teams build for actual user value. ## Core Features & Use Cases - Story framing and critique: Writes or reviews stories using the who/what/why structure, keeping them small, INVEST-compliant, and testable with acceptance criteria. - Story mapping: Connects problem, functionality, user stories, and tasks so every requirement traces back to a real user need. - Gated decisions: Surfaces context-dependent trade-offs such as strict formula vs. free-form, whether to write a story at all, and acceptance-criteria depth. - Use Case: A product manager turns a research-grounded persona's frustration into a sprint-ready story with acceptance criteria, then maps it across the customer journey before handing it to the spec. ## Quick Start Ask the assistant to write a user story for a specific persona and need, for example by requesting a story for a returning user who wants to log in quickly to access saved data.
