@codyswann/lisa 4.72.0 → 4.72.2

package/plugins/lisa/.codex-plugin/skills/lisa-intake/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-intake
 description: "Vendor-agnostic scanner for…"
 allowed-tools: ["Skill", "Bash"]
 ---
+Vendor-agnostic scanner for Ready queues. Notion PRD database URL → first Ready PRD → lisa-plan. Confluence space or parent page URL → first prd-ready PRD → lisa-plan. Linear workspace URL or team key → first prd-ready project → lisa-plan. GitHub repo URL or `org/repo` token → first prd-ready issue → lisa-plan, or first `status:ready` issue → lisa-implement when `tracker = github`. JIRA project key or JQL filter → first Ready ticket → lisa-implement. On the PRD side it also closes the loop: each cycle rolls a ticketed PRD up to shipped and dispatches lisa-verify-prd for one shipped PRD (shipped → verified on pass; on fail, re-opened shipped → ticketed with build-ready fix tickets that auto-build and re-verify — never blocked). Designed as the cron target for /schedule — one eligible item per invocation, exits cleanly on empty. Symmetric counterpart to the single-item lisa-plan and lisa-implement skills.
+
 
 # Intake: $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-intake-explain/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-intake-explain
 description: "Read-only operator surface for…"
 allowed-tools: ["Skill", "Bash", "Read"]
 ---
+Read-only operator surface for diagnosing one repo-scoped PRD or build item against Lisa's current intake and repair contracts. Resolves the item's queue family, lifecycle role, ownership boundary, and gate outcomes using the same source/tracker detection, lifecycle naming, leaf-only, dependency, staleness, and backoff semantics the write-side intake and repair flows already enforce.
+
 
 # Intake Explain: $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-jam-access/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-jam-access
 description: "Vendor-neutral access layer for…"
 allowed-tools: ["Bash", "Read", "Skill"]
 ---
+Vendor-neutral access layer for Jam. Jam triage rules and skills MUST delegate through this skill rather than calling Jam MCP tools directly. Per the credential-substrate-precedence contract, resolves the JAM_PAT-authenticated Jam CLI first when the PAT is present and identity-matched, then falls back to the Jam MCP.
+
 
 # Jam Access: $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-jira-add-journey/SKILL.md

@@ -2,6 +2,8 @@
 name: lisa-jira-add-journey
 description: "Add a Validation Journey…"
 ---
+Add a Validation Journey section to an existing JIRA ticket by analyzing the change type and generating appropriate verification steps with evidence markers.
+
 
 # Add Validation Journey to Existing JIRA Ticket
 

package/plugins/lisa/.codex-plugin/skills/lisa-jira-build-intake/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-jira-build-intake
 description: "Symmetric counterpart to…"
 allowed-tools: ["Skill", "Bash"]
 ---
+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 the first eligible ticket by transitioning to the configured `claimed` status, runs the implementation/build flow via the jira-agent workflow in-session (culminating in lisa-implement), transitions to the configured `done` status on completion, then exits. Enforces the claim-time arm of the `leaf-only-lifecycle` rule: a parent/container with open child work (or a childless Epic) 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.
+
 
 # JIRA Build Intake: $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-jira-claim/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-jira-claim
 description: "Idempotently claims one live…"
 allowed-tools: ["Bash", "Skill", "Read"]
 ---
+Idempotently claims one live Jira leaf ticket for direct Lisa work. Reuses jira-build-intake Phase 3b semantics through lisa-atlassian-access: configured ready-to-claimed transition, assign-only-if-unassigned, stable managed comment, and post-write verification.
+
 
 # Claim Jira Ticket: $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-jira-create/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-jira-create
 description: "creating JIRA epics, stories…"
 allowed-tools: ["Read", "Glob", "LS", "Skill"]
 ---
+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.
+
 
 # Create JIRA Issues from $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-jira-evidence/SKILL.md

@@ -2,6 +2,8 @@
 name: lisa-jira-evidence
 description: "Upload text evidence to GitHub…"
 ---
+Upload text evidence to GitHub pr-assets release, update PR description, post JIRA comment with code blocks, and move ticket to the configured review status only when `jira.workflow.review` is set (otherwise leave it in `claimed`). Reusable by any skill that captures evidence and generates evidence/comment.txt + evidence/comment.md.
+
 
 # JIRA Evidence Posting
 

package/plugins/lisa/.codex-plugin/skills/lisa-jira-journey/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-jira-journey
 description: "Parse a JIRA ticket's…"
 allowed-tools: ["Bash", "Read", "Glob", "Grep", "Skill"]
 ---
+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.
+
 
 # JIRA Validation Journey (TypeScript)
 

package/plugins/lisa/.codex-plugin/skills/lisa-jira-read-ticket/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-jira-read-ticket
 description: "Fetches the full scope of a…"
 allowed-tools: ["Bash", "Skill"]
 ---
+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.
+
 
 # Read JIRA Ticket: $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-jira-sync/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-jira-sync
 description: "Syncs plan progress to a linked…"
 allowed-tools: ["Skill", "Bash", "Read", "Glob", "Grep"]
 ---
+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.
+
 
 # JIRA Ticket Sync
 

package/plugins/lisa/.codex-plugin/skills/lisa-jira-validate-ticket/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-jira-validate-ticket
 description: "Validates a proposed JIRA…"
 allowed-tools: ["Bash", "Skill"]
 ---
+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.
+
 
 # Validate JIRA Ticket: $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-jira-verify/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-jira-verify
 description: "verifying that a JIRA ticket…"
 allowed-tools: ["Skill"]
 ---
+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.
+
 
 # Verify JIRA Ticket: $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-jira-write-ticket/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-jira-write-ticket
 description: "Creates or updates a JIRA…"
 allowed-tools: ["Bash", "Skill"]
 ---
+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.
+
 
 # Write JIRA Ticket: $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-jsdoc-best-practices/SKILL.md

@@ -2,6 +2,8 @@
 name: lisa-jsdoc-best-practices
 description: "Enforces JSDoc documentation…"
 ---
+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.
+
 
 # JSDoc Best Practices
 

package/plugins/lisa/.codex-plugin/skills/lisa-kane-browser/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-kane-browser
 description: "Optional Lisa-owned adapter for…"
 allowed-tools: ["Bash", "Read", "Glob", "Grep", "Skill"]
 ---
+Optional Lisa-owned adapter for TestMu Kane CLI empirical browser runs. Enforces project opt-in, cloud-upload approval, non-production environment allow-lists, full-mutation rollout policy, pinned-version readiness, normalized outcomes, and durable Lisa evidence handling. Never replaces project-native Playwright, Cypress, or Maestro regression tests.
+
 
 # Kane empirical browser provider
 

package/plugins/lisa/.codex-plugin/skills/lisa-learnings-audit/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-learnings-audit
 description: "The gardener of the learnings…"
 allowed-tools: ["Skill", "Bash", "Read", "Glob", "Grep"]
 ---
+The gardener of the learnings ladder (PRD #1729). Periodically audits every knowledge surface — ledger, rules trees (including Lisa's own shipped eager rules), skills, wiki index, and mechanical-control surfaces — gathers evidence per item (recurrence, staleness, redundancy, contradiction, budget pressure), classifies each candidate through the ladder router (skill-evaluator, advisory), and communicates exclusively through the tracker: one evidence-bearing ticket per PROMOTE/DEMOTE, one batch ticket per run for CONFIRM/RETIRE, upstream Lisa issues for upstream-scoped patterns. Everything is human-gated at v1 — the skill only files tickets; humans gate by flipping status:ready or closing as rejected, and rejections are remembered. Cron-able via lisa-setup-automations and runnable on demand via /lisa:learnings:audit.
+
 
 # Learnings Audit (the gardener): $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-linear-access/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-linear-access
 description: "Vendor-neutral access layer for…"
 allowed-tools: ["Bash", "Read", "Skill"]
 ---
+Vendor-neutral access layer for Linear. Linear skills MUST delegate through this skill rather than calling Linear MCP tools or Linear GraphQL directly. Per the credential-substrate-precedence contract, resolves LINEAR_API_KEY + Linear GraphQL first — ahead of the Linear MCP — whenever the key is present and identity-matches the configured workspace/team, and falls back to the Linear MCP when the token path is unavailable. Identity-match is mandatory on both substrates.
+
 
 # Linear Access: $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-linear-add-journey/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-linear-add-journey
 description: "Add a Validation Journey…"
 allowed-tools: ["Bash", "Read", "Glob", "Grep", "Skill"]
 ---
+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.
+
 
 # Add Validation Journey to Existing Linear Issue
 

package/plugins/lisa/.codex-plugin/skills/lisa-linear-build-intake/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-linear-build-intake
 description: "Symmetric counterpart to…"
 allowed-tools: ["Skill", "Bash"]
 ---
+Symmetric counterpart to lisa-jira-build-intake on the Linear side. Scans a Linear team for Issues in the configured `ready` workflow state, claims the first eligible Issue by transitioning it to the configured `claimed` state, runs the implementation/build flow via the linear-agent workflow in-session (culminating in lisa-implement), transitions to the configured `done` state on completion, then exits. Enforces the claim-time arm of the `leaf-only-lifecycle` rule: a parent/container with open child work (or a childless Epic) that still sits in the build-ready state is skipped or safe-blocked with a lifecycle-repair comment, never claimed. The `ready` state 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.
+
 
 # Linear Build Intake: $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-linear-claim/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-linear-claim
 description: "Idempotently claims one live…"
 allowed-tools: ["Bash", "Skill", "Read"]
 ---
+Idempotently claims one live Linear leaf issue for direct Lisa work. Reuses linear-build-intake Phase 3b semantics through lisa-linear-access: configured ready-to-claimed state transition, assign-only-if-unassigned, stable managed comment, and post-write verification.
+
 
 # Claim Linear Issue: $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-linear-create/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-linear-create
 description: "Creates Linear Projects…"
 allowed-tools: ["Read", "Glob", "LS", "Skill"]
 ---
+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.
+
 
 # Create Linear Work Items from $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-linear-evidence/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-linear-evidence
 description: "Uploads text evidence to the…"
 allowed-tools: ["Bash", "Skill"]
 ---
+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` workflow state to the configured `review` workflow state. 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.
+
 
 # Linear Evidence: $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-linear-journey/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-linear-journey
 description: "Parse a Linear Issue's…"
 allowed-tools: ["Bash", "Read", "Glob", "Grep", "Skill"]
 ---
+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 typed [EVIDENCE: <artifact-type>: <name>] marker, and post to Linear + GitHub PR using the linear-evidence skill. Linear counterpart of lisa-jira-journey.
+
 
 # Linear Validation Journey
 

package/plugins/lisa/.codex-plugin/skills/lisa-linear-prd-intake/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-linear-prd-intake
 description: "Scans a Linear workspace (or a…"
 allowed-tools: ["Skill", "Bash"]
 ---
+Scans a Linear workspace (or a specific team) for projects carrying the configured `ready` PRD label and runs the first eligible one through the dry-run validation pipeline. A project that passes every gate gets tickets written and the label flipped to the configured `ticketed` label; a project that fails gets clarifying-question comments (on the project itself, and on the relevant sub-issue where the failure anchors to one) 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).
+
 
 # Linear PRD Intake: $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-linear-read-issue/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-linear-read-issue
 description: "Fetches the full scope of a…"
 allowed-tools: ["Bash", "Skill"]
 ---
+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.
+
 
 # Read Linear Work Item: $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-linear-sync/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-linear-sync
 description: "Syncs plan progress to a linked…"
 allowed-tools: ["Bash", "Skill"]
 ---
+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.
+
 
 # Sync Plan to Linear: $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-linear-to-tracker/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-linear-to-tracker
 description: "Break down a Linear PRD (a…"
 allowed-tools: ["Skill", "Bash"]
 ---
+Break down a Linear PRD (a Linear Project) into Epics, Stories, and Sub-tasks in the configured destination tracker (JIRA, GitHub Issues, or Linear per .lisa.config.json). Use this skill whenever the user shares a Linear project URL and wants it converted into tracker tickets, or asks to "break down this Linear project", "create tickets from a Linear project", "turn this Linear PRD into tickets", or similar. This skill mirrors `lisa-notion-to-tracker` and `lisa-confluence-to-tracker` for projects whose PRDs live in Linear — the workflow, gates, dry-run mode, and validation rules are identical; only the source-of-truth tool surface differs (Linear MCP instead of Notion / Confluence MCP).
+
 
 # Linear PRD to Tracker Breakdown
 

package/plugins/lisa/.codex-plugin/skills/lisa-linear-validate-issue/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-linear-validate-issue
 description: "Validates a proposed Linear…"
 allowed-tools: ["Skill", "Bash"]
 ---
+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.
+
 
 # Validate Linear Work Item: $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-linear-verify/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-linear-verify
 description: "Verifies a Linear work item…"
 allowed-tools: ["Bash", "Skill"]
 ---
+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.
+
 
 # Verify Linear Work Item: $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-linear-write-issue/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-linear-write-issue
 description: "Creates or updates a Linear…"
 allowed-tools: ["Bash", "Skill"]
 ---
+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.
+
 
 # Write Linear Work Item: $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-linear-write-prd/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-linear-write-prd
 description: "Creates or idempotently updates…"
 allowed-tools: ["Skill", "Bash"]
 ---
+Creates or idempotently updates a PRD as a Linear Project carrying exactly one PRD lifecycle project-label (`prd-draft` by default, or `prd-ready` when initial_role is ready so lisa-linear-prd-intake auto-claims it). The Linear PRD-source writer behind lisa-prd-source-write. Dedupes by a stable marker embedded in the Project description (matched by marker, never by name). Uses the Linear MCP.
+
 
 # Write Linear PRD: $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-monitor/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-monitor
 description: "Monitor application health AND…"
 allowed-tools: ["Skill", "Bash", "Read", "Grep", "Glob"]
 ---
+Monitor application health AND audit observability completeness for the current repo, then file build-ready tickets for what it finds. Checks health endpoints, recent logs (CloudWatch / Sentry / browser console), error-rate spikes, performance hotspots, pending migrations, and Playwright smoke flows via the stack-specific ops-specialist (Expo, Rails) or stack-agnostic base probing (any stack, incl. NestJS / CDK). Audits the repo against an observability-completeness rubric scoped to its type (frontend / backend / infra) and flags instrumentation gaps (e.g. no distributed tracing, no DB/query analytics). For each high-signal anomaly and each in-scope missing dimension it files a single-repo, build-ready leaf ticket via tracker-write (idempotent, capped, repo-scoped) so the intake cron implements it — monitor files only, it never fixes. Manual (no cron); files by default, `--dry-run` previews. Conservative by default. Also invoked as the post-deploy step of lisa-verify, where it runs report-only (never files).
+
 
 # Monitor: $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-nightly-add-test-coverage/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-nightly-add-test-coverage
 description: "Nightly direct-execution skill…"
 allowed-tools: ["Edit", "MultiEdit", "Write", "Read", "Glob", "Grep", "Bash"]
 ---
+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.
+
 
 # Nightly Test Coverage Improvement
 

package/plugins/lisa/.codex-plugin/skills/lisa-nightly-improve-tests/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-nightly-improve-tests
 description: "Nightly direct-execution skill…"
 allowed-tools: ["Edit", "MultiEdit", "Write", "Read", "Glob", "Grep", "Bash"]
 ---
+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.
+
 
 # Nightly Test Quality Improvement
 

package/plugins/lisa/.codex-plugin/skills/lisa-nightly-lower-code-complexity/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-nightly-lower-code-complexity
 description: "Nightly direct-execution skill…"
 allowed-tools: ["Edit", "MultiEdit", "Write", "Read", "Glob", "Grep", "Bash"]
 ---
+Nightly direct-execution skill for reducing code complexity thresholds. Receives pre-computed threshold data, refactors violations, updates thresholds, commits, and creates a PR.
+
 
 # Nightly Code Complexity Reduction
 

package/plugins/lisa/.codex-plugin/skills/lisa-notion-access/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-notion-access
 description: "Vendor-neutral access layer for…"
 allowed-tools: ["Bash", "Read", "Skill"]
 ---
+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. Per the credential-substrate-precedence contract, resolves a substrate per operation in this order: (1) curl + Bearer auth + internal-integration token when the token is present and identity-matches the configured workspace, (2) Notion MCP as fallback if authenticated and the configured prdDatabaseId is fetchable through it. Verifies the active connection matches `.lisa.config.json` before every operation — substrates authenticated as a different Notion workspace are skipped, not used.
+
 
 # Notion Access: $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-notion-prd-intake/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-notion-prd-intake
 description: "Scans a Notion PRD database for…"
 allowed-tools: ["Skill", "Bash", "Read", "Write", "Edit", "AskUserQuestion"]
 ---
+Scans a Notion PRD database for pages in the configured `ready` status and runs the first eligible one through the dry-run validation pipeline. A PRD that passes every gate gets tickets written and the status flipped to the configured `ticketed` value; a PRD that fails gets 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.
+
 
 # Notion PRD Intake: $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-notion-to-tracker/SKILL.md

@@ -2,6 +2,8 @@
 name: lisa-notion-to-tracker
 description: "Break down a Notion PRD into…"
 ---
+Break down a Notion PRD into Epics, Stories, and Sub-tasks in the configured destination tracker (JIRA, GitHub Issues, or Linear per .lisa.config.json). Use this skill whenever the user shares a Notion PRD URL and wants it converted into tracker tickets, or asks to "break down a PRD", "create tickets from a PRD", "turn this PRD into tickets", or similar. Also trigger when the user mentions creating epics/stories/tasks from a Notion document. This skill handles the full pipeline: fetching the PRD, analyzing comments, researching the codebase, identifying blockers, and creating all tickets with empirical verification plans.
+
 
 # Notion PRD to Tracker Breakdown
 

package/plugins/lisa/.codex-plugin/skills/lisa-notion-write-prd/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-notion-write-prd
 description: "Creates or idempotently updates…"
 allowed-tools: ["Skill", "Bash"]
 ---
+Creates or idempotently updates a PRD as a page in the configured Notion PRD database, setting the lifecycle Status property to the draft value by default (or the ready value when initial_role is ready so lisa-notion-prd-intake auto-claims it). The Notion PRD-source writer behind lisa-prd-source-write. Dedupes by a stable marker embedded in the page (matched by marker, never by title). All Notion access goes through lisa-notion-access — never call the Notion API or MCP directly.
+
 
 # Write Notion PRD: $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-parity-code-review/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-parity-code-review
 description: "Lisa-native code review of the…"
 allowed-tools: ["Read", "Bash", "Grep", "Glob"]
 ---
+Lisa-native code review of the current git diff. Walks every changed hunk and reports correctness bugs, security issues, and obvious defects as severity-ranked findings with file:line references. Vendor-neutral — the cross-agent equivalent of the upstream code-review command, runnable on Codex, agy, Copilot, Cursor, and Claude.
+
 
 # Parity Code Review
 

package/plugins/lisa/.codex-plugin/skills/lisa-parity-code-simplifier/SKILL.md

@@ -1,9 +1,11 @@
 ---
 name: lisa-parity-code-simplifier
-description: "Lisa-native, behavior-preserving…"
+description: "Lisa-native…"
 allowed-tools: ["Read", "Bash", "Grep", "Glob", "Edit", "Write"]
 synced-from: code-simplifier@claude-plugins-official@1.0.0
 ---
+Lisa-native, behavior-preserving simplification of recently-changed code. Removes duplication and dead code, reuses existing utilities, and improves readability without altering behavior — quality only, never a bug hunt. Vendor-neutral cross-agent equivalent of the upstream code-simplifier agent, runnable on Codex, agy, Copilot, Cursor, and Claude.
+
 
 # Parity Code Simplifier
 

package/plugins/lisa/.codex-plugin/skills/lisa-parity-code-simplifier/agents/openai.yaml

@@ -1,4 +1,4 @@
 display_name: "Parity Code Simplifier"
-short_description: "Lisa-native, behavior-preserving…"
+short_description: "Lisa-native…"
 default_prompt:
-  - "Use $lisa-parity-code-simplifier: Lisa-native, behavior-preserving…."
+  - "Use $lisa-parity-code-simplifier: Lisa-native…."

package/plugins/lisa/.codex-plugin/skills/lisa-parity-coderabbit/SKILL.md

@@ -4,6 +4,8 @@ description: "Thorough PR-style review of the…"
 allowed-tools: ["Read", "Bash", "Grep", "Glob"]
 synced-from: coderabbit@claude-plugins-official@1.1.1
 ---
+Thorough PR-style review of the full diff — bugs, security, performance, and maintainability — with concrete suggested fixes and a structured summary. An independent Lisa-native review skill that does NOT call CodeRabbit's service or port its code. Vendor-neutral cross-agent equivalent of the upstream coderabbit plugin, runnable on Codex, agy, Copilot, Cursor, and Claude.
+
 
 # Parity CodeRabbit
 

package/plugins/lisa/.codex-plugin/skills/lisa-parity-sentry-sdk-setup/SKILL.md

@@ -4,6 +4,8 @@ description: "Install and configure the…"
 allowed-tools: ["Read", "Edit", "Write", "Bash"]
 synced-from: sentry@claude-plugins-official@1.4.0
 ---
+Install and configure the Sentry SDK for a project — detect the framework/runtime, add the correct @sentry/<framework> package, initialize the client, wire the DSN through env, enable error + performance monitoring, and set up source map upload for readable stack traces. One consolidated skill covering react, nextjs, node, nestjs, express, python, django, react-native, and more. Lisa-native reimplementation of Sentry's SDK-setup suite. Use when adding Sentry to a project or fixing an existing Sentry install.
+
 
 # Sentry SDK Setup
 

package/plugins/lisa/.codex-plugin/skills/lisa-parity-sentry-seer/SKILL.md

@@ -4,6 +4,8 @@ description: "AI debugging — given an error…"
 allowed-tools: ["Read", "Grep", "Glob", "Bash", "Edit"]
 synced-from: sentry@claude-plugins-official@1.4.0
 ---
+AI debugging — given an error message, stack trace, or failing test, analyze the signal, form ranked hypotheses, locate the root cause in the codebase with file:line evidence, and propose a minimal fix. Lisa-native reimplementation of Sentry's seer workflow, available across all agent runtimes. Use when handed an exception, crash, regression, or red test and asked to find and fix the cause.
+
 
 # Seer — AI Root-Cause Debugging
 

package/plugins/lisa/.codex-plugin/skills/lisa-parity-skill-creator/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-parity-skill-creator
 description: "Author a new Lisa skill…"
 allowed-tools: ["Read", "Edit", "Write", "Bash"]
 ---
+Author a new Lisa skill end-to-end — scaffold the SKILL.md frontmatter (name/description/allowed-tools), write the pass-through command, follow hyphen naming, place files under plugins/src/base, and rebuild plugins. Lisa-native reimplementation of the upstream skill-creator plugin. NO drift pin: upstream publishes no semver, so it is not drift-trackable.
+
 
 # Skill Creator
 

package/plugins/lisa/.codex-plugin/skills/lisa-performance-review/SKILL.md

@@ -2,6 +2,8 @@
 name: lisa-performance-review
 description: "Performance review methodology"
 ---
+Performance review methodology. N+1 queries, inefficient algorithms, memory leaks, missing indexes, unnecessary re-renders, bundle size issues. Evidence-based recommendations.
+
 
 # Performance Review
 

package/plugins/lisa/.codex-plugin/skills/lisa-persist-learning/SKILL.md

@@ -2,6 +2,8 @@
 name: lisa-persist-learning
 description: "a candidate learning (from a…"
 ---
+This skill should be used when a candidate learning (from a failure signal, rejection, or debrief) needs to be judged and routed. It computes a stable fingerprint, runs the candidate through the hostile-default learning-judge gate, and performs exactly the verdict's side effects — a dropped-with-reason note on the triggering issue (drop), an automatically filed upstream Lisa ticket with marker dedupe, evidence, and a per-run cap (lisa-upstream), or a confidence-routed pull request that touches only the learnings surface (durable-learning). Idempotent via marker dedupe; headless-safe; never blocks the primary build flow.
+
 
 # Persist Learning
 

package/plugins/lisa/.codex-plugin/skills/lisa-plan/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-plan
 description: "Decompose a single PRD or…"
 allowed-tools: ["Skill", "Bash", "Read", "Glob", "Grep"]
 ---
+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.
+
 
 # Plan: $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-plugin-sync-explain/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-plugin-sync-explain
 description: "Read-only diagnostic for Lisa…"
 allowed-tools: ["Bash", "Read"]
 ---
+Read-only diagnostic for Lisa plugin source/generated drift. Compares plugins/src against generated plugins/lisa* status, reports source-not-built, generated-only, and marketplace registration drift, and preserves the working tree.
+
 
 # Plugin Sync Explain: $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-posthog-access/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-posthog-access
 description: "Vendor-neutral access layer for…"
 allowed-tools: ["Bash", "Read", "Skill"]
 ---
+Vendor-neutral access layer for PostHog. PostHog skills and observability rules MUST delegate through this skill rather than calling PostHog MCP tools or REST directly. Per the credential-substrate-precedence contract, resolves POSTHOG_PERSONAL_API_KEY bearer auth first when present and identity-matched to the configured project, then falls back to the PostHog MCP.
+
 
 # PostHog Access: $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-prd-backlink/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-prd-backlink
 description: "Update a source PRD with an…"
 allowed-tools: ["Skill", "Bash", "Read", "Edit", "Write", "Glob", "Grep"]
 ---
+Update a source PRD with an always-written, machine-readable `## Tickets` (alias `## Generated Work`) section linking back to every work item created from it. Each entry carries a parseable ref + URL + type + parent token so the generated child set is readable without scraping prose. Vendor-aware on the source side (Notion / Confluence / Linear / GitHub Issue / file) and tracker-agnostic on the ticket side; the documented section is written for every vendor, additive to native hierarchy linking. 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.
+
 
 # PRD Back-link
 

package/plugins/lisa/.codex-plugin/skills/lisa-prd-source-write/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-prd-source-write
 description: "Vendor-neutral wrapper for…"
 allowed-tools: ["Skill", "Bash", "Read"]
 ---
+Vendor-neutral wrapper for creating (or idempotently updating) a PRD in the configured PRD source. The PRD-side sibling of lisa-tracker-write. Resolves `source` from .lisa.config.local.json first (then .lisa.config.json — local overrides global) and dispatches to lisa-notion-write-prd, lisa-confluence-write-prd, lisa-github-write-prd, or lisa-linear-write-prd. Callers (notably lisa-research) MUST invoke this skill instead of a vendor PRD writer directly — that is what makes the PRD source switchable per project. Accepts an `initial_role` of `draft` (default) or `ready` so a freshly created PRD either waits for human promotion or is immediately picked up by lisa-intake; and a stable dedupe marker so re-runs reference the existing PRD instead of creating a duplicate. The PRD lives in the source — there is no separate document artifact.
+
 
 # PRD Source Write: $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-prd-ticket-coverage/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-prd-ticket-coverage
 description: "Verifies that every requirement…"
 allowed-tools: ["Skill", "Bash"]
 ---
+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.
+
 
 # PRD Ticket Coverage Audit: $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-product-walkthrough/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-product-walkthrough
 description: "Methodology for evaluating the…"
 allowed-tools: ["Skill", "Bash", "Read", "mcp__plugin_playwright_playwright__browser_navigate", "mcp__plugin_playwright_playwright__browser_snapshot", "mcp__plugin_playwright_playwright__browser_take_screenshot", "mcp__plugin_playwright_playwright__browser_click", "mcp__plugin_playwright_playwright__browser_type", "mcp__plugin_playwright_playwright__browser_select_option", "mcp__plugin_playwright_playwright__browser_fill_form", "mcp__plugin_playwright_playwright__browser_press_key", "mcp__plugin_playwright_playwright__browser_hover", "mcp__plugin_playwright_playwright__browser_navigate_back", "mcp__plugin_playwright_playwright__browser_resize", "mcp__plugin_playwright_playwright__browser_tabs", "mcp__plugin_playwright_playwright__browser_console_messages", "mcp__plugin_playwright_playwright__browser_network_requests", "mcp__plugin_playwright_playwright__browser_wait_for", "mcp__plugin_playwright_playwright__browser_close"]
 ---
+Methodology for evaluating the live product 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. Driving the product is owned by the `use-the-product` core (which detects the product type — DOM web, HTTP/API, canvas game, CLI, IaC — resolves the per-environment mutation policy from .lisa.config.json so production is never mutated by accident, and explores through the project's personas when defined); this skill adds the planning lens. Invoke from notion-to-tracker (Phase 2b live-product walkthrough), jira-create, and any PRD intake flow whose work touches existing user-facing surfaces.
+
 
 # Live Product Walkthrough
 

package/plugins/lisa/.codex-plugin/skills/lisa-project-ideation/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-project-ideation
 description: "Generate practical, verifiable…"
 allowed-tools: ["Skill", "Bash", "Read", "Glob", "Grep", "WebFetch", "WebSearch"]
 ---
+Generate practical, verifiable product ideas for the current host project FROM EVIDENCE-DERIVED PERSONAS, then turn the selected build-ready ideas into real PRDs via lisa-research. First derives the personas the project actually serves by mining its docs, code, data model, and releases (never invented — each persona cites its evidence), then ideates per persona. Every build-ready idea must pass a practicality gate (an obtainable data/source path) and an empirical verification gate (a user-observable outcome the agent can verify). Selected ideas are handed to lisa-research, which creates each PRD in the configured source (Notion / Confluence / GitHub / Linear) — in the draft state by default, or prd-ready (auto-picked-up by lisa-intake) when prd_ready=true. Defaults to creating one PRD (the top-ranked idea); max_prds widens the batch. Invoke for 'generate feature ideas for this project', 'what should we build next for <persona>?', 'looking at <external product>, what should we add here?'.
+
 
 # Project Ideation