Tracker Add Journey: $ARGUMENTS
Thin dispatcher. Resolves the configured destination tracker and delegates to the matching vendor skill.
See the config-resolution rule for configuration and dispatch table.
Workflow
- Resolve tracker config (same logic as
lisa-tracker-write). - Dispatch:
- Missing / empty → stop and report
"No tracker configured in .lisa.config.json. Run /lisa:setup:jira, /lisa:setup:github, or /lisa:setup:linear first." jira→ invokelisa-jira-add-journeywith$ARGUMENTSverbatim. Arg: a JIRA ticket key.github→ invokelisa-github-add-journeywith$ARGUMENTSverbatim. Arg:org/repo#<number>or a GitHub issue URL.linear→ invokelisa-linear-add-journeywith$ARGUMENTSverbatim. Arg: a Linear Issue identifier (e.g.,ENG-123).- Anything else → stop and report
"Unknown tracker '<value>' in .lisa.config.json. Expected 'jira', 'github', or 'linear'."
- Missing / empty → stop and report
- Pass through the output.
Rules
- The Validation Journey content format is identical across all vendors (markdown sections with
[EVIDENCE: name]markers). The only difference is how the section is appended — JIRA viaeditJiraIssue(Jira wiki markup), GitHub viagh issue edit --body-file(markdown), Linear viasave_issue(markdown). - If the ticket already has a Validation Journey, the vendor skill reports it and stops. This shim does not retry.