generate-stories

Translate an Epic into User Stories with acceptance criteria and register them in the backlog.

157|28|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/Fr-e-d/GAAI-framework --skill generate-stories-fr-e-d
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-stories
Source: https://github.com/Fr-e-d/GAAI-framework/tree/main/.gaai/core/skills/discovery/generate-stories
Command: npx skills add https://github.com/Fr-e-d/GAAI-framework --skill generate-stories-fr-e-d

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the conversion of high-level Epics into detailed, actionable User Stories, ensuring clear requirements for development.

Core Features & Use Cases

  • Story Generation: Creates individual User Stories from a parent Epic, adhering to standard formats.
  • Acceptance Criteria: Ensures each story includes explicit, testable acceptance criteria.
  • Backlog Integration: Automatically registers generated stories in the active backlog for delivery tracking.
  • Use Case: After defining a new feature as an Epic (e.g., "Implement user authentication"), use this Skill to break it down into manageable stories like "As a user, I want to register with email and password" and "As a user, I want to log in with my credentials."

Quick Start

Use the generate-stories skill to create user stories for the epic located at contexts/artefacts/epics/E01.epic.md.

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 with acceptance criteria?

To break down an epic into actionable user stories, this Skill translates a defined epic into individual stories formatted with explicit, testable acceptance criteria, preparing the work for delivery execution.

When do I need to generate user stories for agile backlog management?

You need to generate user stories for agile backlog management when an epic is fully defined and the high-level requirements must be converted into clear, actionable tasks registered in the active backlog for delivery tracking.

Does generating user stories automatically register them in the active backlog?

Yes, generating user stories automatically registers the newly created files into the active backlog, ensuring the detailed epic breakdown items are immediately available for delivery tracking and agile backlog management.

What is the best way to convert a single epic into standard user stories?

The best way to convert a single epic into standard user stories is to automate the translation process, ensuring each generated story adheres to standard formats and includes explicit, testable acceptance criteria for development.

Can I use this to create testable acceptance criteria for my epic breakdown?

Yes, you can use this to create testable acceptance criteria, as the story generation process ensures every user story derived from the parent epic includes explicit requirements ready for development validation.