jira-task

Create Jira tasks from user requests using Prowler's standard format.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/sebasmzg/sebas.dot --skill jira-task-sebasmzg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-task
Source: https://github.com/sebasmzg/sebas.dot/tree/main/.config/opencode/skill/jira-task
Command: npx skills add https://github.com/sebasmzg/sebas.dot --skill jira-task-sebasmzg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates Jira tasks following Prowler's standard format. Trigger: When user asks to create a Jira task, ticket, or issue.

Core Features & Use Cases

  • Single-task generation: Create a Jira task draft from a natural language request, including title, description, acceptance criteria, and Jira fields following Prowler's templates.
  • Multi-task support: When a request covers multiple components or scopes, split into separate parent/child tasks with clear links and dependencies.
  • Templates & Linking: Generate parent tasks with user-facing descriptions and child tasks with technical notes, affected files, and API/UI details if applicable.
  • Use Cases: Bug reports, feature requests, refactoring tasks, and documentation tasks.

Quick Start

Ask me to create a Jira task, and I will generate a fully structured Jira issue draft.

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 from natural language requests?

To create Jira tasks from natural language, provide a plain text request describing the bug, feature, refactoring, or documentation need. The system then generates a structured Jira issue draft with titles, descriptions, and field mappings.

What is the standard format for structuring Jira issue drafts?

The standard format for Jira issue drafts includes parent and child task templates, acceptance criteria, technical notes, affected files, API or UI details, and specific Jira field mappings to ensure comprehensive project documentation.

Can I split a multi-component request into separate parent and child Jira tasks?

Yes, you can split multi-component requests into separate parent and child Jira tasks. The system generates clear links and dependencies between the parent task with user descriptions and child tasks with technical notes.

Does the Jira task generator work with bug reports and refactoring tasks?

The Jira task generator works with bug reports, feature requests, refactoring tasks, and documentation tasks. It applies standardized templates across projects to produce consistent work items with testing guidance.

What's the best way to map Jira fields for technical notes and acceptance criteria?

The best way to map Jira fields for technical notes and acceptance criteria is by applying standardized templates. This ensures affected files, API and UI details, and testing guidance are populated accurately within the generated issue.

When should I not use automated templates for Jira issue creation?

You should not use automated templates for Jira issue creation when your project requires highly customized field structures that deviate from standard bug, feature, refactoring, or documentation formats supported by the default mappings.