jira-task

Generate standardized Jira tasks for bugs, features, and components.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/brivaro/brivaro-ai-wizard --skill jira-task-brivaro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-task
Source: https://github.com/brivaro/brivaro-ai-wizard/tree/main/skills/jira-task
Command: npx skills add https://github.com/brivaro/brivaro-ai-wizard --skill jira-task-brivaro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation of Jira tasks by providing structured templates and conventions for different task types (bugs, features) and components (API, UI, SDK). It ensures consistency and clarity in task descriptions, acceptance criteria, and technical details.

Core Features & Use Cases

  • Standardized Task Creation: Generates Jira tasks following Prowler's standard format.
  • Bug vs. Feature Handling: Differentiates between bug reports and feature requests, applying appropriate parent-child or sibling task structures.
  • Component-Specific Guidance: Provides templates and conventions for API, UI, and SDK tasks, including affected files and technical notes.
  • Use Case: When a bug is reported in the AWS provider's UI, use this skill to generate a Jira task with a clear title, description, acceptance criteria, and affected file paths, ensuring the development team has all necessary information.

Quick Start

Use the jira-task skill to create a new Jira task for a bug in the API component.

Frequently Asked Questions about jira-task

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

FAQPage Schema
How do I create a standardized Jira task for a bug or feature request?

To create a standardized Jira task, this skill generates structured issues with enforced title conventions, component-specific details, and priority guidelines for bugs and features. It uses the Jira MCP integration to automate issue creation and updates.

What is the best way to format Jira tickets for different components like API, UI, and SDK?

The best way to format Jira tickets is by applying component-specific templates that include affected file paths and technical notes for API, UI, and SDK tasks. This enforces consistent descriptions and acceptance criteria across the project.

Can I automate Jira issue creation and updates directly from my development workflow?

Yes, you can automate Jira issue creation and updates because the skill integrates directly with Jira MCP. It populates specific custom fields for team and work item descriptions to generate issues efficiently.

Does the Jira task generator support specific project formats like Prowler?

Yes, the Jira task generator supports the Prowler project by enforcing its specific standard formats for chores, refactors, documentation, and bugs. It applies appropriate parent-child or sibling task structures tailored to this workflow.

How do I structure parent-child or sibling tasks for a feature enhancement?

To structure parent-child or sibling tasks for a feature enhancement, the skill applies specific hierarchical rules differentiating bugs from features. This ensures proper task linkage and tracking across related issues within the project.