@codyswann/lisa 1.86.2 → 1.86.3

package/package.json

@@ -78,7 +78,7 @@
     "lodash": ">=4.18.1"
   },
   "name": "@codyswann/lisa",
-  "version": "1.86.2",
+  "version": "1.86.3",
   "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": "1.86.2",
+  "version": "1.86.3",
   "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa/agents/jira-agent.md

@@ -76,7 +76,7 @@ If the ticket type is ambiguous, read the description to classify. A "Task" that
 
 ### 5. Delegate to Flow
 
-Hand off to the appropriate flow as defined in `.claude/rules/intent-routing.md`. Pass the full ticket context (description, acceptance criteria, credentials, reproduction steps) to the first agent in the flow.
+Hand off to the appropriate flow as defined in the `intent-routing` rule (loaded via the lisa plugin). Pass the full ticket context (description, acceptance criteria, credentials, reproduction steps) to the first agent in the flow.
 
 ### 6. Sync Progress at Milestones
 

package/plugins/lisa/commands/build.md

@@ -3,7 +3,7 @@ description: "Build a feature. Defines acceptance criteria, researches codebase,
 argument-hint: "<description-or-ticket-id-or-url>"
 ---
 
-Read `.claude/rules/intent-routing.md` and execute the **Implement** flow with the **Build** work type.
+Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Implement** flow with the **Build** work type.
 
 If the argument is a JIRA ticket ID or URL, hand off to the `jira-agent` which will read the ticket, extract context, and delegate back to the Implement flow.
 

package/plugins/lisa/commands/fix.md

@@ -3,7 +3,7 @@ description: "Fix a bug. Reproduces, analyzes git history, finds root cause, imp
 argument-hint: "<description-or-ticket-id-or-url>"
 ---
 
-Read `.claude/rules/intent-routing.md` and execute the **Implement** flow with the **Fix** work type.
+Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Implement** flow with the **Fix** work type.
 
 If the argument is a JIRA ticket ID or URL, hand off to the `jira-agent` which will read the ticket, extract context, and delegate back to the Implement flow.
 

package/plugins/lisa/commands/improve.md

@@ -3,7 +3,7 @@ description: "Improve existing code. Measures baseline, implements improvements
 argument-hint: "<target-description>"
 ---
 
-Read `.claude/rules/intent-routing.md` and execute the **Implement** flow with the **Improve** work type.
+Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Implement** flow with the **Improve** work type.
 
 For specific improvement types, you can also use:
 - `/lisa:plan:add-test-coverage` -- increase test coverage

package/plugins/lisa/commands/investigate.md

@@ -3,7 +3,7 @@ description: "Investigate an issue. Analyzes git history, reproduces, traces exe
 argument-hint: "<description-or-ticket-id-or-url>"
 ---
 
-Read `.claude/rules/intent-routing.md` and execute the **Implement** flow with the **Investigate Only** work type (spike).
+Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Implement** flow with the **Investigate Only** work type (spike).
 
 If the argument is a JIRA ticket ID or URL, hand off to the `jira-agent` which will read the ticket and extract context.
 

package/plugins/lisa/commands/monitor.md

@@ -3,7 +3,7 @@ description: "Monitor application health. Checks health endpoints, logs, errors,
 argument-hint: "[environment]"
 ---
 
-Read `.claude/rules/intent-routing.md` and execute the **Monitor** sub-flow.
+Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Monitor** sub-flow.
 
 This sub-flow is also invoked as part of the Verify flow's remote verification step. Delegates to `ops-specialist` for health checks, log inspection, error monitoring, and performance analysis.
 

package/plugins/lisa/commands/plan/create.md

@@ -3,6 +3,6 @@ description: "Creates an implementation plan from a ticket URL, file path, or te
 argument-hint: "<ticket-url | @file-path | description>"
 ---
 
-Read `.claude/rules/intent-routing.md` and execute the **Plan** flow on $ARGUMENTS.
+Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Plan** flow on $ARGUMENTS.
 
 If requirements are ambiguous or no specification exists, suggest running the **Research** flow first.

package/plugins/lisa/commands/plan/execute.md

@@ -3,4 +3,4 @@ description: "Deploys an agent team to research, implement, review and deploy a
 argument-hint: "<ticket-url | @file-path | description>"
 ---
 
-Pass through to `/build` with $ARGUMENTS. The Build command reads `.claude/rules/intent-routing.md` and runs the full Implement → Review → Verify chain, which is what this command historically did.
+Pass through to `/build` with $ARGUMENTS. The Build command applies the `intent-routing` rule (loaded via the lisa plugin) and runs the full Implement → Review → Verify chain, which is what this command historically did.

package/plugins/lisa/commands/plan.md

@@ -3,7 +3,7 @@ description: "Plan work. Defines acceptance criteria, researches codebase, maps
 argument-hint: "<description-or-ticket-id-or-url>"
 ---
 
-Read `.claude/rules/intent-routing.md` and execute the **Plan** flow.
+Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Plan** flow.
 
 If no PRD or specification exists, suggest running the **Research** flow first to produce one.
 

package/plugins/lisa/commands/research.md

@@ -3,6 +3,6 @@ description: "Research a problem space and produce a PRD. Investigates codebase,
 argument-hint: "<problem-statement-or-feature-idea>"
 ---
 
-Read `.claude/rules/intent-routing.md` and execute the **Research** flow.
+Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Research** flow.
 
 $ARGUMENTS

package/plugins/lisa/commands/review.md

@@ -3,7 +3,7 @@ description: "Review code changes. Runs quality, security, performance, product,
 argument-hint: "[pr-link-or-branch]"
 ---
 
-Read `.claude/rules/intent-routing.md` and execute the **Review** sub-flow.
+Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Review** sub-flow.
 
 This sub-flow is also invoked automatically by the Implement flow. It runs `quality-specialist`, `security-specialist`, and `performance-specialist` in parallel, followed by `product-specialist` and `test-specialist`. Consolidates all findings ranked by severity.
 

package/plugins/lisa/commands/ship.md

@@ -3,6 +3,6 @@ description: "Ship current changes. Alias for /verify."
 argument-hint: "[commit-message-hint]"
 ---
 
-Read `.claude/rules/intent-routing.md` and execute the **Verify** flow.
+Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Verify** flow.
 
 $ARGUMENTS

package/plugins/lisa/commands/verify.md

@@ -3,7 +3,7 @@ description: "Ship and verify code. Commits, opens PR, handles review loop, merg
 argument-hint: "[commit-message-hint]"
 ---
 
-Read `.claude/rules/intent-routing.md` and execute the **Verify** flow.
+Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Verify** flow.
 
 This includes: atomic commits, PR creation, CI/review-fix loop, merge, deploy monitoring, and remote verification.
 

package/plugins/lisa/skills/plan-execute/SKILL.md

@@ -47,7 +47,7 @@ If Implement, determine the work type:
 3. Improve (refactoring, optimization, coverage improvement)
 4. Investigate Only (spike -- no code changes, just findings)
 
-Run the readiness gate check for the selected flow as defined in `.claude/rules/intent-routing.md`. If the gate fails, stop and report what is missing.
+Run the readiness gate check for the selected flow as defined in the `intent-routing` rule (loaded via the lisa plugin). If the gate fails, stop and report what is missing.
 
 IF it is a Fix (bug), execute the Reproduce sub-flow FIRST:
 1. Write a failing test that demonstrates the bug (preferred)

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

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

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

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

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

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

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "1.86.2",
+  "version": "1.86.3",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting 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": "1.86.2",
+  "version": "1.86.3",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/src/base/agents/jira-agent.md

@@ -76,7 +76,7 @@ If the ticket type is ambiguous, read the description to classify. A "Task" that
 
 ### 5. Delegate to Flow
 
-Hand off to the appropriate flow as defined in `.claude/rules/intent-routing.md`. Pass the full ticket context (description, acceptance criteria, credentials, reproduction steps) to the first agent in the flow.
+Hand off to the appropriate flow as defined in the `intent-routing` rule (loaded via the lisa plugin). Pass the full ticket context (description, acceptance criteria, credentials, reproduction steps) to the first agent in the flow.
 
 ### 6. Sync Progress at Milestones
 

package/plugins/src/base/commands/build.md

@@ -3,7 +3,7 @@ description: "Build a feature. Defines acceptance criteria, researches codebase,
 argument-hint: "<description-or-ticket-id-or-url>"
 ---
 
-Read `.claude/rules/intent-routing.md` and execute the **Implement** flow with the **Build** work type.
+Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Implement** flow with the **Build** work type.
 
 If the argument is a JIRA ticket ID or URL, hand off to the `jira-agent` which will read the ticket, extract context, and delegate back to the Implement flow.
 

package/plugins/src/base/commands/fix.md

@@ -3,7 +3,7 @@ description: "Fix a bug. Reproduces, analyzes git history, finds root cause, imp
 argument-hint: "<description-or-ticket-id-or-url>"
 ---
 
-Read `.claude/rules/intent-routing.md` and execute the **Implement** flow with the **Fix** work type.
+Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Implement** flow with the **Fix** work type.
 
 If the argument is a JIRA ticket ID or URL, hand off to the `jira-agent` which will read the ticket, extract context, and delegate back to the Implement flow.
 

package/plugins/src/base/commands/improve.md

@@ -3,7 +3,7 @@ description: "Improve existing code. Measures baseline, implements improvements
 argument-hint: "<target-description>"
 ---
 
-Read `.claude/rules/intent-routing.md` and execute the **Implement** flow with the **Improve** work type.
+Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Implement** flow with the **Improve** work type.
 
 For specific improvement types, you can also use:
 - `/lisa:plan:add-test-coverage` -- increase test coverage

package/plugins/src/base/commands/investigate.md

@@ -3,7 +3,7 @@ description: "Investigate an issue. Analyzes git history, reproduces, traces exe
 argument-hint: "<description-or-ticket-id-or-url>"
 ---
 
-Read `.claude/rules/intent-routing.md` and execute the **Implement** flow with the **Investigate Only** work type (spike).
+Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Implement** flow with the **Investigate Only** work type (spike).
 
 If the argument is a JIRA ticket ID or URL, hand off to the `jira-agent` which will read the ticket and extract context.
 

package/plugins/src/base/commands/monitor.md

@@ -3,7 +3,7 @@ description: "Monitor application health. Checks health endpoints, logs, errors,
 argument-hint: "[environment]"
 ---
 
-Read `.claude/rules/intent-routing.md` and execute the **Monitor** sub-flow.
+Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Monitor** sub-flow.
 
 This sub-flow is also invoked as part of the Verify flow's remote verification step. Delegates to `ops-specialist` for health checks, log inspection, error monitoring, and performance analysis.
 

package/plugins/src/base/commands/plan/create.md

@@ -3,6 +3,6 @@ description: "Creates an implementation plan from a ticket URL, file path, or te
 argument-hint: "<ticket-url | @file-path | description>"
 ---
 
-Read `.claude/rules/intent-routing.md` and execute the **Plan** flow on $ARGUMENTS.
+Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Plan** flow on $ARGUMENTS.
 
 If requirements are ambiguous or no specification exists, suggest running the **Research** flow first.

package/plugins/src/base/commands/plan/execute.md

@@ -3,4 +3,4 @@ description: "Deploys an agent team to research, implement, review and deploy a
 argument-hint: "<ticket-url | @file-path | description>"
 ---
 
-Pass through to `/build` with $ARGUMENTS. The Build command reads `.claude/rules/intent-routing.md` and runs the full Implement → Review → Verify chain, which is what this command historically did.
+Pass through to `/build` with $ARGUMENTS. The Build command applies the `intent-routing` rule (loaded via the lisa plugin) and runs the full Implement → Review → Verify chain, which is what this command historically did.

package/plugins/src/base/commands/plan.md

@@ -3,7 +3,7 @@ description: "Plan work. Defines acceptance criteria, researches codebase, maps
 argument-hint: "<description-or-ticket-id-or-url>"
 ---
 
-Read `.claude/rules/intent-routing.md` and execute the **Plan** flow.
+Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Plan** flow.
 
 If no PRD or specification exists, suggest running the **Research** flow first to produce one.
 

package/plugins/src/base/commands/research.md

@@ -3,6 +3,6 @@ description: "Research a problem space and produce a PRD. Investigates codebase,
 argument-hint: "<problem-statement-or-feature-idea>"
 ---
 
-Read `.claude/rules/intent-routing.md` and execute the **Research** flow.
+Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Research** flow.
 
 $ARGUMENTS

package/plugins/src/base/commands/review.md

@@ -3,7 +3,7 @@ description: "Review code changes. Runs quality, security, performance, product,
 argument-hint: "[pr-link-or-branch]"
 ---
 
-Read `.claude/rules/intent-routing.md` and execute the **Review** sub-flow.
+Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Review** sub-flow.
 
 This sub-flow is also invoked automatically by the Implement flow. It runs `quality-specialist`, `security-specialist`, and `performance-specialist` in parallel, followed by `product-specialist` and `test-specialist`. Consolidates all findings ranked by severity.
 

package/plugins/src/base/commands/ship.md

@@ -3,6 +3,6 @@ description: "Ship current changes. Alias for /verify."
 argument-hint: "[commit-message-hint]"
 ---
 
-Read `.claude/rules/intent-routing.md` and execute the **Verify** flow.
+Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Verify** flow.
 
 $ARGUMENTS

package/plugins/src/base/commands/verify.md

@@ -3,7 +3,7 @@ description: "Ship and verify code. Commits, opens PR, handles review loop, merg
 argument-hint: "[commit-message-hint]"
 ---
 
-Read `.claude/rules/intent-routing.md` and execute the **Verify** flow.
+Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Verify** flow.
 
 This includes: atomic commits, PR creation, CI/review-fix loop, merge, deploy monitoring, and remote verification.
 

package/plugins/src/base/skills/plan-execute/SKILL.md

@@ -47,7 +47,7 @@ If Implement, determine the work type:
 3. Improve (refactoring, optimization, coverage improvement)
 4. Investigate Only (spike -- no code changes, just findings)
 
-Run the readiness gate check for the selected flow as defined in `.claude/rules/intent-routing.md`. If the gate fails, stop and report what is missing.
+Run the readiness gate check for the selected flow as defined in the `intent-routing` rule (loaded via the lisa plugin). If the gate fails, stop and report what is missing.
 
 IF it is a Fix (bug), execute the Reproduce sub-flow FIRST:
 1. Write a failing test that demonstrates the bug (preferred)