Write user stories with AI
Turn a broad feature request into smaller user stories with a named role, a reason for the change and a testable account of what should happen.
Write user stories with AI when a feature heading is too broad to estimate. “Pause a subscription” might involve a subscriber choosing a date, billing stopping and the person seeing when service resumes. The deliver-user-stories skill helps you find pieces that have a recognisable benefit on their own.
Give the agent the requirements you already have. Who can pause a plan? Does the change apply immediately or at renewal? The answers determine whether you have one story or several. A short acceptance example gives a reviewer something to check once the team has built it.
What it does
- Distinguish the person using a feature from the person administering it.
- Split a large request along user-visible outcomes.
- Write the benefit behind each action so the team can discuss its priority.
- Describe acceptance criteria using a starting state, an action and an expected result.
- Review each story for independence, size and testability before planning.
Install and use
- Add the skill to your agent and supply a brief or description of the proposed feature.
- Ask, “Split this subscription pause request into stories for the subscriber.”
- Review the criteria with the team, especially where the brief leaves a business rule open.
FAQ
Source
Made by Jonathan Prisant (Product on Purpose). Original skill: deliver-user-stories, published on GitHub under the Apache-2.0 licence.
View on GitHub