generate-stories

Name: generate-stories
Availability: InStock
Author: petrsimonidesxart

Translate Epics into user stories with acceptance criteria and backlog entries.

Updated Mar 8, 2026

Search Tags:#planning #discovery #story #backlog #delivery #epic #acceptance-criteria

Ready to run

npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill generate-stories-petrsimonidesxart

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: generate-stories
Source: https://github.com/petrSimonidesXart/xPmGateway/tree/main/.gaai/core/skills/discovery/generate-stories
Command: npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill generate-stories-petrsimonidesxart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates a defined Epic into clear, actionable User Stories with explicit acceptance criteria to guide Delivery planning and execution.

Core Features & Use Cases

Derives story IDs from the parent Epic (e.g., E01 -> E01S01, E01S02).
Ensures stories include testable acceptance criteria and explicit backlog registration.
Maintains traceability between Epics, stories, and backlog items for disciplined delivery.

Quick Start

Provide an Epic file as input and let the system generate testable stories registered in the backlog.

Frequently Asked Questions about generate-stories

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

FAQPage Schema

How do I break down an Epic into actionable User Stories for delivery planning?▼

To generate User Stories from an Epic, provide the Epic file as input. The system automatically derives unique story IDs from the parent Epic, applies explicit acceptance criteria, and registers each entry in the backlog for disciplined delivery planning.

What makes a User Story testable and independent in a product backlog?▼

A testable and independent User Story includes explicit acceptance criteria, unique IDs mapped to a parent Epic, and any necessary constraints or related decisions. This ensures each backlog item can be delivered and validated without dependencies on other stories.

How are User Story IDs generated from parent Epics?▼

User Story IDs are generated by appending a sequential number to the parent Epic identifier. For example, an Epic labeled E01 will produce derived Story IDs like E01S01 and E01S02, maintaining clear traceability across the delivery backlog.

Can I use automated story generation for complex planning scenarios with multiple constraints?▼

Yes, you can use automated story generation across various planning scenarios. It processes complex Epics by producing independent stories with explicit acceptance criteria, capturing required constraints and related decisions to ensure disciplined delivery execution.

What is the best way to maintain traceability between Epics and backlog items?▼

The best way to maintain traceability is deriving User Story IDs directly from the parent Epic and registering each story in the backlog. This explicit mapping connects Epics, stories, and delivery work items for disciplined tracking.

Why does my Epic need explicit acceptance criteria before delivery execution?▼

Your Epic needs explicit acceptance criteria to guide delivery planning and execution effectively. Translating Epics into testable stories with defined constraints ensures the resulting work items are independent, verifiable, and meet the required scope.