Menu
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/CodySwannGT/lisa --skill jira-add-journeyThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
| name | jira-add-journey |
| description | Add a Validation Journey… |
Read an existing JIRA ticket, understand the feature or fix it describes, analyze the codebase to determine the verification approach, and append a Validation Journey section to the ticket description.
$ARGUMENTS: <TICKET_ID>
TICKET_ID (required): JIRA ticket key (e.g., PROJ-123)JIRA_API_TOKEN environment variable setjira-cli configured. Prefer the config Lisa writes at
.lisa/jira-cli/.config.yml (the setup-jira-cli SessionStart hook writes it
from JIRA_SERVER / JIRA_LOGIN / JIRA_PROJECT on a project whose
tracker is jira), and pass it explicitly with --config. A developer's
own ~/.config/.jira/.config.yml still works as jira-cli's default when no
--config is given.Use the Atlassian MCP or jira-cli to read the full ticket details:
# Run from the project root. --config pins jira-cli to the file Lisa's
# setup-jira-cli hook wrote, instead of the machine's own ~/.config/.jira.
# jira-cli resolves --config > JIRA_CONFIG_FILE > ~/.config/.jira/.config.yml,
# and a --config path that does not exist fails closed with "Missing
# configuration file." rather than silently using the default.
jira --config .lisa/jira-cli/.config.yml issue view <TICKET_ID>
If .lisa/jira-cli/.config.yml does not exist, drop --config to fall back to
the machine's own jira-cli config — but say so in your report rather than
letting the Lisa-written config go quietly unused.
Extract: title, description, acceptance criteria, components, labels, linked tickets.
Run the parser to see if a Validation Journey already exists:
python3 .claude/skills/jira-journey/scripts/parse-plan.py <TICKET_ID> 2>&1
If the parser succeeds and returns steps, the ticket already has a journey. Report this to the user and stop.
Based on the ticket description and acceptance criteria, determine the appropriate verification approach. Stack-specific overrides provide the analysis logic.
Compose the journey following the Validation Journey format with: Prerequisites, Steps (with evidence markers), and Assertions.
Display the drafted Validation Journey to the user and ask for confirmation before appending it to the ticket.
After user approval, use the JIRA REST API to append the Validation Journey to the existing ticket description.
Run the parser again to confirm the journey was added correctly:
python3 .claude/skills/jira-journey/scripts/parse-plan.py <TICKET_ID>