skills.rest
tom-xs
tom-xsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

deliver-user-stories

Generate user stories in persona, action, benefit format with acceptance criteria.

Updated Nov 22, 2025
Search Tags:#product management#acceptance criteria#agile#sprint planning#user stories#backlog
One-click install
npx skills add https://github.com/tom-xs/nixos-dotfiles --skill deliver-user-stories-tom-xs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deliver-user-stories
Source: https://github.com/tom-xs/nixos-dotfiles/tree/main/ai/kimi-skills/skills/deliver-user-stories
Command: npx skills add https://github.com/tom-xs/nixos-dotfiles --skill deliver-user-stories-tom-xs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the challenge of translating high-level product requirements into actionable, estimable, and testable user stories, ensuring engineering teams have clear user-centric goals.

Core Features & Use Cases

  • Standardized Formatting: Automatically applies the Persona-Action-Benefit structure to feature descriptions.
  • INVEST Validation: Ensures stories are Independent, Negotiable, Valuable, Estimable, Small, and Testable.
  • Use Case: When you have a rough feature description for a new checkout flow, use this skill to break it down into specific, sprint-ready tickets with clear acceptance criteria.

Quick Start

Use the deliver-user-stories skill to generate user stories for the new bulk-export feature based on the provided product requirements.

Frequently Asked Questions about deliver-user-stories

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate user stories from product requirements for sprint planning?▼

You generate user stories by structuring product requirements into the persona, action, and benefit format, ensuring they are INVEST-compliant with Given/When/Then acceptance criteria and technical context for sprint-ready tickets.

What is the standard format for writing agile user stories with acceptance criteria?▼

The standard format structures agile user stories using persona, action, and benefit components, validated by INVEST principles, and includes Given/When/Then acceptance criteria to ensure clear scope communication and testability.

How do I ensure my backlog user stories are INVEST compliant?▼

You ensure backlog user stories are INVEST compliant by validating that each generated story is Independent, Negotiable, Valuable, Estimable, Small, and Testable during the translation from high-level product requirements.

Can I use feature descriptions to create testable tickets for my development team?▼

Yes, feature descriptions can be transformed into testable tickets by generating INVEST-compliant user stories that include Given/When/Then acceptance criteria, providing engineering teams with actionable and testable user-centric goals.

What is the best way to break down a rough checkout flow feature into sprint-ready tickets?▼

The best way to break down a rough checkout flow feature into sprint-ready tickets is to translate the product requirements into INVEST-compliant user stories using the persona, action, and benefit format with clear Given/When/Then acceptance criteria.

Related Skills

Explore More Product & Management Skills→
gabbellogabbello

spdd-story

Decompose feature requirements into INVEST-compliant development stories.

Community
Advanced
alex-tgkalex-tgk

agile-product-owner

Generate INVEST-compliant user stories with acceptance criteria from epics.

Community
Intermediate
zhizhunbaozhizhunbao

dev-scrum

Generate sprint backlogs, user stories, and task breakdowns from PRD requirements.

Community
Advanced
QuestNova502QuestNova502
4

agile-product-owner

Generate INVEST-compliant user stories and sprint plans from epics.

Community
Advanced