skills.rest
dasheck0
dasheck0COMMUNITY
Explore all skills by this author →
𝕏@dasheckGitHub

epic-to-stories

Convert Jira Epics into testable user stories with acceptance criteria.

8|1|Updated Jul 7, 2025
Search Tags:#automation#planning#agile#jira#stories#epic#acceptance-criteria
One-click install
npx skills add https://github.com/dasheck0/qraft-templates --skill epic-to-stories
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: epic-to-stories
Source: https://github.com/dasheck0/qraft-templates/tree/main/opencode-global-skills/epic-to-stories
Command: npx skills add https://github.com/dasheck0/qraft-templates --skill epic-to-stories

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automatically derives precise, testable user stories with complete acceptance criteria from an existing Jira Epic, enabling faster planning and consistent storytelling across teams.

Core Features & Use Cases

  • Converts an Epic into well-scoped user stories, checking for existing stories under the Epic.
  • Decides whether to create new stories, update existing ones, or split a story into smaller parts, and records the results in Jira.
  • Supports proactive triggering when a user describes a Story and an Epic exists, ensuring alignment between Epic and its Stories.

Quick Start

Provide an Epic (Jira key like SCRUM-46) or Epic text, and the tool will generate precise, testable stories with acceptance criteria and handle creation, updating, or splitting in Jira.

Frequently Asked Questions about epic-to-stories

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

FAQPage Schema
How do I automatically break down a Jira Epic into actionable user stories?▼

To break down a Jira Epic into actionable user stories, provide an Epic key like SCRUM-46. The tool analyzes the Epic and generates precise, testable user stories with complete acceptance criteria, then creates them directly in Jira.

What is the best way to generate acceptance criteria for existing agile stories?▼

Generating acceptance criteria for agile stories is handled by transforming Epic descriptions into fully defined stories. The tool evaluates existing child stories under an Epic and updates them with precise, testable acceptance criteria.

Can I update existing stories under a Jira Epic instead of creating new ones?▼

Yes, you can update existing stories under a Jira Epic. The tool checks for existing child stories and decides whether to create new stories, update existing ones, or split them into smaller units based on the Epic's scope.

Do I need a specific Jira format to trigger automated epic planning?▼

You do not need a specific Jira format to trigger automated epic planning. You can provide a standard Jira Epic key like SCRUM-46 or paste the raw Epic text for the tool to process and generate stories.

How does splitting a large epic into smaller stories improve agile automation?▼

Splitting a large epic into smaller stories improves agile automation by ensuring Jira entries have precise details and testable acceptance criteria. This enables downstream agents to automatically implement and validate the work.

Related Skills

Explore More Product & Management Skills→
commercetoolscommercetools
154

jira-create-epic-from-plan

Create Jira epics and child tickets from markdown or OpenSpec plans.

Official
Advanced
reddya3reddya3

qa-story-analysis

Analyze Jira stories and acceptance criteria to generate test scenarios.

Community
Advanced
grandcamelgrandcamel
42

jira-agile-management

Manage Jira Agile workflows for epics, sprints, backlogs, and story points.

Community
Intermediate
epieczkoepieczko

epic.decompose

Parse Markdown Epic documents and generate structured user stories as JSON.

Community
Intermediate