jira-task

Create Jira tasks with standardized Prowler formatting and parent-child links.

Updated Apr 9, 2025
One-click install
npx skills add https://github.com/D4nitrix13/dotfiles-tmp --skill jira-task-d4nitrix13
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-task
Source: https://github.com/D4nitrix13/dotfiles-tmp/tree/main/.config/opencode/skill/jira-task
Command: npx skills add https://github.com/D4nitrix13/dotfiles-tmp --skill jira-task-d4nitrix13

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates Jira tasks and issues following Prowler's standard formatting when users request new work, enabling consistent task structure and traceability.

Core Features & Use Cases

  • Splits work into separate tasks per component (API, UI) when needed.
  • Generates parent tasks for features and links to child tasks.
  • Provides reusable task templates and standardized acceptance criteria.

Quick Start

Ask me to create a Jira task, and I'll generate a Jira task set following Prowler's standard format.

Frequently Asked Questions about jira-task

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

FAQPage Schema
How do I automate creating Jira tasks with standardized titles and acceptance criteria?

Automating Jira task creation applies standardized templates to generate uniform titles, descriptions, and acceptance criteria. It produces structured task sets aligned with Prowler conventions to maintain consistent formatting and traceability across issues.

How does Jira task linking work for multi-component features?

Jira task linking for multi-component work creates separate sibling tasks for each component, such as API and UI, then links them to a parent task. This maintains clear traceability and hierarchical structure across the feature set.

Can I use task templates to split Jira issues by component?

Task templates can split Jira issues by creating separate sibling tasks for each component, like API and UI. The templates generate standardized content including descriptions and references, ensuring each component task follows Prowler formatting.

What is the best way to generate parent and child Jira tickets for a feature?

Generating parent and child Jira tickets involves creating a primary parent task for the feature and linking subsequent child tasks to it. This approach provides reusable templates and standardized acceptance criteria while maintaining clear hierarchical traceability.

Do I need Prowler conventions to structure Jira task descriptions?

Using Prowler conventions to structure Jira task descriptions ensures consistent task content including titles, acceptance criteria, and references. This standard format enables reliable traceability and uniform issue structure across multi-component work.