jira-task

Create Jira tasks with Prowler's standard format and acceptance criteria.

1|Updated Feb 22, 2021
One-click install
npx skills add https://github.com/reVrost/dotfiles --skill jira-task-revrost
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-task
Source: https://github.com/reVrost/dotfiles/tree/main/skills/jira-task
Command: npx skills add https://github.com/reVrost/dotfiles --skill jira-task-revrost

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Jira task creation is standardized to reduce drafting time and ambiguity when logging issues.

Core Features & Use Cases

  • Standardized task creation: Generate Jira tickets in a consistent structure for bugs, features, refactors, and documentation tasks.
  • Component-aware guidance: Provide templates and recommendations for tasks that touch multiple components (API, UI, SDK).
  • Use Case: When a user wants to log a bug or feature, the skill outputs a ready-to-create Jira task with suggested title, description, and acceptance criteria.

Quick Start

Create a Jira task following Prowler's standard format when prompted to log a bug, feature, or improvement.

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 in a standardized format?

Standardized Jira tasks are generated automatically with consistent naming, descriptions, and acceptance criteria. This process is triggered by asking to log a bug, feature, or improvement, which reduces drafting time and ambiguity.

What is the best way to log a Jira issue for multiple components?

The best way to log a Jira issue across multiple components is to generate separate tasks for each specific component, such as the API and UI, using tailored templates to ensure accurate acceptance criteria.

Can I generate Jira tickets for both API and UI components?

Yes, you can generate Jira tickets for both API and UI components. The system provides specific templates and recommendations for each component, ensuring the task descriptions and acceptance criteria match the technical requirements.

Does standardized Jira task creation work for different issue types?

Standardized Jira task creation works for different issue types including bugs, features, refactors, and documentation tasks. It outputs a ready-to-create ticket with a suggested title, description, and acceptance criteria.

Why use a standard format for creating Jira tasks?

Using a standard format for creating Jira tasks reduces drafting time and eliminates ambiguity when logging issues. It ensures every ticket follows a consistent structure for titles, descriptions, and acceptance criteria across the team.