@codyswann/lisa 2.37.0 → 2.38.0

package/package.json

@@ -82,7 +82,7 @@
     "lodash": ">=4.18.1"
   },
   "name": "@codyswann/lisa",
-  "version": "2.37.0",
+  "version": "2.38.0",
   "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.37.0",
+  "version": "2.38.0",
   "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.37.0",
+  "version": "2.38.0",
   "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

@@ -0,0 +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."
+default_prompt:
+  - "Use $acceptance-criteria"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $agent-design-best-practices"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $atlassian-access"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $bug-triage"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $codebase-research"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $codify-verification"

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

@@ -0,0 +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)."
+default_prompt:
+  - "Use $confluence-prd-intake"

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

@@ -0,0 +1,4 @@
+display_name: "confluence-to-tracker"
+short_description: ">"
+default_prompt:
+  - "Use $confluence-to-tracker"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $debrief"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $debrief-apply"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $epic-triage"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $fix-linter-error"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $git-commit"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $git-prune"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $git-submit-pr"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $github-add-journey"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $github-build-intake"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $github-create"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $github-evidence"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $github-journey"

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

@@ -0,0 +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)."
+default_prompt:
+  - "Use $github-prd-intake"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $github-read-issue"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $github-sync"

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

@@ -0,0 +1,4 @@
+display_name: "github-to-tracker"
+short_description: ">"
+default_prompt:
+  - "Use $github-to-tracker"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $github-validate-issue"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $github-verify"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $github-write-issue"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $implement"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $improve-code-complexity"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $improve-max-lines"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $improve-max-lines-per-function"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $improve-test-coverage"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $improve-tests"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $intake"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $jira-add-journey"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $jira-build-intake"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $jira-create"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $jira-evidence"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $jira-journey"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $jira-read-ticket"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $jira-sync"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $jira-validate-ticket"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $jira-verify"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $jira-write-ticket"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $jsdoc-best-practices"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $linear-add-journey"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $linear-build-intake"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $linear-create"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $linear-evidence"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $linear-journey"

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

@@ -0,0 +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)."
+default_prompt:
+  - "Use $linear-prd-intake"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $linear-read-issue"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $linear-sync"

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

@@ -0,0 +1,4 @@
+display_name: "linear-to-tracker"
+short_description: ">"
+default_prompt:
+  - "Use $linear-to-tracker"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $linear-validate-issue"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $linear-verify"

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

@@ -0,0 +1,4 @@
+display_name: "linear-write-issue"
+short_description: "Creates or updates a Linear work item — Project (Epic), Issue (Story), or sub-Issue (Sub-task) — following organizational best practices. Polymorphic: dispatches internally on issue_type to save_project (Epic) or save_issue (Story / Sub-task). Enforces description quality (three audiences), Gherkin acceptance criteria, project-as-parent for Stories, parentId for Sub-tasks, explicit relationship discovery (blocks / is blocked by / relates to / duplicates), labels, components-as-labels, project milestones for fix versions, native priority and estimate fields, and Validation Journey. Rejects thin items — use this skill any time a Linear work item is created or significantly edited."
+default_prompt:
+  - "Use $linear-write-issue"

package/plugins/lisa/skills/lisa-review-implementation/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "lisa-review-implementation"
+short_description: "This skill should be used when comparing a project's Lisa-managed files against Lisa's source templates to identify drift. It reads the project manifest, locates source templates, generates diffs for drifted files, and offers to upstream improvements back to Lisa."
+default_prompt:
+  - "Use $lisa-review-implementation"

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

@@ -0,0 +1,4 @@
+display_name: "monitor"
+short_description: "Monitor application health across environments. Checks health endpoints, recent logs (CloudWatch / Sentry / browser console), error-rate spikes, performance hotspots, pending migrations, and runs Playwright smoke flows when relevant. Routes to the stack-specific ops-specialist agent (Expo, Rails, etc.). Also invoked as the post-deploy step of the lisa:verify skill."
+default_prompt:
+  - "Use $monitor"

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

@@ -0,0 +1,4 @@
+display_name: "nightly-add-test-coverage"
+short_description: "Nightly direct-execution skill for increasing test coverage. Receives pre-computed threshold data, writes tests targeting coverage gaps, updates thresholds, commits, and creates a PR."
+default_prompt:
+  - "Use $nightly-add-test-coverage"

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

@@ -0,0 +1,4 @@
+display_name: "nightly-improve-tests"
+short_description: "Nightly direct-execution skill for improving test quality. In nightly mode, focuses on tests for recently changed files. In general mode, scans all tests for the weakest ones. Commits and creates a PR."
+default_prompt:
+  - "Use $nightly-improve-tests"

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

@@ -0,0 +1,4 @@
+display_name: "nightly-lower-code-complexity"
+short_description: "Nightly direct-execution skill for reducing code complexity thresholds. Receives pre-computed threshold data, refactors violations, updates thresholds, commits, and creates a PR."
+default_prompt:
+  - "Use $nightly-lower-code-complexity"

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

@@ -0,0 +1,4 @@
+display_name: "notion-access"
+short_description: "Vendor-neutral access layer for Notion. Every notion-* skill MUST delegate through this skill rather than invoking the Notion REST API or any Notion MCP directly. Resolves a substrate per operation in this order: (1) Notion MCP if authenticated and the configured prdDatabaseId is fetchable through it (identity-match), (2) curl + Bearer auth + internal-integration token. Verifies the active connection matches `.lisa.config.json` before every operation — substrates authenticated as a different Notion workspace are skipped, not used."
+default_prompt:
+  - "Use $notion-access"

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

@@ -0,0 +1,4 @@
+display_name: "notion-prd-intake"
+short_description: "Scans a Notion PRD database for pages in the configured `ready` status and runs each one through the dry-run validation pipeline. PRDs that pass every gate get tickets written and the status flipped to the configured `ticketed` value; PRDs that fail get clarifying-question comments and the status flipped to the configured `blocked` value. The skill is the runtime for the ready → in_review → blocked|ticketed lifecycle. Composes existing skills (notion-to-tracker, tracker-validate, tracker-source-artifacts, product-walkthrough); does not reimplement their logic."
+default_prompt:
+  - "Use $notion-prd-intake"

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

@@ -0,0 +1,4 @@
+display_name: "notion-to-tracker"
+short_description: ">"
+default_prompt:
+  - "Use $notion-to-tracker"

package/plugins/lisa/skills/performance-review/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "performance-review"
+short_description: "Performance review methodology. N+1 queries, inefficient algorithms, memory leaks, missing indexes, unnecessary re-renders, bundle size issues. Evidence-based recommendations."
+default_prompt:
+  - "Use $performance-review"

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

@@ -0,0 +1,4 @@
+display_name: "plan"
+short_description: "Decompose a single PRD or specification into ordered work items in the configured tracker. Vendor-agnostic — the source can be a Notion PRD URL, a Confluence PRD URL, a Linear project URL, a GitHub Issue URL, an existing JIRA epic key, a markdown file, or a free-form description; the destination tracker is whatever the project is configured to use via `.lisa.config.json` `tracker` (JIRA, GitHub Issues, or Linear). Single-PRD mode only — for batch scanning of all Ready PRDs in a queue, use the lisa:intake skill."
+default_prompt:
+  - "Use $plan"

package/plugins/lisa/skills/prd-backlink/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "prd-backlink"
+short_description: "Update a source PRD with a `## Tickets` section linking back to every work item created from it. Vendor-aware on the source side (Notion / Confluence / Linear / GitHub Issue / file) and tracker-agnostic on the ticket side. Idempotent — regenerates the section on each run rather than appending, so re-planning never accumulates stale links. Invoked by the *-to-tracker skills at the end of their pipeline and standalone if a PRD's Tickets section needs to be refreshed."
+default_prompt:
+  - "Use $prd-backlink"

package/plugins/lisa/skills/prd-ticket-coverage/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "prd-ticket-coverage"
+short_description: "Verifies that every requirement in a PRD (Notion, Confluence, Linear, or GitHub Issues) is covered by at least one created destination ticket (JIRA, GitHub Issues, or Linear) — no silent drops. Parses the PRD into atomic items (goals, user stories, functional/non-functional requirements, acceptance criteria, important notes), maps each to the created tickets, and produces a coverage matrix and verdict (COMPLETE / COMPLETE_WITH_SCOPE_CREEP / GAPS_FOUND / NO_TICKETS_FOUND). Used by notion-prd-intake / confluence-prd-intake / linear-prd-intake / github-prd-intake post-write to gate the Ticketed transition; can also be invoked standalone for after-the-fact audits."
+default_prompt:
+  - "Use $prd-ticket-coverage"

package/plugins/lisa/skills/product-walkthrough/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "product-walkthrough"
+short_description: "Methodology for evaluating the live product via a real browser (Playwright MCP) when planning work or evaluating a PRD. Reading a PRD or a mock without seeing the current product produces tickets that misjudge the change — this skill grounds the analysis in what actually exists today. Invoke this skill from notion-to-tracker (Phase 2b live-product walkthrough), jira-create, and any PRD intake flow whose work touches existing user-facing surfaces."
+default_prompt:
+  - "Use $product-walkthrough"

package/plugins/lisa/skills/pull-request-review/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "pull-request-review"
+short_description: "This skill should be used when checking for code review comments on a pull request and implementing them if required. It fetches PR metadata and comments, generates a brief from unresolved feedback, and bootstraps a project to address the review comments."
+default_prompt:
+  - "Use $pull-request-review"

package/plugins/lisa/skills/quality-review/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "quality-review"
+short_description: "Code quality review checklist. Correctness, coding philosophy compliance, test coverage, documentation quality. Findings ranked by severity in plain English."
+default_prompt:
+  - "Use $quality-review"

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

@@ -0,0 +1,4 @@
+display_name: "reproduce-bug"
+short_description: "How to create reliable bug reproduction scenarios. Covers failing tests, minimal scripts, environment verification, and reproduction evidence capture."
+default_prompt:
+  - "Use $reproduce-bug"

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

@@ -0,0 +1,4 @@
+display_name: "research"
+short_description: "Research a problem space and produce a PRD. Investigates the codebase, defines user flows, assesses technical feasibility, and outputs a specification ready to hand to the Plan flow. Vendor-agnostic — the resulting PRD lands wherever the configured destination is (Notion, Confluence, file, etc.)."
+default_prompt:
+  - "Use $research"

package/plugins/lisa/skills/review-local/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "review-local"
+short_description: "This skill should be used when performing a code review on local changes on the current branch compared to the main branch. It uses multiple parallel agents to check for bugs, CLAUDE.md compliance, git history context, previous PR comments, and code comment adherence, then scores and filters findings by confidence level."
+default_prompt:
+  - "Use $review-local"

package/plugins/lisa/skills/root-cause-analysis/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "root-cause-analysis"
+short_description: "Root cause analysis methodology. Evidence gathering from logs, execution path tracing, strategic log placement, and building irrefutable proof chains."
+default_prompt:
+  - "Use $root-cause-analysis"

package/plugins/lisa/skills/security-review/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "security-review"
+short_description: "Security review methodology. STRIDE threat modeling, OWASP Top 10 vulnerability checks, auth/validation/secrets handling review, and mitigation recommendations."
+default_prompt:
+  - "Use $security-review"

package/plugins/lisa/skills/security-zap-scan/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "security-zap-scan"
+short_description: "Run an OWASP ZAP baseline security scan locally using Docker. Checks for the ZAP baseline script, executes the scan, and summarizes findings by risk level with remediation recommendations."
+default_prompt:
+  - "Use $security-zap-scan"

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

@@ -0,0 +1,4 @@
+display_name: "setup-atlassian"
+short_description: "Configure Atlassian access for this project. Installs acli if missing, runs the OAuth or API-token login, optionally enables the Atlassian MCP, resolves the cloudId for the active site, and writes the `atlassian` section into `.lisa.config.json`. Prerequisite for /lisa:setup:jira and /lisa:setup:confluence (both need atlassian.cloudId). Idempotent — re-running updates the existing section rather than duplicating it."
+default_prompt:
+  - "Use $setup-atlassian"

package/plugins/lisa/skills/setup-confluence/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "setup-confluence"
+short_description: "Configure Confluence as the PRD source for this project. Writes `confluence.spaceKey` and/or `confluence.parentPageId` into `.lisa.config.json` and offers to set top-level `source: \\\"confluence\\\"`. Depends on /lisa:setup:atlassian — atlassian.cloudId must already be present. Idempotent."
+default_prompt:
+  - "Use $setup-confluence"

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

@@ -0,0 +1,4 @@
+display_name: "setup-github"
+short_description: "Configure GitHub Issues as the destination tracker and/or the PRD source for this project. Verifies the gh CLI is installed and authenticated, resolves `org/repo`, scaffolds the build-queue label namespace (`status:*`) when GitHub is the tracker and/or the PRD-lifecycle label namespace (`prd-*` + sentinel) when GitHub is the PRD source, writes the `github` section into `.lisa.config.json`, and offers to set top-level `tracker: \\\"github\\\"` and/or `source: \\\"github\\\"`. Idempotent — re-running updates the existing section and reuses existing labels rather than duplicating. No /lisa:setup:atlassian prerequisite (GitHub auth is standalone)."
+default_prompt:
+  - "Use $setup-github"

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

@@ -0,0 +1,4 @@
+display_name: "setup-jira"
+short_description: "Configure JIRA as the destination tracker for this project. Writes `jira.project` into `.lisa.config.json` and offers to set top-level `tracker: \\\"jira\\\"`. Depends on /lisa:setup:atlassian — atlassian.cloudId must already be present, otherwise this skill stops and instructs the user to run setup-atlassian first. Idempotent."
+default_prompt:
+  - "Use $setup-jira"

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

@@ -0,0 +1,4 @@
+display_name: "setup-linear"
+short_description: "Configure Linear as the destination tracker and/or the PRD source for this project. Verifies Linear access (MCP OAuth or a personal API key in OS keychain), resolves the workspace slug and team key, scaffolds the build-queue issue-label namespace (`status:*`) when Linear is the tracker and/or the PRD-lifecycle project-label namespace (`prd-*` + issue-level sentinel) when Linear is the PRD source, writes the `linear` section into `.lisa.config.json`, and offers to set top-level `tracker: \\\"linear\\\"` and/or `source: \\\"linear\\\"`. Idempotent — re-running updates the existing section and reuses existing labels. No /lisa:setup:atlassian prerequisite."
+default_prompt:
+  - "Use $setup-linear"

package/plugins/lisa/skills/setup-notion/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "setup-notion"
+short_description: "Configure Notion as the PRD source for this project. Walks the user through creating an internal integration in the target workspace, sharing the PRD database with it, stores the resulting `ntn_*` token in OS keychain (multi-workspace-safe — keyed by workspaceId), validates against the Notion API, and writes `notion.workspaceId`, `notion.prdDatabaseId`, and `notion.values` into `.lisa.config.json`. Idempotent — re-runs update the existing section rather than duplicating it. Offers to set top-level `source: \\\"notion\\\"`."
+default_prompt:
+  - "Use $setup-notion"