jira-ticket

Create and update Jira tickets with Phoenix conventions via Jira CLI.

1|Updated Apr 15, 2024
One-click install
npx skills add https://github.com/yiminllin/dotfiles --skill jira-ticket-yiminllin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-ticket
Source: https://github.com/yiminllin/dotfiles/tree/main/opencode/.config/opencode/skills/jira-ticket
Command: npx skills add https://github.com/yiminllin/dotfiles --skill jira-ticket-yiminllin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating and updating concise Jira tickets is tedious and error-prone; this skill guides users to craft consistent, Phoenix-focused tickets using the Jira CLI and related workflows.

Core Features & Use Cases

  • Guided collection of ticket sections such as Summary, Why, Goal, Non-goal, Context, and Plan.
  • Enforces Phoenix conventions: summaries prefixed with [Phoenix], component set to Phoenix, team set to Simulation, and concise descriptions.
  • Drafts ready-to-submit Jira bodies and offers review/edit before creation; supports creating, updating, moving statuses, and linking tickets.

Quick Start

Ask for a Phoenix ticket to be created or updated and provide the required sections one by one.

Frequently Asked Questions about jira-ticket

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

FAQPage Schema
How do I create Jira tickets from the CLI that follow Phoenix conventions?

To create Jira tickets from the CLI, this skill guides you to draft summaries prefixed with [Phoenix], set the component to Phoenix, and assign the team to Simulation, generating a ready-to-submit body.

What sections do I need to draft a concise Jira ticket for a Phoenix workflow?

Drafting a concise Jira ticket requires sections like Summary, Why, Goal, Non-goal, Context, and Plan, which are collected interactively to build the ticket body for Phoenix workflows.

Can I update and move Jira ticket statuses using the Jira CLI?

Yes, you can update existing Jira tickets, move their statuses, and link tickets together using the Jira CLI while maintaining concise descriptions and Phoenix conventions.

Does the Jira CLI support interactive prompts for planning simulation steps?

The Jira CLI supports interactive prompts to collect required ticket sections one by one, allowing you to plan simulation steps and review or edit the drafted body before submission.

What is the best way to ensure my Jira summaries meet Simulation team standards?

The best way to ensure Jira summaries meet Simulation team standards is by enforcing Phoenix conventions, which automatically prefixes summaries with [Phoenix] and maintains concise descriptions.