Skill

jira-verify

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.

Install

npx claudepluginhub codyswanngt/lisa --plugin lisa

Tool Access

This skill is limited to using the following tools:

mcp__atlassian__getJiraIssuemcp__atlassian__searchJiraIssuesUsingJqlmcp__atlassian__getAccessibleAtlassianResources

Preview

Fetch ticket $ARGUMENTS and verify it meets organizational standards.

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

139.2k

mcp-builder

9 files

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

anthropics-skills-13

124.2k

canvas-design

20 files

Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.

anthropics-skills-13

124.2k

Stats

Parent Repo Stars1

Parent Repo Forks2

Last CommitMar 5, 2026

Actions

View Source View Plugin View on GitHub View README

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.

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:

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.