jira-story

Name: jira-story
Availability: InStock
Author: maestria-co

Format structured story specs into Jira-ready user stories with Markdown output.

Updated Mar 2, 2026

Search Tags:#jira #product-management #acceptance-criteria #markdown-output #ticket-generation #story-formatting

Ready to run

npx skills add https://github.com/maestria-co/ai-playbook --skill jira-story

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jira-story
Source: https://github.com/maestria-co/ai-playbook/tree/main/skills/jira-story
Command: npx skills add https://github.com/maestria-co/ai-playbook --skill jira-story

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Format a structured story spec into a Jira-ready user story. This is a formatter only — it does not gather requirements or make design decisions. It is invocable directly when someone says "format this as a Jira ticket", "turn this spec into a Jira story", or "write this up for Jira".

Core Features & Use Cases

Formats a structured story spec into a Jira-ready user story.
Enforces a consistent output structure with sections like acceptance criteria, technical notes, dependencies, and open questions.
Invocable via natural language prompts to generate Jira-ready stories from varied input specs.

Quick Start

Provide a structured story spec and ask the skill to format it as a Jira ticket.

Frequently Asked Questions about jira-story

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

FAQPage Schema

How do I format a structured story spec into a Jira-ready user story?▼

To format a structured story spec into a Jira-ready user story, provide the spec to the skill and invoke it to generate a Markdown block. It outputs a standardized structure with sections for acceptance criteria, technical notes, dependencies, and open questions.

What sections are included in a formatted Jira user story?▼

A formatted Jira user story includes standardized sections for acceptance criteria, technical notes, dependencies, and open questions. This structure enforces consistency across product-management workflows and outputs a Markdown block ready to paste directly into Jira.

Does this skill gather requirements or make design decisions for Jira tickets?▼

This skill does not gather requirements or make design decisions for Jira tickets; it is a formatter only. It takes an existing structured story spec and enforces a consistent output structure to create a Jira-ready Markdown block.

Can I use natural language to turn a spec into a Jira ticket?▼

Yes, you can use natural language prompts like "format this as a Jira ticket" or "turn this spec into a Jira story" to invoke the skill. It processes the structured spec and outputs a Markdown block formatted for Jira.

What is the best way to ensure consistent Jira ticket formatting across diverse input specs?▼

The best way to ensure consistent Jira ticket formatting is to use a formatter that enforces a standardized output structure. This skill takes diverse input specs and outputs a consistent Markdown block with sections for acceptance criteria, technical notes, dependencies, and open questions.

Do I need a pre-structured spec to generate a Jira-ready user story?▼

Yes, you need a pre-structured story spec to generate a Jira-ready user story because this skill is a formatter only. It does not gather requirements or make design decisions; it strictly formats the provided input into a standardized Markdown block for Jira.