@codyswann/lisa 1.95.0 → 2.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (200) hide show
  1. package/dist/cli/index.d.ts.map +1 -1
  2. package/dist/cli/index.js +41 -5
  3. package/dist/cli/index.js.map +1 -1
  4. package/dist/codex/agent-installer.d.ts +56 -0
  5. package/dist/codex/agent-installer.d.ts.map +1 -0
  6. package/dist/codex/agent-installer.js +201 -0
  7. package/dist/codex/agent-installer.js.map +1 -0
  8. package/dist/codex/agent-transformer.d.ts +53 -0
  9. package/dist/codex/agent-transformer.d.ts.map +1 -0
  10. package/dist/codex/agent-transformer.js +181 -0
  11. package/dist/codex/agent-transformer.js.map +1 -0
  12. package/dist/codex/agents-md-installer.d.ts +24 -0
  13. package/dist/codex/agents-md-installer.d.ts.map +1 -0
  14. package/dist/codex/agents-md-installer.js +63 -0
  15. package/dist/codex/agents-md-installer.js.map +1 -0
  16. package/dist/codex/hooks-installer.d.ts +24 -0
  17. package/dist/codex/hooks-installer.d.ts.map +1 -0
  18. package/dist/codex/hooks-installer.js +206 -0
  19. package/dist/codex/hooks-installer.js.map +1 -0
  20. package/dist/codex/hooks-merger.d.ts +82 -0
  21. package/dist/codex/hooks-merger.d.ts.map +1 -0
  22. package/dist/codex/hooks-merger.js +127 -0
  23. package/dist/codex/hooks-merger.js.map +1 -0
  24. package/dist/codex/manifest.d.ts +32 -0
  25. package/dist/codex/manifest.d.ts.map +1 -0
  26. package/dist/codex/manifest.js +86 -0
  27. package/dist/codex/manifest.js.map +1 -0
  28. package/dist/codex/settings-installer.d.ts +48 -0
  29. package/dist/codex/settings-installer.d.ts.map +1 -0
  30. package/dist/codex/settings-installer.js +276 -0
  31. package/dist/codex/settings-installer.js.map +1 -0
  32. package/dist/codex/skills-installer.d.ts +46 -0
  33. package/dist/codex/skills-installer.d.ts.map +1 -0
  34. package/dist/codex/skills-installer.js +344 -0
  35. package/dist/codex/skills-installer.js.map +1 -0
  36. package/dist/core/config.d.ts +19 -0
  37. package/dist/core/config.d.ts.map +1 -1
  38. package/dist/core/config.js +13 -0
  39. package/dist/core/config.js.map +1 -1
  40. package/dist/core/lisa.d.ts +12 -0
  41. package/dist/core/lisa.d.ts.map +1 -1
  42. package/dist/core/lisa.js +48 -0
  43. package/dist/core/lisa.js.map +1 -1
  44. package/dist/core/project-config.d.ts +49 -0
  45. package/dist/core/project-config.d.ts.map +1 -0
  46. package/dist/core/project-config.js +119 -0
  47. package/dist/core/project-config.js.map +1 -0
  48. package/package.json +3 -1
  49. package/plugins/lisa/.claude-plugin/plugin.json +1 -1
  50. package/plugins/lisa/agents/jira-build-intake.md +58 -0
  51. package/plugins/lisa/agents/notion-prd-intake.md +57 -0
  52. package/plugins/lisa/commands/{plan/fix-linter-error.md → fix/linter-error.md} +1 -1
  53. package/plugins/lisa/commands/implement.md +6 -0
  54. package/plugins/{src/base/commands/plan/lower-code-complexity.md → lisa/commands/improve/code-complexity.md} +1 -1
  55. package/plugins/lisa/commands/{plan/reduce-max-lines-per-function.md → improve/max-lines-per-function.md} +1 -1
  56. package/plugins/lisa/commands/{plan/add-test-coverage.md → improve/test-coverage.md} +1 -1
  57. package/plugins/lisa/commands/{plan/improve-tests.md → improve/tests.md} +1 -1
  58. package/plugins/lisa/commands/plan.md +15 -3
  59. package/plugins/lisa/commands/product-walkthrough.md +7 -0
  60. package/plugins/{src/base/commands/plan/local-code-review.md → lisa/commands/review/local.md} +1 -1
  61. package/plugins/{src/base/skills/plan-fix-linter-error → lisa/skills/fix-linter-error}/SKILL.md +2 -2
  62. package/plugins/lisa/skills/{plan-execute → implement}/SKILL.md +1 -1
  63. package/plugins/lisa/skills/{plan-lower-code-complexity → improve-code-complexity}/SKILL.md +2 -2
  64. package/plugins/lisa/skills/{plan-reduce-max-lines → improve-max-lines}/SKILL.md +2 -2
  65. package/plugins/{src/base/skills/plan-reduce-max-lines-per-function → lisa/skills/improve-max-lines-per-function}/SKILL.md +2 -2
  66. package/plugins/lisa/skills/{plan-add-test-coverage → improve-test-coverage}/SKILL.md +2 -2
  67. package/plugins/{src/base/skills/plan-improve-tests → lisa/skills/improve-tests}/SKILL.md +2 -2
  68. package/plugins/lisa/skills/jira-build-intake/SKILL.md +134 -0
  69. package/plugins/lisa/skills/jira-create/SKILL.md +53 -30
  70. package/plugins/lisa/skills/jira-source-artifacts/SKILL.md +107 -0
  71. package/plugins/lisa/skills/jira-validate-ticket/SKILL.md +224 -0
  72. package/plugins/lisa/skills/jira-verify/SKILL.md +15 -91
  73. package/plugins/lisa/skills/jira-write-ticket/SKILL.md +20 -15
  74. package/plugins/lisa/skills/notion-prd-intake/SKILL.md +169 -0
  75. package/plugins/lisa/skills/notion-to-jira/SKILL.md +137 -95
  76. package/plugins/lisa/skills/prd-ticket-coverage/SKILL.md +137 -0
  77. package/plugins/lisa/skills/product-walkthrough/SKILL.md +129 -0
  78. package/plugins/lisa/skills/{plan-local-code-review → review-local}/SKILL.md +1 -1
  79. package/plugins/lisa-cdk/.claude-plugin/plugin.json +1 -1
  80. package/plugins/lisa-expo/.claude-plugin/plugin.json +1 -1
  81. package/plugins/lisa-expo/skills/jira-create/SKILL.md +60 -28
  82. package/plugins/lisa-expo/skills/jira-verify/SKILL.md +14 -34
  83. package/plugins/lisa-nestjs/.claude-plugin/plugin.json +1 -1
  84. package/plugins/lisa-rails/.claude-plugin/plugin.json +1 -1
  85. package/plugins/lisa-rails/skills/{plan-fix-linter-error → fix-linter-error}/SKILL.md +2 -2
  86. package/plugins/lisa-rails/skills/{plan-lower-code-complexity → improve-code-complexity}/SKILL.md +2 -2
  87. package/plugins/{src/rails/skills/plan-reduce-max-lines → lisa-rails/skills/improve-max-lines}/SKILL.md +2 -2
  88. package/plugins/{src/rails/skills/plan-reduce-max-lines-per-function → lisa-rails/skills/improve-max-lines-per-function}/SKILL.md +2 -2
  89. package/plugins/lisa-rails/skills/{plan-add-test-coverage → improve-test-coverage}/SKILL.md +2 -2
  90. package/plugins/lisa-rails/skills/jira-create/SKILL.md +59 -28
  91. package/plugins/lisa-rails/skills/jira-verify/SKILL.md +13 -16
  92. package/plugins/lisa-typescript/.claude-plugin/plugin.json +1 -1
  93. package/plugins/src/base/agents/jira-build-intake.md +58 -0
  94. package/plugins/src/base/agents/notion-prd-intake.md +57 -0
  95. package/plugins/src/base/commands/{plan/fix-linter-error.md → fix/linter-error.md} +1 -1
  96. package/plugins/src/base/commands/implement.md +6 -0
  97. package/plugins/{lisa/commands/plan/lower-code-complexity.md → src/base/commands/improve/code-complexity.md} +1 -1
  98. package/plugins/src/base/commands/{plan/reduce-max-lines-per-function.md → improve/max-lines-per-function.md} +1 -1
  99. package/plugins/src/base/commands/{plan/add-test-coverage.md → improve/test-coverage.md} +1 -1
  100. package/plugins/src/base/commands/{plan/improve-tests.md → improve/tests.md} +1 -1
  101. package/plugins/src/base/commands/plan.md +15 -3
  102. package/plugins/src/base/commands/product-walkthrough.md +7 -0
  103. package/plugins/{lisa/commands/plan/local-code-review.md → src/base/commands/review/local.md} +1 -1
  104. package/plugins/{lisa/skills/plan-fix-linter-error → src/base/skills/fix-linter-error}/SKILL.md +2 -2
  105. package/plugins/src/base/skills/{plan-execute → implement}/SKILL.md +1 -1
  106. package/plugins/src/base/skills/{plan-lower-code-complexity → improve-code-complexity}/SKILL.md +2 -2
  107. package/plugins/src/base/skills/{plan-reduce-max-lines → improve-max-lines}/SKILL.md +2 -2
  108. package/plugins/{lisa/skills/plan-reduce-max-lines-per-function → src/base/skills/improve-max-lines-per-function}/SKILL.md +2 -2
  109. package/plugins/src/base/skills/{plan-add-test-coverage → improve-test-coverage}/SKILL.md +2 -2
  110. package/plugins/{lisa/skills/plan-improve-tests → src/base/skills/improve-tests}/SKILL.md +2 -2
  111. package/plugins/src/base/skills/jira-build-intake/SKILL.md +134 -0
  112. package/plugins/src/base/skills/jira-create/SKILL.md +53 -30
  113. package/plugins/src/base/skills/jira-source-artifacts/SKILL.md +107 -0
  114. package/plugins/src/base/skills/jira-validate-ticket/SKILL.md +224 -0
  115. package/plugins/src/base/skills/jira-verify/SKILL.md +15 -91
  116. package/plugins/src/base/skills/jira-write-ticket/SKILL.md +20 -15
  117. package/plugins/src/base/skills/notion-prd-intake/SKILL.md +169 -0
  118. package/plugins/src/base/skills/notion-to-jira/SKILL.md +137 -95
  119. package/plugins/src/base/skills/prd-ticket-coverage/SKILL.md +137 -0
  120. package/plugins/src/base/skills/product-walkthrough/SKILL.md +129 -0
  121. package/plugins/src/base/skills/{plan-local-code-review → review-local}/SKILL.md +1 -1
  122. package/plugins/src/expo/skills/jira-create/SKILL.md +60 -28
  123. package/plugins/src/expo/skills/jira-verify/SKILL.md +14 -34
  124. package/plugins/src/rails/skills/{plan-fix-linter-error → fix-linter-error}/SKILL.md +2 -2
  125. package/plugins/src/rails/skills/{plan-lower-code-complexity → improve-code-complexity}/SKILL.md +2 -2
  126. package/plugins/{lisa-rails/skills/plan-reduce-max-lines → src/rails/skills/improve-max-lines}/SKILL.md +2 -2
  127. package/plugins/{lisa-rails/skills/plan-reduce-max-lines-per-function → src/rails/skills/improve-max-lines-per-function}/SKILL.md +2 -2
  128. package/plugins/src/rails/skills/{plan-add-test-coverage → improve-test-coverage}/SKILL.md +2 -2
  129. package/plugins/src/rails/skills/jira-create/SKILL.md +59 -28
  130. package/plugins/src/rails/skills/jira-verify/SKILL.md +13 -16
  131. package/plugins/lisa/commands/build.md +0 -12
  132. package/plugins/lisa/commands/fix.md +0 -12
  133. package/plugins/lisa/commands/improve.md +0 -18
  134. package/plugins/lisa/commands/investigate.md +0 -10
  135. package/plugins/lisa/commands/jira/add-journey.md +0 -7
  136. package/plugins/lisa/commands/jira/create.md +0 -7
  137. package/plugins/lisa/commands/jira/evidence.md +0 -7
  138. package/plugins/lisa/commands/jira/journey.md +0 -7
  139. package/plugins/lisa/commands/jira/read-ticket.md +0 -7
  140. package/plugins/lisa/commands/jira/sync.md +0 -7
  141. package/plugins/lisa/commands/jira/triage.md +0 -7
  142. package/plugins/lisa/commands/jira/verify.md +0 -7
  143. package/plugins/lisa/commands/jira/write-ticket.md +0 -7
  144. package/plugins/lisa/commands/plan/create.md +0 -8
  145. package/plugins/lisa/commands/plan/execute.md +0 -6
  146. package/plugins/lisa/commands/review/implementation.md +0 -7
  147. package/plugins/lisa/commands/review.md +0 -10
  148. package/plugins/lisa/commands/ship.md +0 -8
  149. package/plugins/lisa/commands/spec-conformance.md +0 -7
  150. package/plugins/lisa-expo/commands/jira/add-journey.md +0 -7
  151. package/plugins/lisa-expo/commands/jira/create.md +0 -7
  152. package/plugins/lisa-expo/commands/jira/evidence.md +0 -7
  153. package/plugins/lisa-expo/commands/jira/journey.md +0 -7
  154. package/plugins/lisa-expo/commands/jira/verify.md +0 -7
  155. package/plugins/lisa-rails/commands/jira/add-journey.md +0 -7
  156. package/plugins/lisa-rails/commands/jira/create.md +0 -7
  157. package/plugins/lisa-rails/commands/jira/evidence.md +0 -7
  158. package/plugins/lisa-rails/commands/jira/journey.md +0 -7
  159. package/plugins/lisa-rails/commands/jira/verify.md +0 -7
  160. package/plugins/src/base/commands/build.md +0 -12
  161. package/plugins/src/base/commands/fix.md +0 -12
  162. package/plugins/src/base/commands/improve.md +0 -18
  163. package/plugins/src/base/commands/investigate.md +0 -10
  164. package/plugins/src/base/commands/jira/add-journey.md +0 -7
  165. package/plugins/src/base/commands/jira/create.md +0 -7
  166. package/plugins/src/base/commands/jira/evidence.md +0 -7
  167. package/plugins/src/base/commands/jira/journey.md +0 -7
  168. package/plugins/src/base/commands/jira/read-ticket.md +0 -7
  169. package/plugins/src/base/commands/jira/sync.md +0 -7
  170. package/plugins/src/base/commands/jira/triage.md +0 -7
  171. package/plugins/src/base/commands/jira/verify.md +0 -7
  172. package/plugins/src/base/commands/jira/write-ticket.md +0 -7
  173. package/plugins/src/base/commands/plan/create.md +0 -8
  174. package/plugins/src/base/commands/plan/execute.md +0 -6
  175. package/plugins/src/base/commands/review/implementation.md +0 -7
  176. package/plugins/src/base/commands/review.md +0 -10
  177. package/plugins/src/base/commands/ship.md +0 -8
  178. package/plugins/src/base/commands/spec-conformance.md +0 -7
  179. package/plugins/src/expo/commands/jira/add-journey.md +0 -7
  180. package/plugins/src/expo/commands/jira/create.md +0 -7
  181. package/plugins/src/expo/commands/jira/evidence.md +0 -7
  182. package/plugins/src/expo/commands/jira/journey.md +0 -7
  183. package/plugins/src/expo/commands/jira/verify.md +0 -7
  184. package/plugins/src/rails/commands/jira/add-journey.md +0 -7
  185. package/plugins/src/rails/commands/jira/create.md +0 -7
  186. package/plugins/src/rails/commands/jira/evidence.md +0 -7
  187. package/plugins/src/rails/commands/jira/journey.md +0 -7
  188. package/plugins/src/rails/commands/jira/verify.md +0 -7
  189. /package/plugins/lisa/commands/{plan/reduce-max-lines.md → improve/max-lines.md} +0 -0
  190. /package/plugins/lisa-rails/commands/{plan/fix-linter-error.md → fix/linter-error.md} +0 -0
  191. /package/plugins/lisa-rails/commands/{plan/lower-code-complexity.md → improve/code-complexity.md} +0 -0
  192. /package/plugins/lisa-rails/commands/{plan/reduce-max-lines-per-function.md → improve/max-lines-per-function.md} +0 -0
  193. /package/plugins/lisa-rails/commands/{plan/reduce-max-lines.md → improve/max-lines.md} +0 -0
  194. /package/plugins/lisa-rails/commands/{plan/add-test-coverage.md → improve/test-coverage.md} +0 -0
  195. /package/plugins/src/base/commands/{plan/reduce-max-lines.md → improve/max-lines.md} +0 -0
  196. /package/plugins/src/rails/commands/{plan/fix-linter-error.md → fix/linter-error.md} +0 -0
  197. /package/plugins/src/rails/commands/{plan/lower-code-complexity.md → improve/code-complexity.md} +0 -0
  198. /package/plugins/src/rails/commands/{plan/reduce-max-lines-per-function.md → improve/max-lines-per-function.md} +0 -0
  199. /package/plugins/src/rails/commands/{plan/reduce-max-lines.md → improve/max-lines.md} +0 -0
  200. /package/plugins/src/rails/commands/{plan/add-test-coverage.md → improve/test-coverage.md} +0 -0
@@ -1,8 +0,0 @@
1
- ---
2
- description: "Ship current changes. Alias for /verify."
3
- argument-hint: "[commit-message-hint]"
4
- ---
5
-
6
- Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Verify** flow.
7
-
8
- $ARGUMENTS
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Verify shipped work matches its spec — coverage matrix with scope-creep detection and verdict"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "[plan-file | TICKET-KEY | issue-url]"
5
- ---
6
-
7
- Use the /lisa:spec-conformance skill to compare shipped work against its spec and produce a coverage matrix with verdict. $ARGUMENTS
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Add Validation Journey section to existing ticket"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "<TICKET_ID>"
5
- ---
6
-
7
- Use the /lisa-expo:jira-add-journey skill to add a Validation Journey section to the ticket. $ARGUMENTS
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Create JIRA epics/stories/tasks from code files with comprehensive quality requirements"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "<file-or-directory-path> [project-key]"
5
- ---
6
-
7
- Use the /lisa-expo:jira-create skill to create JIRA issues from the provided input. $ARGUMENTS
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Post captured evidence to JIRA and GitHub PR"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "<TICKET_ID> <EVIDENCE_DIR> <PR_NUMBER>"
5
- ---
6
-
7
- Use the /lisa-expo:jira-evidence skill to post captured evidence to JIRA and the GitHub PR. $ARGUMENTS
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Execute Validation Journey and capture evidence"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "<TICKET_ID> [PR_NUMBER]"
5
- ---
6
-
7
- Use the /lisa-expo:jira-journey skill to execute the Validation Journey and capture evidence. $ARGUMENTS
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Verify JIRA ticket meets standards for epic relationships and description quality"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "<TICKET-ID>"
5
- ---
6
-
7
- Use the /lisa-expo:jira-verify skill to verify the JIRA ticket meets organizational standards. $ARGUMENTS
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Add Validation Journey section to existing ticket"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "<TICKET_ID>"
5
- ---
6
-
7
- Use the /lisa-rails:jira-add-journey skill to add a Validation Journey section to the ticket. $ARGUMENTS
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Create JIRA epics/stories/tasks from code files with comprehensive quality requirements"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "<file-or-directory-path> [project-key]"
5
- ---
6
-
7
- Use the /lisa-rails:jira-create skill to create JIRA issues from the provided input. $ARGUMENTS
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Post captured evidence to JIRA and GitHub PR"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "<TICKET_ID> <EVIDENCE_DIR> <PR_NUMBER>"
5
- ---
6
-
7
- Use the /lisa-rails:jira-evidence skill to post captured evidence to JIRA and the GitHub PR. $ARGUMENTS
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Execute Validation Journey and capture evidence"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "<TICKET_ID> [PR_NUMBER]"
5
- ---
6
-
7
- Use the /lisa-rails:jira-journey skill to execute the Validation Journey and capture evidence. $ARGUMENTS
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Verify JIRA ticket meets standards for epic relationships and description quality"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "<TICKET-ID>"
5
- ---
6
-
7
- Use the /lisa-rails:jira-verify skill to verify the JIRA ticket meets organizational standards. $ARGUMENTS
@@ -1,12 +0,0 @@
1
- ---
2
- description: "Build a feature. Defines acceptance criteria, researches codebase, implements via TDD, verifies locally, and reviews."
3
- argument-hint: "<description-or-ticket-id-or-url>"
4
- ---
5
-
6
- Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Implement** flow with the **Build** work type.
7
-
8
- **Orchestration: agent team.** Build runs a long multi-specialist sequence with parallel review. After echoing the flow and orchestration mode, your FIRST tool call MUST be `TeamCreate`. Do not call `TaskCreate`, `Agent`, or implementation tools before the team exists.
9
-
10
- 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.
11
-
12
- $ARGUMENTS
@@ -1,12 +0,0 @@
1
- ---
2
- description: "Fix a bug. Reproduces, analyzes git history, finds root cause, implements fix via TDD, verifies locally, and reviews."
3
- argument-hint: "<description-or-ticket-id-or-url>"
4
- ---
5
-
6
- Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Implement** flow with the **Fix** work type.
7
-
8
- **Orchestration: agent team.** Fix runs a long multi-specialist sequence with parallel review. After echoing the flow and orchestration mode, your FIRST tool call MUST be `TeamCreate`. Do not call `TaskCreate`, `Agent`, or implementation tools before the team exists.
9
-
10
- 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.
11
-
12
- $ARGUMENTS
@@ -1,18 +0,0 @@
1
- ---
2
- description: "Improve existing code. Measures baseline, implements improvements via TDD, measures again, and reviews."
3
- argument-hint: "<target-description>"
4
- ---
5
-
6
- Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Implement** flow with the **Improve** work type.
7
-
8
- **Orchestration: agent team.** Improve runs a multi-specialist sequence with parallel review. After echoing the flow and orchestration mode, your FIRST tool call MUST be `TeamCreate`. Do not call `TaskCreate`, `Agent`, or implementation tools before the team exists.
9
-
10
- For specific improvement types, you can also use:
11
- - `/lisa:plan:add-test-coverage` -- increase test coverage
12
- - `/lisa:plan:fix-linter-error` -- fix lint rule violations
13
- - `/lisa:plan:lower-code-complexity` -- reduce cognitive complexity
14
- - `/lisa:plan:reduce-max-lines` -- reduce file length
15
- - `/lisa:plan:reduce-max-lines-per-function` -- reduce function length
16
- - `/lisa:plan:improve-tests` -- improve test quality
17
-
18
- $ARGUMENTS
@@ -1,10 +0,0 @@
1
- ---
2
- description: "Investigate an issue. Analyzes git history, reproduces, traces execution, checks logs, and reports findings with evidence."
3
- argument-hint: "<description-or-ticket-id-or-url>"
4
- ---
5
-
6
- Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Implement** flow with the **Investigate Only** work type (spike).
7
-
8
- If the argument is a JIRA ticket ID or URL, hand off to the `jira-agent` which will read the ticket and extract context.
9
-
10
- $ARGUMENTS
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Add Validation Journey section to existing ticket"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "<TICKET_ID>"
5
- ---
6
-
7
- Use the /lisa:jira-add-journey skill to add a Validation Journey section to the ticket. $ARGUMENTS
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Create JIRA epics/stories/tasks from code files with comprehensive quality requirements"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "<file-or-directory-path> [project-key]"
5
- ---
6
-
7
- Use the /lisa:jira-create skill to create JIRA issues from the provided input. $ARGUMENTS
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Post captured evidence to JIRA and GitHub PR"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "<TICKET_ID> <EVIDENCE_DIR> <PR_NUMBER>"
5
- ---
6
-
7
- Use the /lisa:jira-evidence skill to post captured evidence to JIRA and the GitHub PR. $ARGUMENTS
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Execute Validation Journey and capture evidence"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "<TICKET_ID> [PR_NUMBER]"
5
- ---
6
-
7
- Use the /lisa:jira-journey skill to execute the Validation Journey and capture evidence. $ARGUMENTS
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Read a JIRA ticket with full scope — metadata, comments, remote PRs, linked tickets, epic siblings, subtasks"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "<TICKET-ID>"
5
- ---
6
-
7
- Use the /lisa:jira-read-ticket skill to fetch the full scope of the JIRA ticket and its related graph. $ARGUMENTS
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Sync plan progress to a linked JIRA ticket"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "<ticket-id>"
5
- ---
6
-
7
- Use the /lisa:jira-sync skill to sync plan progress to the linked JIRA ticket. $ARGUMENTS
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Analytical triage of a JIRA ticket -- ambiguity detection, edge case analysis, verification methodology"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "<TICKET-ID>"
5
- ---
6
-
7
- Use the /lisa:ticket-triage skill to run analytical triage on the JIRA ticket. $ARGUMENTS
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Verify JIRA ticket meets standards for epic relationships and description quality"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "<TICKET-ID>"
5
- ---
6
-
7
- Use the /lisa:jira-verify skill to verify the JIRA ticket meets organizational standards. $ARGUMENTS
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Create or update a JIRA ticket with enforced relationships, Gherkin criteria, and metadata quality gates"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "[TICKET-ID | <create-intent-description>]"
5
- ---
6
-
7
- Use the /lisa:jira-write-ticket skill to create or update the JIRA ticket with full relationship discovery and quality enforcement. $ARGUMENTS
@@ -1,8 +0,0 @@
1
- ---
2
- description: "Creates an implementation plan from a ticket URL, file path, or text description"
3
- argument-hint: "<ticket-url | @file-path | description>"
4
- ---
5
-
6
- Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Plan** flow on $ARGUMENTS.
7
-
8
- If requirements are ambiguous or no specification exists, suggest running the **Research** flow first.
@@ -1,6 +0,0 @@
1
- ---
2
- description: "Deploys an agent team to research, implement, review and deploy a plan"
3
- argument-hint: "<ticket-url | @file-path | description>"
4
- ---
5
-
6
- 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.
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Compare project's Lisa-managed files against Lisa source templates and offer to upstream changes"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "[lisa-dir]"
5
- ---
6
-
7
- Use the /lisa:lisa-review-implementation skill to compare project files against Lisa templates. $ARGUMENTS
@@ -1,10 +0,0 @@
1
- ---
2
- description: "Review code changes. Runs quality, security, performance, product, and test reviews in parallel, then consolidates findings."
3
- argument-hint: "[pr-link-or-branch]"
4
- ---
5
-
6
- Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Review** sub-flow.
7
-
8
- 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.
9
-
10
- $ARGUMENTS
@@ -1,8 +0,0 @@
1
- ---
2
- description: "Ship current changes. Alias for /verify."
3
- argument-hint: "[commit-message-hint]"
4
- ---
5
-
6
- Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Verify** flow.
7
-
8
- $ARGUMENTS
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Verify shipped work matches its spec — coverage matrix with scope-creep detection and verdict"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "[plan-file | TICKET-KEY | issue-url]"
5
- ---
6
-
7
- Use the /lisa:spec-conformance skill to compare shipped work against its spec and produce a coverage matrix with verdict. $ARGUMENTS
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Add Validation Journey section to existing ticket"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "<TICKET_ID>"
5
- ---
6
-
7
- Use the /lisa-expo:jira-add-journey skill to add a Validation Journey section to the ticket. $ARGUMENTS
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Create JIRA epics/stories/tasks from code files with comprehensive quality requirements"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "<file-or-directory-path> [project-key]"
5
- ---
6
-
7
- Use the /lisa-expo:jira-create skill to create JIRA issues from the provided input. $ARGUMENTS
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Post captured evidence to JIRA and GitHub PR"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "<TICKET_ID> <EVIDENCE_DIR> <PR_NUMBER>"
5
- ---
6
-
7
- Use the /lisa-expo:jira-evidence skill to post captured evidence to JIRA and the GitHub PR. $ARGUMENTS
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Execute Validation Journey and capture evidence"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "<TICKET_ID> [PR_NUMBER]"
5
- ---
6
-
7
- Use the /lisa-expo:jira-journey skill to execute the Validation Journey and capture evidence. $ARGUMENTS
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Verify JIRA ticket meets standards for epic relationships and description quality"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "<TICKET-ID>"
5
- ---
6
-
7
- Use the /lisa-expo:jira-verify skill to verify the JIRA ticket meets organizational standards. $ARGUMENTS
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Add Validation Journey section to existing ticket"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "<TICKET_ID>"
5
- ---
6
-
7
- Use the /lisa-rails:jira-add-journey skill to add a Validation Journey section to the ticket. $ARGUMENTS
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Create JIRA epics/stories/tasks from code files with comprehensive quality requirements"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "<file-or-directory-path> [project-key]"
5
- ---
6
-
7
- Use the /lisa-rails:jira-create skill to create JIRA issues from the provided input. $ARGUMENTS
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Post captured evidence to JIRA and GitHub PR"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "<TICKET_ID> <EVIDENCE_DIR> <PR_NUMBER>"
5
- ---
6
-
7
- Use the /lisa-rails:jira-evidence skill to post captured evidence to JIRA and the GitHub PR. $ARGUMENTS
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Execute Validation Journey and capture evidence"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "<TICKET_ID> [PR_NUMBER]"
5
- ---
6
-
7
- Use the /lisa-rails:jira-journey skill to execute the Validation Journey and capture evidence. $ARGUMENTS
@@ -1,7 +0,0 @@
1
- ---
2
- description: "Verify JIRA ticket meets standards for epic relationships and description quality"
3
- allowed-tools: ["Skill"]
4
- argument-hint: "<TICKET-ID>"
5
- ---
6
-
7
- Use the /lisa-rails:jira-verify skill to verify the JIRA ticket meets organizational standards. $ARGUMENTS