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.

npx claudepluginhub codyswanngt/lisa --plugin lisa-expo

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

design-system

167.4k

Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.

team-skills-platform

ui-demo

167.4k

Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.

team-skills-platform

kotlin-patterns

167.4k

Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.

team-skills-platform

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 (Frontend Tickets)

Rule: Tickets that touch UI (components, labels, or description mentioning frontend, UI, modal, layout, responsive, screen, page, button, form) 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:

Pure backend/API tickets (no UI surface)

Config-only tickets (env vars, feature flags, CI/CD)

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 (Frontend Tickets)

Rule: Tickets that touch UI (components, labels, or description mentioning frontend, UI, modal, layout, responsive, screen, page, button, form) 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:

Pure backend/API tickets (no UI surface)
Config-only tickets (env vars, feature flags, CI/CD)
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.