jira

Create Task, Bug, and Story issues in Jira from templates.

Updated Feb 2, 2026
One-click install
npx skills add https://github.com/k3sdtw/.claude --skill jira-k3sdtw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira
Source: https://github.com/k3sdtw/.claude/tree/main/skills/jira
Command: npx skills add https://github.com/k3sdtw/.claude --skill jira-k3sdtw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to quickly create and manage Jira issues using standard templates for Task, Bug, and Story, reducing context switching and ensuring consistency across projects.

Core Features & Use Cases

  • Template-based issue creation for Task, Bug, and Story.
  • Centralized MCP-driven workflow for creating and updating Jira issues.
  • Use Case: When a backlog item is received, generate a templated Jira issue with summary, description, and acceptance criteria.

Quick Start

Use /jira-task to create a Task issue, /jira-bug to create a Bug, and /jira-story to create a Story.

Frequently Asked Questions about jira

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

FAQPage Schema
How do I create Jira issues with consistent templates across projects?

Template-based issue creation ensures consistency by automating Jira issue generation for Task, Bug, and Story types with predefined formats. Use /jira-task, /jira-bug, or /jira-story commands to generate issues with standardized summary, description, and acceptance criteria fields across multiple projects.

Can I automate issue creation for agile teams using MCP workflows?

Yes. This Skill integrates MCP-driven workflows to automate Jira issue creation and retrieval. Teams can generate templated issues directly from backlog items, reducing manual entry and ensuring uniform issue structure across agile projects.

What's the fastest way to create Bug and Story issues in Jira without repetitive formatting?

Use template commands for immediate issue creation: /jira-bug generates Bug issues and /jira-story generates Story issues with pre-populated fields. Templates eliminate manual formatting, reducing context switching and creation time.

Does this work for managing issues across multiple Jira projects?

Yes. The Skill applies consistent templates across multiple projects, enabling centralized issue management. Template-driven creation ensures standardized formatting regardless of project scope.

Can I use this to reduce backlog processing time?

Template-based issue creation accelerates backlog processing by automating issue generation from incoming items. The Skill populates summary, description, and acceptance criteria automatically, eliminating manual setup per issue.