skills.rest
fearovex
fearovexCOMMUNITY
Explore all skills by this author →
GitHub

jira-task

Create standardized Jira tasks with parent-child structure and Wiki markup.

Updated Aug 27, 2026
Search Tags:#templates#jira#software-engineering#issue-tracking#task#wiki-markup
One-click install
npx skills add https://github.com/fearovex/claude-config --skill jira-task-fearovex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jira-task
Source: https://github.com/fearovex/claude-config/tree/main/skills/jira-task
Command: npx skills add https://github.com/fearovex/claude-config --skill jira-task-fearovex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating Jira tasks that follow a consistent structure and Jira Wiki markup, reducing ambiguity and rework across engineering and product teams.

Core Features & Use Cases

  • Templates that enforce a consistent task title, description, and acceptance criteria for features, bugs, and enhancements.
  • Guidance for splitting work by component (API, UI, SDK) and for establishing parent-child task relationships.
  • Jira Wiki markup examples and ready-to-use structures to accelerate ticket creation in software projects.

Quick Start

Create a parent Jira task for a new feature and add aligned child tasks for API and UI components using the Jira Wiki markup.

Frequently Asked Questions about jira-task

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

FAQPage Schema
How do I create standardized Jira tasks with proper Wiki markup?▼

Standardized Jira tasks are created using structured templates that enforce consistent titles, descriptions, and Jira Wiki markup. This ensures tickets for features, bugs, or enhancements remain uniform and reduces ambiguity across teams.

What is the best way to structure parent-child Jira tasks for feature development?▼

The best way to structure parent-child Jira tasks is by creating a parent ticket for the feature and splitting child tasks by component, such as API, UI, or SDK. This maintains clear traceability and aligned task relationships.

How do I write Jira Wiki markup for bug and enhancement tickets?▼

Jira Wiki markup for bug and enhancement tickets is applied within task descriptions using ready-to-use structures. These templates provide consistent formatting for acceptance criteria and descriptions, accelerating ticket creation.

Do I need specific templates for API, UI, and SDK component tasks in Jira?▼

Yes, using specific templates for API, UI, and SDK component tasks in Jira ensures proper ticketing workflow structure. The templates provide guidance for splitting work by component and establishing clear parent-child task relationships.

Why does my Jira task formatting break when splitting work across engineering teams?▼

Jira task formatting breaks when descriptions lack consistent Jira Wiki markup and structured templates. Applying standardized formats for titles and acceptance criteria prevents misalignment and reduces rework across engineering and product teams.

Related Skills

Explore More Software Engineering Skills→
adiomasadiomas

task-decomposer

Break down feature requests into atomic tasks with dependencies and parallelization guidance.

Community
Basic
zero3041zero3041
1

jira-integration

Automate Jira ticket management via the Jira REST API.

Community
Intermediate
SpiceLabsHQSpiceLabsHQ

issue-tracker-beads

Map abstract task operations to 'bd' CLI issue tracking commands.

Official
Intermediate
abnejLLCabnejLLC

risk-to-jira-transformer

Convert unstructured risk assessments into Jira tickets via JSON payloads.

Community
Intermediate