jira-workflow

Create and synchronize Jira issues from planning documents using jira-cli.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/TUP-TESIS-LAB/FRONTEND-LABORATORIO --skill jira-workflow-tup-tesis-lab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-workflow
Source: https://github.com/TUP-TESIS-LAB/FRONTEND-LABORATORIO/tree/main/.claude/skills/jira-workflow
Command: npx skills add https://github.com/TUP-TESIS-LAB/FRONTEND-LABORATORIO --skill jira-workflow-tup-tesis-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill eliminates the friction of manual project tracking by automatically converting planning documents into Jira issues and maintaining a bidirectional link between the plan and the ticket.

Core Features & Use Cases

  • Automated Ticket Creation: Generates Jira issues directly from plan files, ensuring consistency and reducing administrative overhead.
  • Bidirectional Sync: Keeps the plan and the ticket updated, allowing for status transitions and description updates without leaving the development environment.
  • Use Case: After finalizing a technical design document, trigger this skill to create a corresponding Jira task, auto-assign it to yourself, and link the ticket URL back into the design document for full traceability.

Quick Start

Run the jira-workflow skill to create a new ticket based on the current plan file.

Frequently Asked Questions about jira-workflow

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

FAQPage Schema
How do I automate Jira ticket creation from project planning documents?

Automating Jira ticket creation from planning documents requires using the jira-workflow skill to generate issues directly from your plan files. This ensures consistency and reduces administrative overhead by maintaining a bidirectional link between the technical specification and the tracking system.

Can I sync Jira issue status transitions without leaving my development environment?

Syncing Jira issue status transitions without leaving your environment is possible using the jira-workflow skill. It performs bidirectional synchronization, allowing you to update ticket statuses and descriptions directly from your local plan files via the jira-cli tool.

What is the best way to link technical design documents to issue tracking systems?

Linking technical design documents to issue tracking systems is best achieved by automating ticket creation and embedding the generated Jira ticket URL back into the design document. This process establishes full traceability between your technical specifications and project management tasks.

Do I need a jira-cli environment with API token authentication to manage issues?

A configured jira-cli environment with valid API token authentication is required to perform issue operations with this workflow. You must have this prerequisite set up locally to authorize the automated creation and synchronization of your Jira tickets.

How does bidirectional synchronization work between plan files and Jira tickets?

Bidirectional synchronization between plan files and Jira tickets works by automatically updating the plan and the ticket whenever changes occur. This allows status transitions and description updates to reflect across both your local documents and the Jira issue tracking system simultaneously.