Create Jira Story

Automate creation of Jira stories with acceptance criteria.

112|305|Updated Oct 10, 2025

Search Tags:#agile #jira #project-management #user-stories #story-creation #acceptance-criteria #agile-development

Ready to run

npx skills add https://github.com/openshift-eng/ai-helpers --skill create-jira-story-openshift-eng

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Create Jira Story
Source: https://github.com/openshift-eng/ai-helpers/tree/main/plugins/jira/skills/create-story
Command: npx skills add https://github.com/openshift-eng/ai-helpers --skill create-jira-story-openshift-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates poorly formatted Jira stories by providing structured templates and interactive guidance for creating user stories with comprehensive acceptance criteria.

Core Features & Use Cases

Interactive Story Creation: Guides users through collecting user roles, actions, and value statements.
Acceptance Criteria Generation: Helps define testable, specific criteria using multiple formats.
Use Case: When your team needs to create a new feature story for automatic node pool scaling, this Skill ensures proper formatting and comprehensive coverage.

Quick Start

Use the Create Jira Story skill to help me create a well-formatted Jira story for adding user dashboard functionality to our application.

Frequently Asked Questions about Create Jira Story

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

FAQPage Schema

How do I create a well-formatted Jira story with acceptance criteria?▼

Create a Jira story by using structured guidance to write a concise summary, a full description in As a... I want... So that... format, and explicit acceptance criteria in one of three formats: Test-Based, Demonstration-Based, or Verification-Based. This ensures complete, testable user stories.

What's the standard structure for writing user stories in Jira?▼

User stories follow a three-part structure: a brief summary line, a description using the As a [role] I want [action] So that [value] template, and acceptance criteria that are specific and testable. This format clarifies requirements for features, bugs, tasks, and epics.

How do I define acceptance criteria for Jira issues?▼

Acceptance criteria can follow Format 1 (Test-Based), Format 2 (Demonstration-Based), or Format 3 (Verification-Based) approaches. Each format specifies testable conditions that confirm when a story is complete, ensuring clarity between team members.

Can I use this approach for different issue types in Jira?▼

Yes, the structured story format applies across features, bugs, tasks, and epics. The same principles—clear summary, role-based description, and explicit acceptance criteria—work across all issue types in your Jira projects.

What's the difference between summary and description in a Jira story?▼

The summary is a concise one-line title; the description expands using the As a... I want... So that... format to explain the user role, desired action, and business value. Separating them prevents confusion and keeps the story searchable.

Why is acceptance criteria format important for agile teams?▼

Well-defined acceptance criteria reduce ambiguity, enable consistent testing, and align developers, testers, and stakeholders on what "done" means. Format-based approaches (test, demonstration, or verification) ensure criteria are specific and measurable.