create-jira-work-items

Create Jira feature, development task, and verification issues with duplicate checks.

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/Omniloy/agent-skills --skill create-jira-work-items
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-jira-work-items
Source: https://github.com/Omniloy/agent-skills/tree/main/skills/create-jira-work-items
Command: npx skills add https://github.com/Omniloy/agent-skills --skill create-jira-work-items

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing Jira tickets by hand often leads to missing acceptance criteria, wrong links, and weak verification ownership. This Skill turns a request into the team's required Feature plus linked Dev task and independent Verification structure so work is ready to track and review.

Core Features & Use Cases

  • Drafts a Feature, a linked development task, and a separate Verification issue with the correct Jira relationships.
  • Checks for likely duplicates before creating anything and pauses for a decision when it finds possible matches.
  • Validates epics, project metadata, and assignees so the feature owner and verifier are different people.
  • Use it when someone asks to create a ticket, file a story, open a feature, or use Jira MCP for new work.

Quick Start

Ask this skill to create a Jira feature for your request, name the project, epic, and verifier, and it will draft the linked issues for your approval before any ticket is created.

Frequently Asked Questions about create-jira-work-items

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

FAQPage Schema
How do I create Jira work items with linked development tasks and verification?

Creating Jira work items with linked development tasks and verification involves drafting a Feature, a linked Dev task, and a separate Verification issue to ensure correct hierarchy and independent review tracking.

How do I avoid duplicate Jira tickets when filing new feature requests?

To avoid duplicate Jira tickets when filing feature requests, perform a duplicate check before creation to identify likely matches and pause the workflow for a decision on possible duplicates.

Can I enforce different assignees for feature ownership and verification in Jira?

You can enforce different assignees for feature ownership and verification in Jira by validating project metadata and assignee rules, ensuring the feature owner and the verifier are always different people.

What is the best way to structure acceptance criteria for Jira story filing?

The best way to structure acceptance criteria for Jira story filing is to apply a structured format during ticket creation, ensuring all requirements are captured before a final review gate approves the issue.

How does a review gate work before creating Jira issues through MCP?

A review gate before creating Jira issues through MCP works by drafting the linked Feature, Dev task, and Verification ticket for explicit user approval, preventing any issue from being created until confirmed.

Does this Jira workflow require selecting an epic before opening a feature?

This Jira workflow requires selecting an epic and validating project metadata before opening a feature, ensuring the new feature request correctly integrates into the existing team hierarchy and assignee rules.