skills.rest
liminal-ai
liminal-aiOFFICIAL
Explore all skills by this author →
GitHub

ls-publish-epic

Break down a validated epic into per-story files with Jira-ready formatting.

1|1|Updated Apr 13, 2026
Search Tags:#documentation#agile#traceability#jira#epic#story-creation
One-click install
npx skills add https://github.com/liminal-ai/liminal-build --skill ls-publish-epic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ls-publish-epic
Source: https://github.com/liminal-ai/liminal-build/tree/main/references/full-liminal-spec-skills/ls-publish-epic
Command: npx skills add https://github.com/liminal-ai/liminal-build --skill ls-publish-epic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured method to transform a validated epic into a set of implementable stories with clear acceptance criteria, traceability, and a plan for a PO-friendly business epic if required.

Core Features & Use Cases

  • Shards a detailed epic into individual story files (e.g., 00-foundation.md, 01-...). Each story carries its own Acceptance Criteria, Test Conditions, and Technical Design sections.
  • Generates a coverage artifact mapping every AC/TC to a story and a corresponding integration path trace, to ensure no gaps.
  • Supports an optional business epic that groups ACs for PO consumption and references the related stories.
  • Formats are Jira-ready, with sections and markers ready for copy-paste into tooling.

Quick Start

Process a validated epic to generate per-story files and an optional business epic.

Frequently Asked Questions about ls-publish-epic

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

FAQPage Schema
How do I break down an agile epic into Jira-ready stories?▼

To break down an agile epic into Jira-ready stories, this Skill shards a validated epic into individual per-story files with Acceptance Criteria, Test Conditions, and Technical Design sections formatted for direct copy-paste into Jira.

What is the best way to ensure traceability between epic acceptance criteria and generated stories?▼

Ensuring traceability between epic acceptance criteria and stories requires a coverage artifact mapping every AC and TC to a specific story file, alongside a precise integration path trace to guarantee zero gaps in development implementation.

Can I generate a business epic for product owners from detailed development stories?▼

Yes, you can generate an optional PO-friendly business epic that groups Acceptance Criteria for product owner consumption and directly references the related foundation and feature stories generated in the stories directory.

How do I shard a validated epic into foundation and feature story files?▼

Sharding a validated epic into foundation and feature story files involves processing the epic to create individual markdown files under a stories directory, each carrying dedicated Acceptance Criteria, Test Conditions, and Technical Design sections.

Does this story creation process support integration path tracing for agile development?▼

Yes, the story creation process enforces precise integration path tracing and generates a coverage artifact mapping every Acceptance Criteria and Test Condition to ensure complete traceability and no implementation gaps.

Related Skills

Explore More Software Engineering Skills→
grandcamelgrandcamel
42

jira-agile-management

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

Community
Intermediate
mol4mol4
1

bmad-sprint-planning

Generate sprint-status.yaml from BMAD epic markdown files and story artifacts.

Community
Advanced
dundasdundas

user-story-generator

Generate user stories with acceptance criteria in Markdown format.

Community
Intermediate
wtthorntonwtthornton
4

planner

Creates user stories, epics, and tasks with Fibonacci point estimates.

Community
Advanced