deliver-user-stories

Generate user stories with testable acceptance criteria from product requirements.

Updated May 20, 2026
One-click install
npx skills add https://github.com/richardnguyen0715/ai-chatting-app --skill deliver-user-stories-richardnguyen0715
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deliver-user-stories
Source: https://github.com/richardnguyen0715/ai-chatting-app/tree/main/.github/skills/deliver-user-stories
Command: npx skills add https://github.com/richardnguyen0715/ai-chatting-app --skill deliver-user-stories-richardnguyen0715

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the process of crafting user stories, ensuring clear acceptance criteria and efficient product requirements communication.

Core Features & Use Cases

  • User Story Creation: Guided steps to create concise, actionable user stories.
  • Feature Decomposition: Break down features into distinct user goals.
  • Acceptance Criteria: Define testable criteria for each story.
  • INVEST Criteria: Validate stories against Independent, Negotiable, Valuable, Estimable, Small, Testable standards.
  • Use Case: Ideal for product managers to translate high-level requirements into executable tasks for engineering teams.

Quick Start

Generate user stories from the feature description in 'feature-description.txt'.

Frequently Asked Questions about deliver-user-stories

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

FAQPage Schema
How do I write user stories with clear acceptance criteria from product requirements?

To write user stories with clear acceptance criteria, decompose high-level product features into distinct user goals and translate them into actionable tasks. This process identifies user personas and defines testable conditions to ensure user-centric functionality for sprint planning.

What are INVEST criteria for validating user stories in sprint planning?

INVEST criteria validate that user stories are Independent, Negotiable, Valuable, Estimable, Small, and Testable. Checking stories against these standards ensures they are properly sized and structured for efficient sprint planning and engineering execution.

How do I break down feature descriptions into actionable tasks for engineering teams?

Breaking down feature descriptions into actionable tasks requires feature decomposition to isolate distinct user goals. You then generate concise user stories with testable acceptance criteria, ensuring engineering teams receive executable tasks for sprint planning.

Can I generate user stories for sprint planning using only a feature description file?

Yes, you can generate user stories using a feature description file. The process reads your product requirements, applies user persona identification, and outputs actionable stories validated by INVEST criteria, ready for sprint planning workflows.

What is the best way to ensure user stories are testable and estimable for product management?

The best way to ensure user stories are testable and estimable is to validate them using INVEST criteria. Defining explicit acceptance criteria during user story creation guarantees that each task meets user-centric functionality standards before sprint planning.