jira-task

Convert user requests into standardized Jira tasks with acceptance criteria.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates Jira tasks following Prowler's standard format, ensuring consistent structure and reducing manual formatting errors.

Core Features & Use Cases

  • Standardized Task Templates: Generates Jira task bodies that follow Prowler's conventions, including title, description, acceptance criteria, and links.
  • Multi-Component Task Splitting: When changes span APIs, UI, or SDK, automatically propose separate tasks per component.
  • Guidance for Use Cases: Provides templates for bugs, features, refactors, and documentation tasks.
  • Real-World Example: Imagine reporting a bug that touches both API and UI; the system suggests separate API and UI tasks with cross-links.

Quick Start

Convert a user request into a Jira task using the standard Prowler structure.

Frequently Asked Questions about jira-task

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

FAQPage Schema
How do I create Jira tasks that follow a consistent format across bugs and features?

This Skill generates Jira tasks with standardized formatting, applying consistent titles, descriptions, and acceptance criteria to bugs, features, refactors, and documentation requests automatically.

Can I split a Jira task across API and UI components automatically?

Yes, when changes span API, UI, or SDK components, the system automatically proposes separate tasks per component and establishes cross-links between the related Jira issues.

What is the standard Prowler format for Jira task creation?

The Prowler format structures Jira tasks with specific conventions for titles, descriptions, acceptance criteria, and links, ensuring consistent formatting across bugs, features, refactors, and documentation tasks.

How do I generate acceptance criteria for a Jira feature request?

You can generate acceptance criteria by providing a user request to this Skill, which transforms it into a complete Jira feature request following the standardized Prowler template structure.

Do I need any Jira API dependencies to format tasks with this workflow?

No dependencies are required. This workflow operates independently to transform user requests into properly formatted Jira task structures for API, UI, and SDK components.