@codyswann/lisa 1.96.0 → 2.1.0

package/plugins/lisa-expo/commands/jira/add-journey.md

@@ -1,7 +0,0 @@
----
-description: "Add Validation Journey section to existing ticket"
-allowed-tools: ["Skill"]
-argument-hint: "<TICKET_ID>"
----
-
-Use the /lisa-expo:jira-add-journey skill to add a Validation Journey section to the ticket. $ARGUMENTS

package/plugins/lisa-expo/commands/jira/create.md

@@ -1,7 +0,0 @@
----
-description: "Create JIRA epics/stories/tasks from code files with comprehensive quality requirements"
-allowed-tools: ["Skill"]
-argument-hint: "<file-or-directory-path> [project-key]"
----
-
-Use the /lisa-expo:jira-create skill to create JIRA issues from the provided input. $ARGUMENTS

package/plugins/lisa-expo/commands/jira/evidence.md

@@ -1,7 +0,0 @@
----
-description: "Post captured evidence to JIRA and GitHub PR"
-allowed-tools: ["Skill"]
-argument-hint: "<TICKET_ID> <EVIDENCE_DIR> <PR_NUMBER>"
----
-
-Use the /lisa-expo:jira-evidence skill to post captured evidence to JIRA and the GitHub PR. $ARGUMENTS

package/plugins/lisa-expo/commands/jira/journey.md

@@ -1,7 +0,0 @@
----
-description: "Execute Validation Journey and capture evidence"
-allowed-tools: ["Skill"]
-argument-hint: "<TICKET_ID> [PR_NUMBER]"
----
-
-Use the /lisa-expo:jira-journey skill to execute the Validation Journey and capture evidence. $ARGUMENTS

package/plugins/lisa-expo/commands/jira/verify.md

@@ -1,7 +0,0 @@
----
-description: "Verify JIRA ticket meets standards for epic relationships and description quality"
-allowed-tools: ["Skill"]
-argument-hint: "<TICKET-ID>"
----
-
-Use the /lisa-expo:jira-verify skill to verify the JIRA ticket meets organizational standards. $ARGUMENTS

package/plugins/lisa-rails/commands/jira/add-journey.md

@@ -1,7 +0,0 @@
----
-description: "Add Validation Journey section to existing ticket"
-allowed-tools: ["Skill"]
-argument-hint: "<TICKET_ID>"
----
-
-Use the /lisa-rails:jira-add-journey skill to add a Validation Journey section to the ticket. $ARGUMENTS

package/plugins/lisa-rails/commands/jira/create.md

@@ -1,7 +0,0 @@
----
-description: "Create JIRA epics/stories/tasks from code files with comprehensive quality requirements"
-allowed-tools: ["Skill"]
-argument-hint: "<file-or-directory-path> [project-key]"
----
-
-Use the /lisa-rails:jira-create skill to create JIRA issues from the provided input. $ARGUMENTS

package/plugins/lisa-rails/commands/jira/evidence.md

@@ -1,7 +0,0 @@
----
-description: "Post captured evidence to JIRA and GitHub PR"
-allowed-tools: ["Skill"]
-argument-hint: "<TICKET_ID> <EVIDENCE_DIR> <PR_NUMBER>"
----
-
-Use the /lisa-rails:jira-evidence skill to post captured evidence to JIRA and the GitHub PR. $ARGUMENTS

package/plugins/lisa-rails/commands/jira/journey.md

@@ -1,7 +0,0 @@
----
-description: "Execute Validation Journey and capture evidence"
-allowed-tools: ["Skill"]
-argument-hint: "<TICKET_ID> [PR_NUMBER]"
----
-
-Use the /lisa-rails:jira-journey skill to execute the Validation Journey and capture evidence. $ARGUMENTS

package/plugins/lisa-rails/commands/jira/verify.md

@@ -1,7 +0,0 @@
----
-description: "Verify JIRA ticket meets standards for epic relationships and description quality"
-allowed-tools: ["Skill"]
-argument-hint: "<TICKET-ID>"
----
-
-Use the /lisa-rails:jira-verify skill to verify the JIRA ticket meets organizational standards. $ARGUMENTS

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

@@ -1,12 +0,0 @@
----
-description: "Build a feature. Defines acceptance criteria, researches codebase, implements via TDD, verifies locally, and reviews."
-argument-hint: "<description-or-ticket-id-or-url>"
----
-
-Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Implement** flow with the **Build** work type.
-
-**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.
-
-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.
-
-$ARGUMENTS

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

@@ -1,12 +0,0 @@
----
-description: "Fix a bug. Reproduces, analyzes git history, finds root cause, implements fix via TDD, verifies locally, and reviews."
-argument-hint: "<description-or-ticket-id-or-url>"
----
-
-Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Implement** flow with the **Fix** work type.
-
-**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.
-
-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.
-
-$ARGUMENTS

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

@@ -1,18 +0,0 @@
----
-description: "Improve existing code. Measures baseline, implements improvements via TDD, measures again, and reviews."
-argument-hint: "<target-description>"
----
-
-Apply the `intent-routing` rule (loaded via the lisa plugin) and execute the **Implement** flow with the **Improve** work type.
-
-**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.
-
-For specific improvement types, you can also use:
-- `/lisa:plan:add-test-coverage` -- increase test coverage
-- `/lisa:plan:fix-linter-error` -- fix lint rule violations
-- `/lisa:plan:lower-code-complexity` -- reduce cognitive complexity
-- `/lisa:plan:reduce-max-lines` -- reduce file length
-- `/lisa:plan:reduce-max-lines-per-function` -- reduce function length
-- `/lisa:plan:improve-tests` -- improve test quality
-
-$ARGUMENTS

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

@@ -1,10 +0,0 @@
----
-description: "Investigate an issue. Analyzes git history, reproduces, traces execution, checks logs, and reports findings with evidence."
-argument-hint: "<description-or-ticket-id-or-url>"
----
-
-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.
-
-$ARGUMENTS

package/plugins/src/base/commands/jira/add-journey.md

@@ -1,7 +0,0 @@
----
-description: "Add Validation Journey section to existing ticket"
-allowed-tools: ["Skill"]
-argument-hint: "<TICKET_ID>"
----
-
-Use the /lisa:jira-add-journey skill to add a Validation Journey section to the ticket. $ARGUMENTS

package/plugins/src/base/commands/jira/build-intake.md

@@ -1,7 +0,0 @@
----
-description: "Run one JIRA build-intake cycle. Finds tickets in Status=Ready, claims each via In Progress, runs the implementation flow via jira-agent, and transitions to On Dev on completion. Symmetric counterpart to /notion-prd-intake."
-allowed-tools: ["Skill"]
-argument-hint: "<project key> | <full JQL filter>"
----
-
-Use the /lisa:jira-build-intake skill to scan for Ready JIRA tickets, claim them, run the build flow, and transition to On Dev. $ARGUMENTS

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

@@ -1,7 +0,0 @@
----
-description: "Create JIRA epics/stories/tasks from code files with comprehensive quality requirements"
-allowed-tools: ["Skill"]
-argument-hint: "<file-or-directory-path> [project-key]"
----
-
-Use the /lisa:jira-create skill to create JIRA issues from the provided input. $ARGUMENTS

package/plugins/src/base/commands/jira/evidence.md

@@ -1,7 +0,0 @@
----
-description: "Post captured evidence to JIRA and GitHub PR"
-allowed-tools: ["Skill"]
-argument-hint: "<TICKET_ID> <EVIDENCE_DIR> <PR_NUMBER>"
----
-
-Use the /lisa:jira-evidence skill to post captured evidence to JIRA and the GitHub PR. $ARGUMENTS

package/plugins/src/base/commands/jira/journey.md

@@ -1,7 +0,0 @@
----
-description: "Execute Validation Journey and capture evidence"
-allowed-tools: ["Skill"]
-argument-hint: "<TICKET_ID> [PR_NUMBER]"
----
-
-Use the /lisa:jira-journey skill to execute the Validation Journey and capture evidence. $ARGUMENTS

package/plugins/src/base/commands/jira/read-ticket.md

@@ -1,7 +0,0 @@
----
-description: "Read a JIRA ticket with full scope — metadata, comments, remote PRs, linked tickets, epic siblings, subtasks"
-allowed-tools: ["Skill"]
-argument-hint: "<TICKET-ID>"
----
-
-Use the /lisa:jira-read-ticket skill to fetch the full scope of the JIRA ticket and its related graph. $ARGUMENTS

package/plugins/src/base/commands/jira/source-artifacts.md

@@ -1,6 +0,0 @@
----
-description: "Load the canonical taxonomy and rules for handling source artifacts (Figma, Lovable, Loom, etc.) in JIRA tickets — domains, classification, source precedence, inheritance, and conflict handling."
-allowed-tools: ["Skill"]
----
-
-Use the /lisa:jira-source-artifacts skill to load the canonical taxonomy and rules for source artifact handling. $ARGUMENTS

package/plugins/src/base/commands/jira/sync.md

@@ -1,7 +0,0 @@
----
-description: "Sync plan progress to a linked JIRA ticket"
-allowed-tools: ["Skill"]
-argument-hint: "<ticket-id>"
----
-
-Use the /lisa:jira-sync skill to sync plan progress to the linked JIRA ticket. $ARGUMENTS

package/plugins/src/base/commands/jira/triage.md

@@ -1,7 +0,0 @@
----
-description: "Analytical triage of a JIRA ticket -- ambiguity detection, edge case analysis, verification methodology"
-allowed-tools: ["Skill"]
-argument-hint: "<TICKET-ID>"
----
-
-Use the /lisa:ticket-triage skill to run analytical triage on the JIRA ticket. $ARGUMENTS

package/plugins/src/base/commands/jira/validate-ticket.md

@@ -1,7 +0,0 @@
----
-description: "Validate a proposed JIRA ticket spec or an existing ticket against the organizational quality gates. Read-only, no writes."
-allowed-tools: ["Skill"]
-argument-hint: "<TICKET-ID> | <YAML spec block>"
----
-
-Use the /lisa:jira-validate-ticket skill to validate the ticket spec or existing ticket against organizational quality gates and return a structured PASS/FAIL report. $ARGUMENTS

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

@@ -1,7 +0,0 @@
----
-description: "Verify JIRA ticket meets standards for epic relationships and description quality"
-allowed-tools: ["Skill"]
-argument-hint: "<TICKET-ID>"
----
-
-Use the /lisa:jira-verify skill to verify the JIRA ticket meets organizational standards. $ARGUMENTS

package/plugins/src/base/commands/jira/write-ticket.md

@@ -1,7 +0,0 @@
----
-description: "Create or update a JIRA ticket with enforced relationships, Gherkin criteria, and metadata quality gates"
-allowed-tools: ["Skill"]
-argument-hint: "[TICKET-ID | <create-intent-description>]"
----
-
-Use the /lisa:jira-write-ticket skill to create or update the JIRA ticket with full relationship discovery and quality enforcement. $ARGUMENTS

package/plugins/src/base/commands/notion-prd-intake.md

@@ -1,7 +0,0 @@
----
-description: "Run one PRD intake cycle against a Notion PRD database. Finds Ready PRDs, validates each through the JIRA gate logic, then routes to Blocked (with clarifying comments) or Ticketed (with JIRA tickets created)."
-allowed-tools: ["Skill"]
-argument-hint: "<Notion database URL or ID>"
----
-
-Use the /lisa:notion-prd-intake skill to scan the given Notion PRD database for Ready PRDs, dry-run-validate each, and route to Blocked or Ticketed. $ARGUMENTS

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

@@ -1,8 +0,0 @@
----
-description: "Creates an implementation plan from a ticket URL, file path, or text description"
-argument-hint: "<ticket-url | @file-path | description>"
----
-
-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

@@ -1,6 +0,0 @@
----
-description: "Deploys an agent team to research, implement, review and deploy a plan"
-argument-hint: "<ticket-url | @file-path | description>"
----
-
-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/prd-ticket-coverage.md

@@ -1,7 +0,0 @@
----
-description: "Audit PRD-to-tickets coverage. Verifies every requirement in a Notion PRD is covered by at least one created JIRA ticket; flags gaps (silent drops) and scope creep. Read-only — no writes to JIRA or Notion."
-allowed-tools: ["Skill"]
-argument-hint: "<PRD URL> [tickets=KEY-1,KEY-2,...]"
----
-
-Use the /lisa:prd-ticket-coverage skill to audit coverage of the PRD against the listed (or auto-discovered) JIRA tickets and produce a coverage matrix + verdict. $ARGUMENTS

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

@@ -1,7 +0,0 @@
----
-description: "Compare project's Lisa-managed files against Lisa source templates and offer to upstream changes"
-allowed-tools: ["Skill"]
-argument-hint: "[lisa-dir]"
----
-
-Use the /lisa:lisa-review-implementation skill to compare project files against Lisa templates. $ARGUMENTS

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

@@ -1,10 +0,0 @@
----
-description: "Review code changes. Runs quality, security, performance, product, and test reviews in parallel, then consolidates findings."
-argument-hint: "[pr-link-or-branch]"
----
-
-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.
-
-$ARGUMENTS

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

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

package/plugins/src/base/commands/spec-conformance.md

@@ -1,7 +0,0 @@
----
-description: "Verify shipped work matches its spec — coverage matrix with scope-creep detection and verdict"
-allowed-tools: ["Skill"]
-argument-hint: "[plan-file | TICKET-KEY | issue-url]"
----
-
-Use the /lisa:spec-conformance skill to compare shipped work against its spec and produce a coverage matrix with verdict. $ARGUMENTS

package/plugins/src/expo/commands/jira/add-journey.md

@@ -1,7 +0,0 @@
----
-description: "Add Validation Journey section to existing ticket"
-allowed-tools: ["Skill"]
-argument-hint: "<TICKET_ID>"
----
-
-Use the /lisa-expo:jira-add-journey skill to add a Validation Journey section to the ticket. $ARGUMENTS

package/plugins/src/expo/commands/jira/create.md

@@ -1,7 +0,0 @@
----
-description: "Create JIRA epics/stories/tasks from code files with comprehensive quality requirements"
-allowed-tools: ["Skill"]
-argument-hint: "<file-or-directory-path> [project-key]"
----
-
-Use the /lisa-expo:jira-create skill to create JIRA issues from the provided input. $ARGUMENTS

package/plugins/src/expo/commands/jira/evidence.md

@@ -1,7 +0,0 @@
----
-description: "Post captured evidence to JIRA and GitHub PR"
-allowed-tools: ["Skill"]
-argument-hint: "<TICKET_ID> <EVIDENCE_DIR> <PR_NUMBER>"
----
-
-Use the /lisa-expo:jira-evidence skill to post captured evidence to JIRA and the GitHub PR. $ARGUMENTS

package/plugins/src/expo/commands/jira/journey.md

@@ -1,7 +0,0 @@
----
-description: "Execute Validation Journey and capture evidence"
-allowed-tools: ["Skill"]
-argument-hint: "<TICKET_ID> [PR_NUMBER]"
----
-
-Use the /lisa-expo:jira-journey skill to execute the Validation Journey and capture evidence. $ARGUMENTS

package/plugins/src/expo/commands/jira/verify.md

@@ -1,7 +0,0 @@
----
-description: "Verify JIRA ticket meets standards for epic relationships and description quality"
-allowed-tools: ["Skill"]
-argument-hint: "<TICKET-ID>"
----
-
-Use the /lisa-expo:jira-verify skill to verify the JIRA ticket meets organizational standards. $ARGUMENTS

package/plugins/src/rails/commands/jira/add-journey.md

@@ -1,7 +0,0 @@
----
-description: "Add Validation Journey section to existing ticket"
-allowed-tools: ["Skill"]
-argument-hint: "<TICKET_ID>"
----
-
-Use the /lisa-rails:jira-add-journey skill to add a Validation Journey section to the ticket. $ARGUMENTS

package/plugins/src/rails/commands/jira/create.md

@@ -1,7 +0,0 @@
----
-description: "Create JIRA epics/stories/tasks from code files with comprehensive quality requirements"
-allowed-tools: ["Skill"]
-argument-hint: "<file-or-directory-path> [project-key]"
----
-
-Use the /lisa-rails:jira-create skill to create JIRA issues from the provided input. $ARGUMENTS

package/plugins/src/rails/commands/jira/evidence.md

@@ -1,7 +0,0 @@
----
-description: "Post captured evidence to JIRA and GitHub PR"
-allowed-tools: ["Skill"]
-argument-hint: "<TICKET_ID> <EVIDENCE_DIR> <PR_NUMBER>"
----
-
-Use the /lisa-rails:jira-evidence skill to post captured evidence to JIRA and the GitHub PR. $ARGUMENTS

package/plugins/src/rails/commands/jira/journey.md

@@ -1,7 +0,0 @@
----
-description: "Execute Validation Journey and capture evidence"
-allowed-tools: ["Skill"]
-argument-hint: "<TICKET_ID> [PR_NUMBER]"
----
-
-Use the /lisa-rails:jira-journey skill to execute the Validation Journey and capture evidence. $ARGUMENTS

package/plugins/src/rails/commands/jira/verify.md

@@ -1,7 +0,0 @@
----
-description: "Verify JIRA ticket meets standards for epic relationships and description quality"
-allowed-tools: ["Skill"]
-argument-hint: "<TICKET-ID>"
----
-
-Use the /lisa-rails:jira-verify skill to verify the JIRA ticket meets organizational standards. $ARGUMENTS