Menu
Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.
Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
npx skills add https://github.com/CodySwannGT/lisa --skill lisa-tracker-add-journeyO comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.
Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.
This skill should be used for any non-trivial request — features, bugs, stories, epics, spikes, or multi-step tasks. It accepts a ticket URL (Jira, Linear, GitHub), a file path containing a spec, or a plain-text prompt. It assembles an agent team, breaks the work into structured tasks, and manages the full lifecycle from research through implementation, code review, deploy, and empirical verification.
any non-trivial request —…
This skill should be used for any non-trivial request — features, bugs, stories, epics, spikes, or multi-step tasks. It accepts a ticket URL (Jira, Linear, GitHub), a file path containing a spec, or a plain-text prompt. It assembles an agent team, breaks the work into structured tasks, and manages the full lifecycle from research through implementation, code review, deploy, and empirical verification.
Baseado na classificação ocupacional SOC
Exibindo SKILL.md
| name | lisa-tracker-add-journey |
| description | Vendor-neutral wrapper for… |
| allowed-tools | ["Skill","Bash","Read"] |
Thin dispatcher. Resolves the configured destination tracker and delegates to the matching vendor skill.
See the config-resolution rule for configuration and dispatch table.
lisa-tracker-write)."No tracker configured in .lisa.config.json. Run /lisa:setup:jira, /lisa:setup:github, or /lisa:setup:linear first."jira → invoke lisa-jira-add-journey with $ARGUMENTS verbatim. Arg: a JIRA ticket key.github → invoke lisa-github-add-journey with $ARGUMENTS verbatim. Arg: org/repo#<number> or a GitHub issue URL.linear → invoke lisa-linear-add-journey with $ARGUMENTS verbatim. Arg: a Linear Issue identifier (e.g., ENG-123)."Unknown tracker '<value>' in .lisa.config.json. Expected 'jira', 'github', or 'linear'."[EVIDENCE: <artifact-type>: <name>] markers per the verification rule taxonomy). The only difference is how the section is appended — JIRA via editJiraIssue (Jira wiki markup), GitHub via gh issue edit --body-file (markdown), Linear via save_issue (markdown).[EVIDENCE-REF: <work-item-ref> | <artifact-type>: <kebab-case-name>]. It is non-claiming and never replaces a runtime-changing leaf's local S14 marker.[EVIDENCE: ...] marker, the vendor skill reports it and stops. A reference-only journey is incomplete; the vendor skill preserves its prose and appends the missing local evidence. This shim does not retry.