jira-add-journey

Add a structured Validation Journey section to JIRA tickets using jira-cli.

3|3|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/CodySwannGT/lisa --skill jira-add-journey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-add-journey
Source: https://github.com/CodySwannGT/lisa/tree/main/plugins/lisa-expo/skills/jira-add-journey
Command: npx skills add https://github.com/CodySwannGT/lisa --skill jira-add-journey

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of adding a structured "Validation Journey" section to existing JIRA tickets, ensuring clarity and consistency in testing procedures.

Core Features & Use Cases

  • Automated Journey Creation: Reads JIRA ticket details, analyzes feature requirements, and drafts a comprehensive validation journey.
  • Codebase Analysis: Leverages codebase understanding to identify relevant user flows, checkpoints, and assertions.
  • Use Case: When a new feature is implemented, use this skill to automatically generate the necessary steps, screenshots, viewports, and assertions for testing, appending it directly to the JIRA ticket description.

Quick Start

Use the jira-add-journey skill to add a validation journey to the JIRA ticket PROJ-123.

Frequently Asked Questions about jira-add-journey

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

FAQPage Schema
How do I automatically add validation steps to a JIRA ticket?

To add validation steps to a JIRA ticket, this skill parses ticket descriptions and analyzes codebase context to append a structured Validation Journey section. It identifies UI surfaces, user flows, and assertions directly onto the existing JIRA issue.

What is a validation journey in software testing?

A validation journey is a structured testing section appended to JIRA tickets that defines testable steps. It identifies visual checkpoints, viewports, and assertions based on feature requirements and codebase analysis to ensure comprehensive testing coverage.

Do I need a JIRA API token to generate test documentation?

Yes, you need a configured JIRA_API_TOKEN and jira-cli setup to generate and append test documentation. These dependencies allow the skill to read existing ticket details and automatically update the description with validation journeys.

How does codebase analysis improve JIRA workflow automation?

Codebase analysis improves JIRA workflow automation by leveraging codebase understanding to identify relevant user flows and visual checkpoints. This ensures the generated validation journeys accurately reflect the actual implemented feature surfaces and assertions.

Can I automatically identify viewports and assertions for JIRA testing?

Yes, you can automatically identify viewports and assertions for JIRA testing by running this skill against a target ticket. It analyzes feature requirements and codebase context to draft the necessary visual checkpoints and testable steps.

What are the limitations of automated validation journey creation?

A key limitation of automated validation journey creation is its dependency on a pre-configured jira-cli and a valid JIRA_API_TOKEN. Without proper environment setup and codebase access, the skill cannot parse ticket details or append the testing documentation.