jira-task_skill

This skill creates Jira tasks following Prowler's standard format when you ask to create a Jira task, ticket, or issue.

198

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill gentleman-programming/gentleman-skills --skill jira-task

SKILL.md9.2 KB

Overview

This skill creates Jira tasks using Prowler's standard format when you ask to create a Jira task, ticket, or issue. It produces properly structured titles, descriptions, acceptance criteria, technical notes, and linking conventions for bugs, features, refactors, docs, and chores. The output is organized to support MCP Jira integration and to enforce multi-component splitting rules.

How this skill works

When triggered, the skill analyzes the request type (bug, feature, enhancement, refactor, docs) and the affected components (API, UI, SDK, Full Stack). It generates either sibling bug tasks or a parent + child feature set, using Prowler templates for Description, Acceptance Criteria, Technical Notes, Testing, Priority, and Related Tasks. It also includes the exact Jira fields and team field guidance needed for MCP-based creation and the Work Item Description update pattern.

When to use it

Report production bugs that require backend, frontend, or SDK changes
Propose new features that need stakeholder context plus technical work
Create refactors, documentation tasks, or maintenance chores
Split multi-component work into parallel tasks for API, UI, SDK
Generate ready-to-paste Jira content for MCP automation

Best practices

Split multi-component changes: sibling tasks for bugs, parent+children for features
Use the title convention: [TYPE] Brief description (components)
Include Current State and Expected State in every task description
Provide full file paths in Technical Notes and clear, testable acceptance criteria
Set Team via customfield_10359 (API, UI, SDK) and update customfield_10363 with Jira Wiki markup for Work Item Description

Example use cases

Create two sibling bug tasks when an AWS region field is missing in both API and UI
Create a parent feature task for AWS GovCloud support with child API and UI tasks linked and prioritized
Convert a bug report into two component-specific tasks so backend can be fixed before UI changes
Produce a technical SDK task describing affected provider checks and config changes
Prepare MCP payloads: create issue, update Work Item Description, assign team field, and transition workflow

FAQ

No. For bugs create separate sibling tasks per component. For features create a parent task with child tasks for each component.

What title format should I use?

Use the convention: [TYPE] Brief description (components), e.g. [BUG] Add region selector (API + UI).

Which Jira field stores the display description?

Use customfield_10363 (Work Item Description) and provide content in Jira Wiki markup when updating the issue.