playbooks

home / skills / codyswanngt / lisa / jira-verify

jira-verify skill

/.claude/skills/jira-verify

This skill verifies a JIRA ticket against epic relationships and description quality, guiding improvements for coding assistants, developers, and stakeholders.

npx playbooks add skill codyswanngt/lisa --skill jira-verify

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.2 KB
---
name: jira-verify
description: This skill should be used when verifying that a JIRA ticket meets organizational standards for epic relationships and description quality. It checks epic parent relationships and validates description completeness for coding assistants, developers, and stakeholders.
allowed-tools: ["mcp__atlassian__getJiraIssue", "mcp__atlassian__searchJiraIssuesUsingJql", "mcp__atlassian__getAccessibleAtlassianResources"]
---

# Verify JIRA Ticket: $ARGUMENTS

Fetch ticket $ARGUMENTS and verify it meets organizational standards.

## Verification Checks

### 1. Epic Parent Relationship

**Rule**: Non-bug, non-epic tickets MUST have an epic parent

- If missing: Search filter 10089 (Epic Backlog) and suggest appropriate epics

### 2. Description Quality

Verify description adequately addresses:

**Coding Assistants**: Acceptance criteria, requirements, constraints, I/O
**Developers**: Technical context, integration points, testing, edge cases
**Stakeholders**: Business value, user impact, success metrics, summary

## Execute Verification

Retrieve ticket details, run both checks, and provide specific improvement recommendations for any failures.

Overview

This skill verifies that a JIRA ticket meets organizational standards for epic relationships and description quality. It helps coding assistants, developers, and stakeholders ensure tickets are actionable, traceable, and ready for implementation. Use it to get specific, prioritized recommendations when a ticket fails checks.

How this skill works

The skill fetches a JIRA ticket by ID and runs two core checks: (1) ensures non-bug, non-epic tickets have an epic parent and suggests epics from a configured search filter if missing; (2) evaluates the description against role-specific criteria for coding assistants, developers, and stakeholders. It returns a pass/fail result for each check with concise, actionable improvement steps.

When to use it

  • Creating or triaging a new JIRA ticket
  • Preparing tickets for sprint planning or backlog refinement
  • Validating tickets before handing work to coding assistants or contractors
  • Auditing existing backlog for gaps in epic linkage or description quality
  • Enforcing organizational ticketing standards in CI/automation pipelines

Best practices

  • Run verification immediately after ticket creation or significant edits
  • Include acceptance criteria and I/O examples for coding assistants
  • Document technical context, integration points, and testing notes for developers
  • State business value, user impact, and success metrics for stakeholders
  • Use suggested epics from the filter as a starting point, then confirm domain fit

Example use cases

  • Automated pre-merge check that prevents tasks without an epic parent from entering the sprint
  • Backlog grooming session where missing description elements are auto-flagged and assigned
  • Onboarding a new developer by ensuring tickets include technical context and edge cases
  • Generating a short improvement checklist to send to a ticket author before review
  • Continuous audit report that lists tickets failing epic or description standards

FAQ

What counts as a missing epic parent?

Non-bug, non-epic tickets that do not reference an epic field or parent link are considered missing an epic parent.

How are suggested epics chosen?

The skill queries a configured search filter (e.g., Epic Backlog) and lists relevant epics to consider based on project and label matches.

What elements are required in the description?

For coding assistants: acceptance criteria, constraints, and I/O. For developers: technical context, integration points, testing, and edge cases. For stakeholders: business value, user impact, success metrics, and a summary.