generate-stories

Generate stories from an epic with unique IDs, branches, and PRs.

13|1|Updated Nov 21, 2025
One-click install
npx skills add https://github.com/Roeia1/SAGA --skill generate-stories
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-stories
Source: https://github.com/Roeia1/SAGA/tree/main/plugin/skills/generate-stories
Command: npx skills add https://github.com/Roeia1/SAGA --skill generate-stories

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate cohesive, actionable stories automatically from a single epic, enabling rapid planning and implementation.

Core Features & Use Cases

  • Read an epic and produce a lightweight, globally unique breakdown of stories with IDs, titles, and descriptions.
  • Validate existing stories to avoid ID collisions and ensure non-overlapping scopes.
  • Spawn parallel story-generation agents to produce story.json and associated task data, with an approval workflow when needed.
  • Collect results and present a completion report with PRs and worktree paths to accelerate implementation.

Quick Start

Create stories for the epic by invoking the skill with your epic identifier.

Frequently Asked Questions about generate-stories

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

FAQPage Schema
How do I generate multiple user stories from a single epic automatically?

To generate stories from an epic automatically, this skill reads your epic documents and produces a validated breakdown of actionable stories with unique IDs, titles, and descriptions. It spawns parallel agents to scale software delivery without manual writing.

What is the best way to break down an epic into actionable development stories?

The best way to break down an epic is using automated validation and parallel story-agent execution. This process ensures non-overlapping scopes and generates cohesive stories with associated branches and PRs for rapid implementation.

How does automated story generation prevent duplicate IDs and overlapping scopes?

Automated story generation prevents duplicates by checking existing stories within your project directory before creating new ones. It validates scopes to ensure no overlaps and assigns globally unique IDs to every generated story breakdown.

How do I manage epic documents in .saga/epics for automated story breakdown?

To manage epic documents for automated story breakdown, place your epics in the .saga/epics directory. The skill reads these documents, prompts for approval on the generated breakdown, and outputs story.json files with worktree paths.

Can I spawn parallel agents to create story branches and PRs at scale?

Yes, you can spawn parallel story-generation agents to create story branches and PRs at scale. The system aggregates results from each agent into a completion report, accelerating implementation across multiple cohesive stories.

Does automated epic breakdown require manual approval before generating stories?

Automated epic breakdown includes an approval workflow before spawning agents. After reading the epic and generating a proposed breakdown, it prompts for your approval to ensure the story scope and IDs match your expectations.