@codyswann/lisa 2.38.0 → 2.39.1

package/package.json

@@ -82,7 +82,7 @@
     "lodash": ">=4.18.1"
   },
   "name": "@codyswann/lisa",
-  "version": "2.38.0",
+  "version": "2.39.1",
   "description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
   "main": "dist/index.js",
   "exports": {

package/plugins/lisa/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "2.38.0",
+  "version": "2.39.1",
   "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "2.38.0",
+  "version": "2.39.1",
   "description": "Universal governance: agents, skills, commands, hooks, and rules for all projects.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa/skills/acceptance-criteria/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "acceptance-criteria"
-short_description: "Acceptance criteria definition. Gherkin user flows (Given/When/Then), error states, UX concerns, and empirical verification from the user perspective."
+display_name: "Acceptance Criteria"
+short_description: "Acceptance criteria definition"
 default_prompt:
-  - "Use $acceptance-criteria"
+  - "Use $acceptance-criteria: Acceptance criteria definition."

package/plugins/lisa/skills/agent-design-best-practices/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "agent-design-best-practices"
-short_description: "Best practices for designing Claude Code agent files (.claude/agents/*.md). This skill should be used when writing or reviewing agent markdown files to ensure proper design with focused domains, correct tool access, reusable definitions, and separation of capabilities from lifecycle. Combines Anthropic's official guidance with battle-tested patterns from agent team usage."
+display_name: "Agent Design Best Practices"
+short_description: "Best practices for designing Claude Code agent files (.claude/agents/*.md)"
 default_prompt:
-  - "Use $agent-design-best-practices"
+  - "Use $agent-design-best-practices: Best practices for designing Claude Code agent files (.claude/agents/*.md)."

package/plugins/lisa/skills/atlassian-access/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "atlassian-access"
-short_description: "Vendor-neutral access layer for Atlassian (JIRA + Confluence). Every jira-* and confluence-* skill MUST delegate through this skill rather than calling Atlassian directly. Resolves a substrate per operation in this order: (1) acli if installed and its active profile matches the configured site, (2) Atlassian MCP if authenticated and the configured cloudId is in its accessible resources, (3) curl + API-token Basic auth. Verifies the active connection matches `.lisa.config.json` before every operation — substrates authenticated as a different Atlassian account are skipped, not used."
+display_name: "Atlassian Access"
+short_description: "Vendor-neutral access layer for Atlassian (JIRA + Confluence)"
 default_prompt:
-  - "Use $atlassian-access"
+  - "Use $atlassian-access: Vendor-neutral access layer for Atlassian (JIRA + Confluence)."

package/plugins/lisa/skills/bug-triage/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "bug-triage"
-short_description: "8-step bug triage and implementation workflow. Ensures bugs are reproducible, root-caused, and fixable before implementation begins."
+display_name: "Bug Triage"
+short_description: "8-step bug triage and implementation workflow"
 default_prompt:
-  - "Use $bug-triage"
+  - "Use $bug-triage: 8-step bug triage and implementation workflow."

package/plugins/lisa/skills/codebase-research/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "codebase-research"
-short_description: "Codebase exploration and architecture analysis. Read files, trace data flow, identify modification points, map dependencies, find reusable code, evaluate design patterns."
+display_name: "Codebase Research"
+short_description: "Codebase exploration and architecture analysis"
 default_prompt:
-  - "Use $codebase-research"
+  - "Use $codebase-research: Codebase exploration and architecture analysis."

package/plugins/lisa/skills/codify-verification/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "codify-verification"
-short_description: "Convert empirical verification into a regression test so it never has to be re-proven manually. Runs after a verification passes — picks the appropriate test framework for the verification type (Playwright for UI/browser, integration test for API/DB/auth, benchmark for performance, etc.), generates the test, wires it into the project's test runner, and confirms it executes. Mandatory step in the verification lifecycle and in the Build/Fix/Improve flows."
+display_name: "Codify Verification"
+short_description: "Convert empirical verification into a regression test so it never has to be re-proven manually"
 default_prompt:
-  - "Use $codify-verification"
+  - "Use $codify-verification: Convert empirical verification into a regression test so it never has to be re-proven manually."

package/plugins/lisa/skills/confluence-prd-intake/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "confluence-prd-intake"
-short_description: "Scans a Confluence space (or a parent page) for PRD pages currently parented under the configured `ready` lifecycle page and runs each one through the dry-run validation pipeline. PRDs that pass every gate get tickets written and are re-parented under the `ticketed` lifecycle page; PRDs that fail get clarifying-question comments and are re-parented under the `blocked` lifecycle page. Confluence counterpart of `lisa:notion-prd-intake` — the workflow is identical; only the source-of-truth tools and the state encoding differ (parent-page re-parenting instead of a status property). Composes existing skills (confluence-to-tracker, tracker-validate, tracker-source-artifacts, product-walkthrough)."
+display_name: "Confluence PRD Intake"
+short_description: "Scans a Confluence space (or a parent page) for PRD pages currently parented under the configured `ready` lifecycle page and runs each one…"
 default_prompt:
-  - "Use $confluence-prd-intake"
+  - "Use $confluence-prd-intake: Scans a Confluence space (or a parent page) for PRD pages currently parented under the configured `ready` lifecycle page and runs each one…."

package/plugins/lisa/skills/confluence-to-tracker/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "confluence-to-tracker"
+display_name: "Confluence To Tracker"
 short_description: ">"
 default_prompt:
-  - "Use $confluence-to-tracker"
+  - "Use $confluence-to-tracker: >."

package/plugins/lisa/skills/debrief/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "debrief"
-short_description: "Run the Debrief flow over a shipped initiative. Input: a PRD URL (Notion / Confluence / Linear / GitHub Issue / file), a JIRA epic key, or a GitHub epic issue URL. Output: a triage-ready learnings document covering every work item in the initiative — edge cases, gotchas, process friction, tooling gaps, convention drift — each with structured evidence and a human-disposition field. Persistence is deferred to lisa:debrief-apply."
+display_name: "Debrief"
+short_description: "Run the Debrief flow over a shipped initiative"
 default_prompt:
-  - "Use $debrief"
+  - "Use $debrief: Run the Debrief flow over a shipped initiative."

package/plugins/lisa/skills/debrief-apply/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "debrief-apply"
-short_description: "Apply human-marked dispositions from a Debrief triage document. Reads the triage doc produced by lisa:debrief, parses each row's disposition (Accept / Reject / Defer), and routes Accepted items to their persistence destination. Deterministic and idempotent — safe to re-run if dispositions are added incrementally."
+display_name: "Debrief Apply"
+short_description: "Apply human-marked dispositions from a Debrief triage document"
 default_prompt:
-  - "Use $debrief-apply"
+  - "Use $debrief-apply: Apply human-marked dispositions from a Debrief triage document."

package/plugins/lisa/skills/epic-triage/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "epic-triage"
-short_description: "9-step epic triage and 5-step implementation workflow. Ensures epics are fully scoped, broken down, and ordered before execution begins."
+display_name: "Epic Triage"
+short_description: "9-step epic triage and 5-step implementation workflow"
 default_prompt:
-  - "Use $epic-triage"
+  - "Use $epic-triage: 9-step epic triage and 5-step implementation workflow."

package/plugins/lisa/skills/fix-linter-error/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "fix-linter-error"
-short_description: "This skill should be used when fixing all violations of one or more ESLint rules across the codebase. It runs the linter, groups violations by rule and file, generates a brief with fix strategies, and creates a plan with tasks to implement the fixes."
+display_name: "Fix Linter Error"
+short_description: "fixing all violations of one or more ESLint rules across the codebase"
 default_prompt:
-  - "Use $fix-linter-error"
+  - "Use $fix-linter-error: fixing all violations of one or more ESLint rules across the codebase."

package/plugins/lisa/skills/git-commit/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "git-commit"
-short_description: "This skill should be used when creating conventional commits for current changes. It groups related changes into logical commits, ensures all files are committed, and verifies the working directory is clean afterward."
+display_name: "Git Commit"
+short_description: "creating conventional commits for current changes"
 default_prompt:
-  - "Use $git-commit"
+  - "Use $git-commit: creating conventional commits for current changes."

package/plugins/lisa/skills/git-prune/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "git-prune"
-short_description: "This skill should be used when pruning local branches that have been deleted on the remote. It fetches remote changes, identifies stale local branches, and safely deletes them."
+display_name: "Git Prune"
+short_description: "pruning local branches that have been deleted on the remote"
 default_prompt:
-  - "Use $git-prune"
+  - "Use $git-prune: pruning local branches that have been deleted on the remote."

package/plugins/lisa/skills/git-submit-pr/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "git-submit-pr"
-short_description: "This skill should be used when pushing changes and creating or updating a pull request. It verifies the branch state, pushes to remote, creates or updates a PR with a comprehensive description, and enables auto-merge."
+display_name: "Git Submit PR"
+short_description: "pushing changes and creating or updating a pull request"
 default_prompt:
-  - "Use $git-submit-pr"
+  - "Use $git-submit-pr: pushing changes and creating or updating a pull request."

package/plugins/lisa/skills/github-add-journey/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "github-add-journey"
-short_description: "Add a Validation Journey section to an existing GitHub Issue by analyzing the change type and generating appropriate verification steps with evidence markers. The GitHub counterpart of lisa:jira-add-journey."
+display_name: "Github Add Journey"
+short_description: "Add a Validation Journey section to an existing GitHub Issue by analyzing the change type and generating appropriate verification steps…"
 default_prompt:
-  - "Use $github-add-journey"
+  - "Use $github-add-journey: Add a Validation Journey section to an existing GitHub Issue by analyzing the change type and generating appropriate verification steps…."

package/plugins/lisa/skills/github-build-intake/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "github-build-intake"
-short_description: "GitHub counterpart to lisa:jira-build-intake. Scans a GitHub repository for issues carrying the configured `ready` build label, claims each leaf work unit by relabeling to the configured `claimed` label, runs the implementation/build flow via lisa:github-agent, and relabels to the configured `done` label on completion. Enforces the claim-time arm of the `leaf-only-lifecycle` rule: a parent/container with open child work (or a childless Epic/Story/Spike) that still carries a stale build-ready label is skipped or safe-blocked with a lifecycle-repair comment, never claimed. The `ready` label is the human-flipped signal that an issue is truly ready for development — mirroring how Notion PRDs work product Draft → Ready → (us) In Review → Blocked|Ticketed."
+display_name: "Github Build Intake"
+short_description: "GitHub counterpart to lisa:jira-build-intake"
 default_prompt:
-  - "Use $github-build-intake"
+  - "Use $github-build-intake: GitHub counterpart to lisa:jira-build-intake."

package/plugins/lisa/skills/github-create/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "github-create"
-short_description: "This skill should be used when creating GitHub Issue Epics, Stories, and Sub-tasks from code files or descriptions. It analyzes the provided input, determines the appropriate issue hierarchy, and creates issues with comprehensive quality requirements including test-first development and documentation. The GitHub counterpart of lisa:jira-create."
+display_name: "Github Create"
+short_description: "creating GitHub Issue Epics, Stories, and Sub-tasks from code files or descriptions"
 default_prompt:
-  - "Use $github-create"
+  - "Use $github-create: creating GitHub Issue Epics, Stories, and Sub-tasks from code files or descriptions."

package/plugins/lisa/skills/github-evidence/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "github-evidence"
-short_description: "Upload text evidence to the GitHub `pr-assets` release, update PR description, post a GitHub Issue comment with code blocks, and relabel the issue to the configured `review` label (default `status:code-review`). Reusable by any skill that captures evidence and generates evidence/comment.md (and optionally evidence/comment.txt). The GitHub counterpart of lisa:jira-evidence."
+display_name: "Github Evidence"
+short_description: "Upload text evidence to the GitHub `pr-assets` release, update PR description, post a GitHub Issue comment with code blocks, and relabel…"
 default_prompt:
-  - "Use $github-evidence"
+  - "Use $github-evidence: Upload text evidence to the GitHub `pr-assets` release, update PR description, post a GitHub Issue comment with code blocks, and relabel…."

package/plugins/lisa/skills/github-journey/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "github-journey"
-short_description: "Parse a GitHub Issue's Validation Journey section, execute the verification steps using appropriate tools (curl, test commands, database queries), capture evidence at each marker, and post results via lisa:github-evidence. The GitHub counterpart of lisa:jira-journey."
+display_name: "Github Journey"
+short_description: "Parse a GitHub Issue's Validation Journey section, execute the verification steps using appropriate tools (curl, test commands, database…"
 default_prompt:
-  - "Use $github-journey"
+  - "Use $github-journey: Parse a GitHub Issue's Validation Journey section, execute the verification steps using appropriate tools (curl, test commands, database…."

package/plugins/lisa/skills/github-prd-intake/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "github-prd-intake"
-short_description: "Scans a GitHub repository for issues carrying the configured `ready` PRD label and runs each one through the dry-run validation pipeline. PRDs that pass every gate get tickets written (to whatever destination tracker is configured — JIRA, GitHub Issues itself, or Linear) and the label flipped to the configured `ticketed` label; PRDs that fail get clarifying-question comments and the label flipped to the configured `blocked` label. The GitHub counterpart of lisa:notion-prd-intake / lisa:confluence-prd-intake / lisa:linear-prd-intake. Composes existing skills (github-to-tracker, tracker-validate, tracker-source-artifacts, product-walkthrough)."
+display_name: "Github PRD Intake"
+short_description: "Scans a GitHub repository for issues carrying the configured `ready` PRD label and runs each one through the dry-run validation pipeline"
 default_prompt:
-  - "Use $github-prd-intake"
+  - "Use $github-prd-intake: Scans a GitHub repository for issues carrying the configured `ready` PRD label and runs each one through the dry-run validation pipeline."

package/plugins/lisa/skills/github-read-issue/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "github-read-issue"
-short_description: "Fetches the full scope of a GitHub Issue — metadata, body sections, all comments, native sub-issue parent and children, linked PRs, related issues parsed from `Blocks/Blocked by/Relates to/Duplicates/Cloned from` lines, and any cross-repo references. Produces a consolidated context bundle that downstream agents consume so they never act on an issue in isolation. The GitHub counterpart of lisa:jira-read-ticket."
+display_name: "Github Read Issue"
+short_description: "Fetches the full scope of a GitHub Issue — metadata, body sections, all comments, native sub-issue parent and children, linked PRs, related…"
 default_prompt:
-  - "Use $github-read-issue"
+  - "Use $github-read-issue: Fetches the full scope of a GitHub Issue — metadata, body sections, all comments, native sub-issue parent and children, linked PRs, related…."

package/plugins/lisa/skills/github-sync/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "github-sync"
-short_description: "Syncs plan progress to a linked GitHub Issue. Posts plan contents, progress updates, branch links, and PR links at key milestones. Use this skill throughout the plan lifecycle to keep issues in sync. The GitHub counterpart of lisa:jira-sync."
+display_name: "Github Sync"
+short_description: "Syncs plan progress to a linked GitHub Issue"
 default_prompt:
-  - "Use $github-sync"
+  - "Use $github-sync: Syncs plan progress to a linked GitHub Issue."

package/plugins/lisa/skills/github-to-tracker/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "github-to-tracker"
+display_name: "Github To Tracker"
 short_description: ">"
 default_prompt:
-  - "Use $github-to-tracker"
+  - "Use $github-to-tracker: >."

package/plugins/lisa/skills/github-validate-issue/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "github-validate-issue"
-short_description: "Validates a proposed GitHub Issue spec (or an existing issue) against the organizational quality gates without writing anything. Returns a structured PASS/FAIL report per gate with concrete remediation. The GitHub counterpart of lisa:jira-validate-ticket — same gate definitions, translated to the GitHub Issues data model. Single source of truth for what makes a valid GitHub Issue. Both the write path (github-write-issue runs it pre-write) and the dry-run path (github-to-tracker runs it during PRD intake) call this skill."
+display_name: "Github Validate Issue"
+short_description: "Validates a proposed GitHub Issue spec (or an existing issue) against the organizational quality gates without writing anything"
 default_prompt:
-  - "Use $github-validate-issue"
+  - "Use $github-validate-issue: Validates a proposed GitHub Issue spec (or an existing issue) against the organizational quality gates without writing anything."

package/plugins/lisa/skills/github-verify/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "github-verify"
-short_description: "This skill should be used when verifying that a GitHub Issue meets organizational standards for parent-sub-issue relationships and description quality. It fetches the live issue and delegates the gate checks to github-validate-issue so the bar matches what github-write-issue enforces pre-write. The GitHub counterpart of lisa:jira-verify."
+display_name: "Github Verify"
+short_description: "verifying that a GitHub Issue meets organizational standards for parent-sub-issue relationships and description quality"
 default_prompt:
-  - "Use $github-verify"
+  - "Use $github-verify: verifying that a GitHub Issue meets organizational standards for parent-sub-issue relationships and description quality."

package/plugins/lisa/skills/github-write-issue/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "github-write-issue"
-short_description: "Creates or updates a GitHub Issue following the same organizational best practices as lisa:jira-write-ticket — three-audience description, Gherkin acceptance criteria, parent sub-issue (Epic/Story hierarchy), explicit relationship discovery, remote links, labels for status/components/priority/story-points, and Validation Journey. Uses the `gh` CLI exclusively (no MCP). Rejects thin issues. The GitHub counterpart of lisa:jira-write-ticket."
+display_name: "Github Write Issue"
+short_description: "Creates or updates a GitHub Issue following the same organizational best practices as lisa:jira-write-ticket — three-audience description…"
 default_prompt:
-  - "Use $github-write-issue"
+  - "Use $github-write-issue: Creates or updates a GitHub Issue following the same organizational best practices as lisa:jira-write-ticket — three-audience description…."

package/plugins/lisa/skills/implement/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "implement"
-short_description: "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."
+display_name: "Implement"
+short_description: "any non-trivial request — features, bugs, stories, epics, spikes, or multi-step tasks"
 default_prompt:
-  - "Use $implement"
+  - "Use $implement: any non-trivial request — features, bugs, stories, epics, spikes, or multi-step tasks."

package/plugins/lisa/skills/improve-code-complexity/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "improve-code-complexity"
-short_description: "This skill should be used when reducing the cognitive complexity threshold of the codebase. It lowers the threshold by 2, identifies functions that exceed the new limit, generates a brief with refactoring strategies, and creates a plan with tasks to fix all violations."
+display_name: "Improve Code Complexity"
+short_description: "reducing the cognitive complexity threshold of the codebase"
 default_prompt:
-  - "Use $improve-code-complexity"
+  - "Use $improve-code-complexity: reducing the cognitive complexity threshold of the codebase."

package/plugins/lisa/skills/improve-max-lines/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "improve-max-lines"
-short_description: "This skill should be used when reducing the maximum file lines threshold and fixing all violations. It updates the eslint threshold configuration, identifies files exceeding the new limit, generates a brief with refactoring strategies, and creates a plan with tasks to split oversized files."
+display_name: "Improve Max Lines"
+short_description: "reducing the maximum file lines threshold and fixing all violations"
 default_prompt:
-  - "Use $improve-max-lines"
+  - "Use $improve-max-lines: reducing the maximum file lines threshold and fixing all violations."

package/plugins/lisa/skills/improve-max-lines-per-function/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "improve-max-lines-per-function"
-short_description: "This skill should be used when reducing the maximum lines per function threshold and fixing all violations. It updates the eslint threshold configuration, identifies functions exceeding the new limit, generates a brief with refactoring strategies, and creates a plan with tasks to split oversized functions."
+display_name: "Improve Max Lines Per Function"
+short_description: "reducing the maximum lines per function threshold and fixing all violations"
 default_prompt:
-  - "Use $improve-max-lines-per-function"
+  - "Use $improve-max-lines-per-function: reducing the maximum lines per function threshold and fixing all violations."

package/plugins/lisa/skills/improve-test-coverage/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "improve-test-coverage"
-short_description: "This skill should be used when increasing test coverage to a specified threshold percentage. It runs the coverage report, identifies files with the lowest coverage, generates a brief with coverage gaps, and creates a plan with tasks to add the missing tests."
+display_name: "Improve Test Coverage"
+short_description: "increasing test coverage to a specified threshold percentage"
 default_prompt:
-  - "Use $improve-test-coverage"
+  - "Use $improve-test-coverage: increasing test coverage to a specified threshold percentage."

package/plugins/lisa/skills/improve-tests/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "improve-tests"
-short_description: "This skill should be used when improving test quality. It scans the test suite for weak, brittle, or poorly-written tests, generates a brief with improvement opportunities, and creates a plan with tasks to strengthen the tests."
+display_name: "Improve Tests"
+short_description: "improving test quality"
 default_prompt:
-  - "Use $improve-tests"
+  - "Use $improve-tests: improving test quality."

package/plugins/lisa/skills/intake/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "intake"
-short_description: "Vendor-agnostic batch scanner for Ready queues. Given a Notion PRD database URL → finds Ready PRDs and runs lisa:plan per item. Given a Confluence space or parent page URL → finds prd-ready PRDs and runs lisa:plan per item. Given a Linear workspace URL or team key → finds prd-ready Linear projects and runs lisa:plan per item. Given a GitHub repo URL or `org/repo` token → finds prd-ready GitHub issues and runs lisa:plan per item. Given a JIRA project key or JQL filter → finds Ready tickets and runs lisa:implement per item. Given a GitHub repo URL or `org/repo` token when `tracker = github` → finds `status:ready` issues and runs lisa:implement per item. Designed as the cron target for /schedule — one cycle per invocation, processes everything currently Ready, exits cleanly on empty. Symmetric counterpart to the single-item lisa:plan and lisa:implement skills."
+display_name: "Intake"
+short_description: "Vendor-agnostic batch scanner for Ready queues"
 default_prompt:
-  - "Use $intake"
+  - "Use $intake: Vendor-agnostic batch scanner for Ready queues."

package/plugins/lisa/skills/jira-add-journey/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "jira-add-journey"
-short_description: "Add a Validation Journey section to an existing JIRA ticket by analyzing the change type and generating appropriate verification steps with evidence markers."
+display_name: "Jira Add Journey"
+short_description: "Add a Validation Journey section to an existing JIRA ticket by analyzing the change type and generating appropriate verification steps with…"
 default_prompt:
-  - "Use $jira-add-journey"
+  - "Use $jira-add-journey: Add a Validation Journey section to an existing JIRA ticket by analyzing the change type and generating appropriate verification steps with…."

package/plugins/lisa/skills/jira-build-intake/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "jira-build-intake"
-short_description: "Symmetric counterpart to notion-prd-intake on the JIRA side. Scans a JIRA project (or JQL filter) for tickets in the configured `ready` status, claims each by transitioning to the configured `claimed` status, runs the implementation/build flow via jira-agent, and transitions to the configured `done` status on completion. Enforces the claim-time arm of the `leaf-only-lifecycle` rule: a parent/container with open child work (or a childless Epic/Story/Spike) that still carries a stale build-ready status is skipped or safe-blocked with a lifecycle-repair comment, never claimed. The `ready` status is the human-flipped signal that a TODO ticket is truly ready for development — mirroring how Notion PRDs work product Draft → Ready → (us) In Review → Blocked|Ticketed."
+display_name: "Jira Build Intake"
+short_description: "Symmetric counterpart to notion-prd-intake on the JIRA side"
 default_prompt:
-  - "Use $jira-build-intake"
+  - "Use $jira-build-intake: Symmetric counterpart to notion-prd-intake on the JIRA side."

package/plugins/lisa/skills/jira-create/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "jira-create"
-short_description: "This skill should be used when creating JIRA epics, stories, and tasks from code files or descriptions. It analyzes the provided input, determines the appropriate issue hierarchy, and creates issues with comprehensive quality requirements including test-first development and documentation."
+display_name: "Jira Create"
+short_description: "creating JIRA epics, stories, and tasks from code files or descriptions"
 default_prompt:
-  - "Use $jira-create"
+  - "Use $jira-create: creating JIRA epics, stories, and tasks from code files or descriptions."

package/plugins/lisa/skills/jira-evidence/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "jira-evidence"
-short_description: "Upload text evidence to GitHub pr-assets release, update PR description, post JIRA comment with code blocks, and move ticket to the configured code-review status. Reusable by any skill that captures evidence and generates evidence/comment.txt + evidence/comment.md."
+display_name: "Jira Evidence"
+short_description: "Upload text evidence to GitHub pr-assets release, update PR description, post JIRA comment with code blocks, and move ticket to the…"
 default_prompt:
-  - "Use $jira-evidence"
+  - "Use $jira-evidence: Upload text evidence to GitHub pr-assets release, update PR description, post JIRA comment with code blocks, and move ticket to the…."

package/plugins/lisa/skills/jira-journey/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "jira-journey"
-short_description: "Parse a JIRA ticket's Validation Journey section, execute the verification steps using appropriate tools (curl, test commands, database queries), capture evidence, and post to JIRA + GitHub PR using the jira-evidence skill."
+display_name: "Jira Journey"
+short_description: "Parse a JIRA ticket's Validation Journey section, execute the verification steps using appropriate tools (curl, test commands, database…"
 default_prompt:
-  - "Use $jira-journey"
+  - "Use $jira-journey: Parse a JIRA ticket's Validation Journey section, execute the verification steps using appropriate tools (curl, test commands, database…."

package/plugins/lisa/skills/jira-read-ticket/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "jira-read-ticket"
-short_description: "Fetches the full scope of a JIRA ticket — metadata, description, acceptance criteria, all comments, remote links (PRs, Confluence, dashboards), issue links (blocks/is blocked by/relates to/duplicates/clones), epic parent with siblings, and subtasks. Produces a consolidated context bundle that downstream agents consume so they never act on a single ticket in isolation."
+display_name: "Jira Read Ticket"
+short_description: "Fetches the full scope of a JIRA ticket — metadata, description, acceptance criteria, all comments, remote links (PRs, Confluence…"
 default_prompt:
-  - "Use $jira-read-ticket"
+  - "Use $jira-read-ticket: Fetches the full scope of a JIRA ticket — metadata, description, acceptance criteria, all comments, remote links (PRs, Confluence…."

package/plugins/lisa/skills/jira-sync/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "jira-sync"
-short_description: "Syncs plan progress to a linked JIRA ticket. Posts plan contents, progress updates, branch links, and PR links at key milestones. Use this skill throughout the plan lifecycle to keep tickets in sync."
+display_name: "Jira Sync"
+short_description: "Syncs plan progress to a linked JIRA ticket"
 default_prompt:
-  - "Use $jira-sync"
+  - "Use $jira-sync: Syncs plan progress to a linked JIRA ticket."

package/plugins/lisa/skills/jira-validate-ticket/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "jira-validate-ticket"
-short_description: "Validates a proposed JIRA ticket spec (or an existing ticket) against the organizational quality gates without writing anything. Returns a structured PASS/FAIL report per gate with concrete remediation. This is the single source of truth for what makes a valid ticket — both the write path (jira-write-ticket runs it pre-write) and the dry-run path (notion-to-tracker runs it during PRD intake) call this skill so the bar can never drift."
+display_name: "Jira Validate Ticket"
+short_description: "Validates a proposed JIRA ticket spec (or an existing ticket) against the organizational quality gates without writing anything"
 default_prompt:
-  - "Use $jira-validate-ticket"
+  - "Use $jira-validate-ticket: Validates a proposed JIRA ticket spec (or an existing ticket) against the organizational quality gates without writing anything."

package/plugins/lisa/skills/jira-verify/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "jira-verify"
-short_description: "This skill should be used when verifying that a JIRA ticket meets organizational standards for epic relationships and description quality. It fetches the live ticket and delegates the gate checks to jira-validate-ticket so the bar matches what jira-write-ticket enforces pre-write."
+display_name: "Jira Verify"
+short_description: "verifying that a JIRA ticket meets organizational standards for epic relationships and description quality"
 default_prompt:
-  - "Use $jira-verify"
+  - "Use $jira-verify: verifying that a JIRA ticket meets organizational standards for epic relationships and description quality."

package/plugins/lisa/skills/jira-write-ticket/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "jira-write-ticket"
-short_description: "Creates or updates a JIRA ticket following organizational best practices. Enforces description quality (coding assistant / developer / stakeholder sections), Gherkin acceptance criteria, epic parent relationship, explicit link discovery (blocks / is blocked by / relates to / duplicates / clones), remote links (PRs, Confluence, dashboards), labels, components, fix version, priority, story points, and Validation Journey. Rejects thin tickets — use this skill any time a ticket is created or significantly edited."
+display_name: "Jira Write Ticket"
+short_description: "Creates or updates a JIRA ticket following organizational best practices"
 default_prompt:
-  - "Use $jira-write-ticket"
+  - "Use $jira-write-ticket: Creates or updates a JIRA ticket following organizational best practices."

package/plugins/lisa/skills/jsdoc-best-practices/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "jsdoc-best-practices"
-short_description: "Enforces JSDoc documentation standards for this TypeScript project. This skill should be used when writing or reviewing TypeScript code to ensure proper documentation with file preambles, function docs, interface docs, and the critical distinction between documenting \"what\" vs \"why\". Use this skill to understand the project's JSDoc ESLint rules and established patterns."
+display_name: "Jsdoc Best Practices"
+short_description: "Enforces JSDoc documentation standards for this TypeScript project"
 default_prompt:
-  - "Use $jsdoc-best-practices"
+  - "Use $jsdoc-best-practices: Enforces JSDoc documentation standards for this TypeScript project."

package/plugins/lisa/skills/linear-add-journey/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "linear-add-journey"
-short_description: "Add a Validation Journey section to an existing Linear Issue by analyzing the change type and generating appropriate verification steps with evidence markers. Linear counterpart of lisa:jira-add-journey."
+display_name: "Linear Add Journey"
+short_description: "Add a Validation Journey section to an existing Linear Issue by analyzing the change type and generating appropriate verification steps…"
 default_prompt:
-  - "Use $linear-add-journey"
+  - "Use $linear-add-journey: Add a Validation Journey section to an existing Linear Issue by analyzing the change type and generating appropriate verification steps…."

package/plugins/lisa/skills/linear-build-intake/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "linear-build-intake"
-short_description: "Symmetric counterpart to lisa:jira-build-intake on the Linear side. Scans a Linear team for Issues carrying the configured `ready` build label, claims each by relabeling to the configured `claimed` label, runs the implementation/build flow via lisa:linear-agent, and relabels to the configured `done` label on completion. Enforces the claim-time arm of the `leaf-only-lifecycle` rule: a parent/container with open child work (or a childless Epic/Story/Spike) that still carries a stale build-ready label is skipped or safe-blocked with a lifecycle-repair comment, never claimed. The `ready` label is the human-flipped signal that an Issue is truly ready for development — mirroring how Notion PRDs work Draft → Ready → (us) In Review → Blocked|Ticketed."
+display_name: "Linear Build Intake"
+short_description: "Symmetric counterpart to lisa:jira-build-intake on the Linear side"
 default_prompt:
-  - "Use $linear-build-intake"
+  - "Use $linear-build-intake: Symmetric counterpart to lisa:jira-build-intake on the Linear side."

package/plugins/lisa/skills/linear-create/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "linear-create"
-short_description: "Creates Linear Projects (Epic-equivalent), Issues (Story / Task / Bug / Spike), and sub-Issues (Sub-task) from code files or descriptions. Analyzes the input, determines the appropriate hierarchy, and creates items with comprehensive quality requirements including test-first development and Validation Journey. The Linear counterpart of lisa:jira-create — delegates every write to lisa:linear-write-issue."
+display_name: "Linear Create"
+short_description: "Creates Linear Projects (Epic-equivalent), Issues (Story / Task / Bug / Spike), and sub-Issues (Sub-task) from code files or descriptions"
 default_prompt:
-  - "Use $linear-create"
+  - "Use $linear-create: Creates Linear Projects (Epic-equivalent), Issues (Story / Task / Bug / Spike), and sub-Issues (Sub-task) from code files or descriptions."

package/plugins/lisa/skills/linear-evidence/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "linear-evidence"
-short_description: "Uploads text evidence to the GitHub `pr-assets` release, updates the PR description, posts a comment on the originating Linear Issue with code blocks, and transitions the Issue from the configured `claimed` label to the configured `review` label. Reusable by any skill that captures evidence and generates evidence/comment.txt + evidence/code-blocks.md. Linear counterpart of lisa:jira-evidence and lisa:github-evidence."
+display_name: "Linear Evidence"
+short_description: "Uploads text evidence to the GitHub `pr-assets` release, updates the PR description, posts a comment on the originating Linear Issue with…"
 default_prompt:
-  - "Use $linear-evidence"
+  - "Use $linear-evidence: Uploads text evidence to the GitHub `pr-assets` release, updates the PR description, posts a comment on the originating Linear Issue with…."

package/plugins/lisa/skills/linear-journey/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "linear-journey"
-short_description: "Parse a Linear Issue's Validation Journey section, execute the verification steps using appropriate tools (curl, test commands, database queries, Playwright), capture evidence at each [EVIDENCE: name] marker, and post to Linear + GitHub PR using the linear-evidence skill. Linear counterpart of lisa:jira-journey."
+display_name: "Linear Journey"
+short_description: "Parse a Linear Issue's Validation Journey section, execute the verification steps using appropriate tools (curl, test commands, database…"
 default_prompt:
-  - "Use $linear-journey"
+  - "Use $linear-journey: Parse a Linear Issue's Validation Journey section, execute the verification steps using appropriate tools (curl, test commands, database…."

package/plugins/lisa/skills/linear-prd-intake/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "linear-prd-intake"
-short_description: "Scans a Linear workspace (or a specific team) for projects carrying the configured `ready` PRD label and runs each one through the dry-run validation pipeline. Projects that pass every gate get tickets written and the label flipped to the configured `ticketed` label; projects that fail get clarifying-question comments (on a sentinel feedback issue under the project) and the label flipped to the configured `blocked` label. Linear counterpart of `lisa:notion-prd-intake` and `lisa:confluence-prd-intake` — the workflow is identical; only the source-of-truth tools differ. Composes existing skills (linear-to-tracker, tracker-validate, tracker-source-artifacts, product-walkthrough)."
+display_name: "Linear PRD Intake"
+short_description: "Scans a Linear workspace (or a specific team) for projects carrying the configured `ready` PRD label and runs each one through the dry-run…"
 default_prompt:
-  - "Use $linear-prd-intake"
+  - "Use $linear-prd-intake: Scans a Linear workspace (or a specific team) for projects carrying the configured `ready` PRD label and runs each one through the dry-run…."

package/plugins/lisa/skills/linear-read-issue/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "linear-read-issue"
-short_description: "Fetches the full scope of a Linear work item — Issue or Project — including metadata, description, acceptance criteria, all comments, attachments, native relations (blocks/blocked_by/relates_to/duplicates), Project parent (if any) with siblings, and sub-Issues. Produces a consolidated context bundle that downstream agents consume so they never act on a single item in isolation."
+display_name: "Linear Read Issue"
+short_description: "Fetches the full scope of a Linear work item — Issue or Project — including metadata, description, acceptance criteria, all comments…"
 default_prompt:
-  - "Use $linear-read-issue"
+  - "Use $linear-read-issue: Fetches the full scope of a Linear work item — Issue or Project — including metadata, description, acceptance criteria, all comments…."

package/plugins/lisa/skills/linear-sync/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "linear-sync"
-short_description: "Syncs plan progress to a linked Linear Issue. Posts plan contents, progress updates, branch links, and PR links at key milestones. Use this skill throughout the plan lifecycle to keep Linear Issues in sync. The Linear counterpart of lisa:jira-sync and lisa:github-sync."
+display_name: "Linear Sync"
+short_description: "Syncs plan progress to a linked Linear Issue"
 default_prompt:
-  - "Use $linear-sync"
+  - "Use $linear-sync: Syncs plan progress to a linked Linear Issue."

package/plugins/lisa/skills/linear-to-tracker/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "linear-to-tracker"
+display_name: "Linear To Tracker"
 short_description: ">"
 default_prompt:
-  - "Use $linear-to-tracker"
+  - "Use $linear-to-tracker: >."

package/plugins/lisa/skills/linear-validate-issue/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "linear-validate-issue"
-short_description: "Validates a proposed Linear work item spec (Project, Issue, or sub-Issue) — or an existing Linear item — against the organizational quality gates without writing anything. Returns a structured PASS/FAIL report per gate with concrete remediation. Single source of truth for what makes a valid Linear item — both the write path (linear-write-issue runs it pre-write) and the dry-run path (linear-to-tracker runs it during PRD intake) call this skill so the bar can never drift."
+display_name: "Linear Validate Issue"
+short_description: "Validates a proposed Linear work item spec (Project, Issue, or sub-Issue) — or an existing Linear item — against the organizational quality…"
 default_prompt:
-  - "Use $linear-validate-issue"
+  - "Use $linear-validate-issue: Validates a proposed Linear work item spec (Project, Issue, or sub-Issue) — or an existing Linear item — against the organizational quality…."

package/plugins/lisa/skills/linear-verify/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "linear-verify"
-short_description: "Verifies a Linear work item meets organizational standards by fetching the live item and running it through lisa:linear-validate-issue. Catches anything dropped or reformatted on write — same gates as the pre-write check, but applied to what Linear actually stored. Read-only."
+display_name: "Linear Verify"
+short_description: "Verifies a Linear work item meets organizational standards by fetching the live item and running it through lisa:linear-validate-issue"
 default_prompt:
-  - "Use $linear-verify"
+  - "Use $linear-verify: Verifies a Linear work item meets organizational standards by fetching the live item and running it through lisa:linear-validate-issue."