generate-stories

Translate an Epic into user stories with acceptance criteria and register them in the active backlog.

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/bketelsen/truenas-mcp --skill generate-stories-bketelsen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-stories
Source: https://github.com/bketelsen/truenas-mcp/tree/main/.gaai/core/skills/discovery/generate-stories
Command: npx skills add https://github.com/bketelsen/truenas-mcp --skill generate-stories-bketelsen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill transforms high-level Epics into detailed, actionable User Stories, bridging the gap between product vision and development execution.

Core Features & Use Cases

  • User Story Generation: Creates well-defined user stories with clear acceptance criteria from an Epic.
  • Backlog Integration: Automatically registers generated stories into the active backlog for tracking and execution.
  • Use Case: When a new feature Epic is defined, activate this Skill to break it down into manageable stories for the development team, ensuring all requirements are captured and prioritized.

Quick Start

Activate the generate-stories skill to create user stories from the epic file located at contexts/artefacts/epics/E001.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 for backlog refinement?

You generate user stories from an epic by activating this Skill to translate your Epic file into clear, actionable User Stories with explicit acceptance criteria, preparing the work for Delivery execution.

What is the best way to write user stories with acceptance criteria from a high-level epic?

The best way to write user stories with acceptance criteria from a high-level epic is to apply story writing best practices through this Skill, which bridges product vision and development execution by capturing all requirements.

Do I need a specific file format to convert epics into user stories for agile development?

You need an epic file located at contexts/artefacts/epics/E001.epic.md to convert epics into user stories for agile development, which the Skill processes to generate well-defined stories for the development team.

Can I automatically register generated user stories into the active backlog during product discovery?

You can automatically register generated user stories into the active backlog during product discovery, as this Skill integrates backlog tracking to ensure all requirements are captured and prioritized for execution.

Why does my agile team need explicit acceptance criteria when splitting epics into user stories?

Your agile team needs explicit acceptance criteria when splitting epics into user stories because it ensures all requirements are captured and prioritized, bridging the gap between product vision and development execution.