@codyswann/lisa 2.53.0 → 2.54.0

package/package.json

@@ -82,7 +82,7 @@
     "lodash": ">=4.18.1"
   },
   "name": "@codyswann/lisa",
-  "version": "2.53.0",
+  "version": "2.54.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.53.0",
+  "version": "2.54.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.53.0",
+  "version": "2.54.0",
   "description": "Universal governance: agents, skills, commands, hooks, and rules for all projects.",
   "author": {
     "name": "Cody Swann"

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

@@ -116,3 +116,12 @@ When the user wants to act on an idea, preserve its feasibility and verification
 - Turn a PRD into tickets → `/lisa:plan`
 - Build a ticket end-to-end → `/lisa:implement`
 - Lock in the verification so it never regresses → `/lisa:codify-verification`
+
+## Example outputs
+
+Use the markdown examples in `examples/` as shape references when composing reports:
+
+- `host-project-only.md` shows ideas grounded only in the current repository.
+- `public-external-inspiration.md` shows how public, no-login external sources can inspire ideas without becoming hidden requirements.
+- `unavailable-data-rejection.md` shows how to name missing private, paid, or unavailable data sources when demoting ideas.
+- `evidence-card-format.md` shows the required evidence fields every Practical Idea card must carry.

package/plugins/lisa/skills/project-ideation/examples/evidence-card-format.md

@@ -0,0 +1,21 @@
+# Evidence Card Formatting Example Output
+
+## What Already Exists
+- Lisa work items already use Validation Journey evidence markers.
+- Skill reports can be saved as markdown artifacts and reviewed by humans.
+
+## Practical Ideas
+### 1. Evidence-First Idea Cards
+- User value: A reviewer can decide whether an idea is ready without asking how it will be proven.
+- Existing fit: Uses the project-ideation report shape and Lisa's evidence-first verification rules.
+- Data/source path: Existing local project files plus any public URLs cited in the report.
+- Practical slice: Require each practical idea to include `Empirical verification` and `Evidence` lines before it can remain in the practical list.
+- Empirical verification: Render this example and confirm every practical idea card includes the two evidence fields.
+- Evidence: Text output showing all practical cards pass the field check.
+- Confidence: high because the check is structural and does not require external services.
+
+## Discovery Spikes
+- Evidence attachments inside generated reports: needs a storage and retention decision for binary artifacts.
+
+## Rejected / Not Practical Yet
+- Treating lint, typecheck, or unit tests as the only proof for a user-facing idea: rejected because quality gates are prerequisites, not empirical evidence artifacts.

package/plugins/lisa/skills/project-ideation/examples/host-project-only.md

@@ -0,0 +1,22 @@
+# Host Project Only Example Output
+
+## What Already Exists
+- CLI command registration is documented in the repository README.
+- Skill sources live under `plugins/src/base/skills/` and are copied into the generated Lisa plugin.
+- The project already has unit tests that verify generated plugin artifacts.
+
+## Practical Ideas
+### 1. Plugin Surface Drift Report
+- User value: Maintainers can see which source skills are not represented in the generated plugin before publishing.
+- Existing fit: Builds on the existing plugin source tree and generated plugin artifact tests.
+- Data/source path: Local files under `plugins/src/base/skills/` and `plugins/lisa/skills/`.
+- Practical slice: Emit a markdown report listing source-only, generated-only, and mismatched skill directories.
+- Empirical verification: Run the report command in a clean checkout after intentionally adding one fixture-only source skill.
+- Evidence: CLI output showing the mismatched skill and the generated markdown report path.
+- Confidence: high because the required data is already local and deterministic.
+
+## Discovery Spikes
+- Skill usage frequency ranking: needs a bounded source of invocation telemetry before it can be recommended.
+
+## Rejected / Not Practical Yet
+- Personalized skill suggestions from private user history: rejected because the repository does not have access to private Codex usage history.

package/plugins/lisa/skills/project-ideation/examples/public-external-inspiration.md

@@ -0,0 +1,22 @@
+# Public External Inspiration Example Output
+
+## What Already Exists
+- The host project already has a command catalog and source-authored skill files.
+- The host project can inspect public documentation pages without sign-in.
+- Existing verification can run through CLI commands and generated markdown artifacts.
+
+## Practical Ideas
+### 1. Public Pattern Checklist Import
+- User value: Maintainers can compare their command guidance against public best-practice pages without copying private or paid content.
+- Existing fit: Builds on the current docs and skill authoring workflow.
+- Data/source path: A public, no-login documentation URL supplied by the user, plus local `README.md` and skill files.
+- Practical slice: Generate a checklist of public patterns found in the external page and mark whether each is already represented locally.
+- Empirical verification: Run the ideation workflow against a fixed public URL and inspect the generated checklist.
+- Evidence: Generated markdown containing source URLs, matched local file paths, and unmatched public patterns.
+- Confidence: medium because public pages can change, but the source path is accessible and citeable.
+
+## Discovery Spikes
+- Automated freshness checks for public pages: needs a policy for when external pages may be re-fetched and cached.
+
+## Rejected / Not Practical Yet
+- Importing examples from a sign-in-only competitor workspace: rejected because the data source is not publicly obtainable.

package/plugins/lisa/skills/project-ideation/examples/unavailable-data-rejection.md

@@ -0,0 +1,22 @@
+# Unavailable Data Rejection Example Output
+
+## What Already Exists
+- The host project can read local source files, docs, scripts, and generated artifacts.
+- The host project does not expose customer analytics, private support tickets, or paid market datasets.
+
+## Practical Ideas
+### 1. Local Verification Gap Finder
+- User value: Maintainers can identify skills that describe empirical verification but do not name an evidence artifact.
+- Existing fit: Builds on local skill markdown files and existing unit tests.
+- Data/source path: Local `SKILL.md` files under the plugin source tree.
+- Practical slice: Scan skill files for verification sections and report entries that mention tests but no observable artifact.
+- Empirical verification: Run the scanner against a fixture skill with one missing evidence line.
+- Evidence: CLI output naming the fixture skill and the missing evidence field.
+- Confidence: high because the input is local and fully inspectable.
+
+## Discovery Spikes
+- Prioritize gaps by real-world usage: needs an obtainable telemetry source or a manually approved usage export before it can rank by frequency.
+
+## Rejected / Not Practical Yet
+- Recommend ideas from private customer support pain points: rejected because the missing source is a legitimate support-ticket export or configured support integration.
+- Recommend ideas from paid analyst reports: rejected because the missing source is a licensed data feed available to the agent at runtime.

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.53.0",
+  "version": "2.54.0",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.53.0",
+  "version": "2.54.0",
   "description": "AWS CDK-specific Lisa plugin.",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.53.0",
+  "version": "2.54.0",
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.53.0",
+  "version": "2.54.0",
   "description": "Expo and React Native-specific skills, agents, rules, and MCP servers.",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "2.53.0",
+  "version": "2.54.0",
   "description": "Harper/Fabric-specific rules for TypeScript component apps",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "2.53.0",
+  "version": "2.54.0",
   "description": "Harper/Fabric-specific Lisa rules for TypeScript component apps.",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "2.53.0",
+  "version": "2.54.0",
   "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "2.53.0",
+  "version": "2.54.0",
   "description": "NestJS-specific skills and migration write-protection hooks.",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "2.53.0",
+  "version": "2.54.0",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "2.53.0",
+  "version": "2.54.0",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, across Claude and Codex.",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "2.53.0",
+  "version": "2.54.0",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "2.53.0",
+  "version": "2.54.0",
   "description": "Ruby on Rails-specific skills and hooks for RuboCop and ast-grep scanning on edit.",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "2.53.0",
+  "version": "2.54.0",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "2.53.0",
+  "version": "2.54.0",
   "description": "TypeScript-specific hooks for formatting, linting, and ast-grep scanning on edit.",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.53.0",
+  "version": "2.54.0",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.53.0",
+  "version": "2.54.0",
   "description": "Distributable LLM Wiki kernel — ingest, query, lint, and maintain a git-native markdown knowledge base across Claude and Codex.",
   "author": {
     "name": "Cody Swann"

package/plugins/src/base/skills/project-ideation/SKILL.md

@@ -116,3 +116,12 @@ When the user wants to act on an idea, preserve its feasibility and verification
 - Turn a PRD into tickets → `/lisa:plan`
 - Build a ticket end-to-end → `/lisa:implement`
 - Lock in the verification so it never regresses → `/lisa:codify-verification`
+
+## Example outputs
+
+Use the markdown examples in `examples/` as shape references when composing reports:
+
+- `host-project-only.md` shows ideas grounded only in the current repository.
+- `public-external-inspiration.md` shows how public, no-login external sources can inspire ideas without becoming hidden requirements.
+- `unavailable-data-rejection.md` shows how to name missing private, paid, or unavailable data sources when demoting ideas.
+- `evidence-card-format.md` shows the required evidence fields every Practical Idea card must carry.

package/plugins/src/base/skills/project-ideation/examples/evidence-card-format.md

@@ -0,0 +1,21 @@
+# Evidence Card Formatting Example Output
+
+## What Already Exists
+- Lisa work items already use Validation Journey evidence markers.
+- Skill reports can be saved as markdown artifacts and reviewed by humans.
+
+## Practical Ideas
+### 1. Evidence-First Idea Cards
+- User value: A reviewer can decide whether an idea is ready without asking how it will be proven.
+- Existing fit: Uses the project-ideation report shape and Lisa's evidence-first verification rules.
+- Data/source path: Existing local project files plus any public URLs cited in the report.
+- Practical slice: Require each practical idea to include `Empirical verification` and `Evidence` lines before it can remain in the practical list.
+- Empirical verification: Render this example and confirm every practical idea card includes the two evidence fields.
+- Evidence: Text output showing all practical cards pass the field check.
+- Confidence: high because the check is structural and does not require external services.
+
+## Discovery Spikes
+- Evidence attachments inside generated reports: needs a storage and retention decision for binary artifacts.
+
+## Rejected / Not Practical Yet
+- Treating lint, typecheck, or unit tests as the only proof for a user-facing idea: rejected because quality gates are prerequisites, not empirical evidence artifacts.

package/plugins/src/base/skills/project-ideation/examples/host-project-only.md

@@ -0,0 +1,22 @@
+# Host Project Only Example Output
+
+## What Already Exists
+- CLI command registration is documented in the repository README.
+- Skill sources live under `plugins/src/base/skills/` and are copied into the generated Lisa plugin.
+- The project already has unit tests that verify generated plugin artifacts.
+
+## Practical Ideas
+### 1. Plugin Surface Drift Report
+- User value: Maintainers can see which source skills are not represented in the generated plugin before publishing.
+- Existing fit: Builds on the existing plugin source tree and generated plugin artifact tests.
+- Data/source path: Local files under `plugins/src/base/skills/` and `plugins/lisa/skills/`.
+- Practical slice: Emit a markdown report listing source-only, generated-only, and mismatched skill directories.
+- Empirical verification: Run the report command in a clean checkout after intentionally adding one fixture-only source skill.
+- Evidence: CLI output showing the mismatched skill and the generated markdown report path.
+- Confidence: high because the required data is already local and deterministic.
+
+## Discovery Spikes
+- Skill usage frequency ranking: needs a bounded source of invocation telemetry before it can be recommended.
+
+## Rejected / Not Practical Yet
+- Personalized skill suggestions from private user history: rejected because the repository does not have access to private Codex usage history.

package/plugins/src/base/skills/project-ideation/examples/public-external-inspiration.md

@@ -0,0 +1,22 @@
+# Public External Inspiration Example Output
+
+## What Already Exists
+- The host project already has a command catalog and source-authored skill files.
+- The host project can inspect public documentation pages without sign-in.
+- Existing verification can run through CLI commands and generated markdown artifacts.
+
+## Practical Ideas
+### 1. Public Pattern Checklist Import
+- User value: Maintainers can compare their command guidance against public best-practice pages without copying private or paid content.
+- Existing fit: Builds on the current docs and skill authoring workflow.
+- Data/source path: A public, no-login documentation URL supplied by the user, plus local `README.md` and skill files.
+- Practical slice: Generate a checklist of public patterns found in the external page and mark whether each is already represented locally.
+- Empirical verification: Run the ideation workflow against a fixed public URL and inspect the generated checklist.
+- Evidence: Generated markdown containing source URLs, matched local file paths, and unmatched public patterns.
+- Confidence: medium because public pages can change, but the source path is accessible and citeable.
+
+## Discovery Spikes
+- Automated freshness checks for public pages: needs a policy for when external pages may be re-fetched and cached.
+
+## Rejected / Not Practical Yet
+- Importing examples from a sign-in-only competitor workspace: rejected because the data source is not publicly obtainable.

package/plugins/src/base/skills/project-ideation/examples/unavailable-data-rejection.md

@@ -0,0 +1,22 @@
+# Unavailable Data Rejection Example Output
+
+## What Already Exists
+- The host project can read local source files, docs, scripts, and generated artifacts.
+- The host project does not expose customer analytics, private support tickets, or paid market datasets.
+
+## Practical Ideas
+### 1. Local Verification Gap Finder
+- User value: Maintainers can identify skills that describe empirical verification but do not name an evidence artifact.
+- Existing fit: Builds on local skill markdown files and existing unit tests.
+- Data/source path: Local `SKILL.md` files under the plugin source tree.
+- Practical slice: Scan skill files for verification sections and report entries that mention tests but no observable artifact.
+- Empirical verification: Run the scanner against a fixture skill with one missing evidence line.
+- Evidence: CLI output naming the fixture skill and the missing evidence field.
+- Confidence: high because the input is local and fully inspectable.
+
+## Discovery Spikes
+- Prioritize gaps by real-world usage: needs an obtainable telemetry source or a manually approved usage export before it can rank by frequency.
+
+## Rejected / Not Practical Yet
+- Recommend ideas from private customer support pain points: rejected because the missing source is a legitimate support-ticket export or configured support integration.
+- Recommend ideas from paid analyst reports: rejected because the missing source is a licensed data feed available to the agent at runtime.