Agent-Skills.md

Agent Skills: Verify JIRA Ticket: $ARGUMENTS

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.

UncategorizedID: codyswanngt/lisa/jira-verify

Repository

codyswanngt/lisa
CodySwannGTLicense: MIT
12

Install this agent skill to your local

pnpm dlx add-skill https://github.com/CodySwannGT/lisa/tree/HEAD/plugins/lisa/skills/jira-verify

Skill Files

Browse the full folder contents for jira-verify.

Download Skill

Loading file tree…

plugins/lisa/skills/jira-verify/SKILL.md

Skill Metadata

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.

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

3. Validation Journey

Rule: Tickets that change runtime behavior MUST include a Validation Journey section.

Check by running:

python3 .claude/skills/jira-journey/scripts/parse-plan.py <TICKET_ID> 2>&1
  • If the parser returns steps: PASS
  • If the parser fails with "No 'Validation Journey' section found": FAIL — recommend using /jira-add-journey <TICKET_ID> to add one

This check is skipped for:

  • Documentation-only tickets
  • Config-only tickets (env vars, CI/CD, feature flags)
  • Type-definition-only tickets (no runtime effect)
  • Epic-level tickets (journeys belong on child stories/tasks)

Execute Verification

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