skills.rest
cedricfarinazzo
cedricfarinazzoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

agile-7-create-stories

Derive Jira Stories from an Epic with PRD and Specs UI references.

Updated May 16, 2026
Search Tags:#jira#prd#agile-planning#story-writing#specs-ui#derive-stories#epic-to-stories
One-click install
npx skills add https://github.com/cedricfarinazzo/agile-skills --skill agile-7-create-stories
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agile-7-create-stories
Source: https://github.com/cedricfarinazzo/agile-skills/tree/main/agile-planning/skills/agile-7-create-stories
Command: npx skills add https://github.com/cedricfarinazzo/agile-skills --skill agile-7-create-stories

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams struggle to translate high-level Epics into measurable Jira Stories; this Skill provides a repeatable process to derive a story list, clarify gaps via targeted questions, and prepare Story briefs that map to Epic, PRD, and Specs UI.

Core Features & Use Cases

  • Derive a proposed Story list from an Epic based on PRD requirements and Specs UI screens.
  • Generate complete Story briefs with title, description, acceptance criteria, DoD, and Spec UI references.
  • Facilitate gap-closing interviews to confirm persona, scope, and edge cases before creation.

Quick Start

In Jira, from the target Epic, derive a proposed Story list and prepare questions before writing any Stories.

Frequently Asked Questions about agile-7-create-stories

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

FAQPage Schema
How do I derive Jira stories from an epic based on PRD requirements?▼

Deriving Jira stories from an epic involves mapping PRD requirements and Specs UI screens into standalone stories. This generates complete story briefs with acceptance criteria and Definition of Done while maintaining traceability to the target epic.

What is the best way to write agile stories with acceptance criteria and UI specs?▼

Writing agile stories with UI specs involves generating complete story briefs from PRD requirements and Specs UI screens. This approach ensures each story contains acceptance criteria, DoD, and Spec UI references for precise agile planning.

Can I use PRD and Specs UI to identify missing scope before creating stories?▼

Yes, you can identify missing scope by conducting gap-closing interviews before story creation. This clarifies persona, scope, and edge cases by asking targeted questions derived from PRD requirements and Specs UI screens.

How to ensure traceability between Jira epics and product requirement documents?▼

Traceability between Jira epics and product requirement documents is achieved by generating stories with explicit Jira epic linkage. The derived stories map directly to PRD requirements and include Spec UI references for complete alignment.

Does this story generation process support gap analysis for edge cases?▼

The story generation process supports gap analysis for edge cases by facilitating targeted interviews. It asks optional questions to confirm persona and scope before writing stories, ensuring all gaps are closed.

Related Skills

Explore More Product & Management Skills→
bitovibitovi
24

write-next-story-from-shell-story

Convert the next unwritten shell story in a Jira epic into a full Jira story.

Official
Advanced
grandcamelgrandcamel
42

jira-agile-management

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

Community
Intermediate
KaakatiKaakati
2

sprint-planner

Facilitate agile sprint planning with capacity and effort estimation.

Community
Advanced
nroze22nroze22
1

requirements-test-matrix

Generate categorized test case matrices from PRD text, Confluence URLs, or Jira story keys.

Community
Advanced