@codyswann/lisa 2.91.3 → 2.92.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.
- package/README.md +8 -0
- package/package.json +1 -1
- package/plugins/lisa/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa/commands/doctor.md +1 -1
- package/plugins/lisa/commands/queue-status.md +13 -0
- package/plugins/lisa/commands/setup/github.md +1 -1
- package/plugins/lisa/skills/queue-status/SKILL.md +72 -0
- package/plugins/lisa/skills/queue-status/agents/openai.yaml +4 -0
- package/plugins/lisa-cdk/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-cdk/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-expo/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-expo/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-harper-fabric/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-harper-fabric/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-nestjs/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-nestjs/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-openclaw/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-openclaw/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-rails/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-rails/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-typescript/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-typescript/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-wiki/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-wiki/.codex-plugin/plugin.json +1 -1
- package/plugins/src/base/commands/doctor.md +1 -1
- package/plugins/src/base/commands/queue-status.md +13 -0
- package/plugins/src/base/commands/setup/github.md +1 -1
- package/plugins/src/base/skills/queue-status/SKILL.md +72 -0
package/README.md
CHANGED
|
@@ -82,6 +82,14 @@ Most users only ever call `/lisa:research`, `/lisa:plan`, and `/lisa:implement`.
|
|
|
82
82
|
|
|
83
83
|
PRD intake records generated work with native hierarchy where the source and tracker support it, and with a durable generated-work fallback everywhere else. The vendor matrix for GitHub, Linear, JIRA/Atlassian, Confluence, Notion, and cross-vendor queues lives in `plugins/src/base/rules/prd-lifecycle-rollup.md`.
|
|
84
84
|
|
|
85
|
+
### Optional GitHub Project Coordination
|
|
86
|
+
|
|
87
|
+
GitHub Projects are an optional coordination layer for GitHub-backed Lisa flows, not the lifecycle source of truth. Real GitHub Issues and Pull Requests still carry the durable labels, comments, hierarchy, dependencies, and review state; Project membership just gives you a cross-repo view over that work.
|
|
88
|
+
|
|
89
|
+
Use `/lisa:setup-github` to scaffold `github.projects.v2` in `.lisa.config.json`, then `/lisa:doctor` to verify namespace and access before operators rely on it. In v1, `github.projects.v2.owner.slug` must match `github.org`. `required: false` is the default best-effort mode: repository-local issue and PR writes still succeed if Project membership cannot be added. `required: true` upgrades the same failure into a blocking readiness error.
|
|
90
|
+
|
|
91
|
+
This does not relax Lisa's single-repo leaf rule. PRDs, Epics, Stories, and Spikes may coordinate work across repositories, but every build-ready Task, Bug, Sub-task, or Improvement must still target exactly one repository, carry exactly one `repo:<name>` marker, and be claimed only by that repository's intake lane.
|
|
92
|
+
|
|
85
93
|
### Maintenance and Operations
|
|
86
94
|
|
|
87
95
|
| Command | What it does |
|
package/package.json
CHANGED
|
@@ -82,7 +82,7 @@
|
|
|
82
82
|
"lodash": ">=4.18.1"
|
|
83
83
|
},
|
|
84
84
|
"name": "@codyswann/lisa",
|
|
85
|
-
"version": "2.
|
|
85
|
+
"version": "2.92.0",
|
|
86
86
|
"description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
|
|
87
87
|
"main": "dist/index.js",
|
|
88
88
|
"exports": {
|
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
---
|
|
2
|
-
description: "Audit whether the current repository is ready to use Lisa. Runs grouped read-only readiness checks for config, runtime surfaces, tracker/source access, automation prerequisites, and optional
|
|
2
|
+
description: "Audit whether the current repository is ready to use Lisa. Runs grouped read-only readiness checks for config, runtime surfaces, tracker/source access, automation prerequisites, and optional GitHub Project/wiki coordination, then reports PASS/WARN/FAIL/SKIP results plus an overall verdict."
|
|
3
3
|
argument-hint: "[--fix=false]"
|
|
4
4
|
---
|
|
5
5
|
|
|
@@ -0,0 +1,13 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: "Inspect the current project's PRD and build queues, summarize lifecycle counts, and surface actionable queue-health signals without mutating work."
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Use the /lisa:queue-status skill to inspect the current project's configured PRD source and build tracker, report queue-health verdicts, and highlight actionable backlog or stuck-state signals. $ARGUMENTS
|
|
6
|
+
|
|
7
|
+
Common operator usage:
|
|
8
|
+
|
|
9
|
+
- `/lisa:queue-status`
|
|
10
|
+
- `/lisa:queue-status queue=prd`
|
|
11
|
+
- `/lisa:queue-status queue=build`
|
|
12
|
+
|
|
13
|
+
This surface is read-only in v1. Use it to understand whether the repo's PRD and build queues are idle, healthy, attention-needed, or misconfigured before deciding whether to run `/lisa:intake`, `/lisa:repair-intake`, or deeper tracker-native investigation.
|
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
---
|
|
2
|
-
description: "Set up GitHub Issues as the tracker and/or PRD source for this project. Verifies the gh CLI, resolves org/repo, scaffolds the `status:*` (build) and/or `prd-*` (PRD) label namespaces, writes the `github` section of `.lisa.config.json`, and
|
|
2
|
+
description: "Set up GitHub Issues as the tracker and/or PRD source for this project. Verifies the gh CLI, resolves org/repo, scaffolds the `status:*` (build) and/or `prd-*` (PRD) label namespaces, writes the `github` section of `.lisa.config.json`, and can document optional GitHub ProjectV2 coordination before offering top-level `tracker: \"github\"` / `source: \"github\"`. No /lisa:setup:atlassian prerequisite."
|
|
3
3
|
allowed-tools: ["Skill"]
|
|
4
4
|
argument-hint: "[--repo=<org/repo>]"
|
|
5
5
|
---
|
|
@@ -0,0 +1,72 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: queue-status
|
|
3
|
+
description: "Read-only operator surface for the current project's PRD and build backlog health. Resolves the configured PRD source and build tracker from the same Lisa contract used by intake and repair, summarizes lifecycle-role counts, distinguishes idle queues from setup problems, and highlights actionable blocked, in-review, claimed, or shipped work."
|
|
4
|
+
allowed-tools: ["Skill", "Bash", "Read"]
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Queue Status: $ARGUMENTS
|
|
8
|
+
|
|
9
|
+
`/lisa:queue-status` is the operator-facing inspection surface for Lisa's live backlog state. It answers, for the **current repo only**, what Lisa's configured PRD queue and build queue currently look like, whether the queues appear healthy or stuck, and which items are most actionable next.
|
|
10
|
+
|
|
11
|
+
This command is **read-only** in v1. It does not create, claim, relabel, repair, transition, comment on, or otherwise mutate queue items. It complements `/lisa:intake`, `/lisa:repair-intake`, `/lisa:verify-prd`, `/lisa:automation-status`, and the underlying vendor trackers; it does not replace them.
|
|
12
|
+
|
|
13
|
+
## Confirmation policy
|
|
14
|
+
|
|
15
|
+
Do **not** ask for confirmation once invoked. This skill inspects queue state and reports what it finds. There are no write-side effects in the v1 surface.
|
|
16
|
+
|
|
17
|
+
## Scope
|
|
18
|
+
|
|
19
|
+
Inspect only the Lisa queues for the current project:
|
|
20
|
+
|
|
21
|
+
- the configured PRD source queue
|
|
22
|
+
- the configured build tracker queue
|
|
23
|
+
|
|
24
|
+
Resolve queue source, tracker, lifecycle roles, and queue arguments from the **same contract** Lisa already uses for `/lisa:intake` and `/lisa:repair-intake`. Do **not** invent a second source of truth for queue detection, lifecycle naming, or stack support.
|
|
25
|
+
|
|
26
|
+
Support a repo-scoped queue selector when requested:
|
|
27
|
+
|
|
28
|
+
- default: inspect both queues
|
|
29
|
+
- `queue=prd`: inspect only the PRD queue
|
|
30
|
+
- `queue=build`: inspect only the build queue
|
|
31
|
+
|
|
32
|
+
## What to report
|
|
33
|
+
|
|
34
|
+
For each inspected queue, report:
|
|
35
|
+
|
|
36
|
+
1. The queue source or tracker Lisa resolved.
|
|
37
|
+
2. Lifecycle counts using the repo's configured role names.
|
|
38
|
+
3. Whether the queue appears `IDLE`, `HEALTHY`, `ATTENTION_NEEDED`, or `MISCONFIGURED`.
|
|
39
|
+
4. Whether the lifecycle namespace appears adopted versus absent.
|
|
40
|
+
5. The oldest or most actionable blocked, in-review, claimed, shipped, or similar stuck items Lisa can surface without mutating work.
|
|
41
|
+
6. A concise remediation hint when attention is needed.
|
|
42
|
+
|
|
43
|
+
The report should stay terminal-first and immediately actionable: observable queue facts first, then the smallest useful next step.
|
|
44
|
+
|
|
45
|
+
## Runtime and vendor expectations
|
|
46
|
+
|
|
47
|
+
- Reuse the same config-resolution defaults and queue-routing rules that `intake` and `repair-intake` use.
|
|
48
|
+
- Work from the current repo's `.lisa.config.json` instead of hardcoding one vendor's lifecycle names.
|
|
49
|
+
- Support the vendor families already served by Lisa intake: GitHub, Linear, JIRA, Notion, and Confluence.
|
|
50
|
+
- If a queue cannot be resolved or its lifecycle namespace has not been adopted, report that explicitly as `MISCONFIGURED` rather than pretending the queue is empty.
|
|
51
|
+
|
|
52
|
+
## Verdicts and remediation
|
|
53
|
+
|
|
54
|
+
- `IDLE`: the queue resolved successfully and no actionable ready or stuck work is present.
|
|
55
|
+
- `HEALTHY`: the queue resolved successfully and the current backlog/state appears normal.
|
|
56
|
+
- `ATTENTION_NEEDED`: the queue resolved, but blocked, stalled, or accumulating work needs operator follow-up.
|
|
57
|
+
- `MISCONFIGURED`: Lisa could not resolve the queue, could not find the expected lifecycle namespace, or detected another setup/adoption problem.
|
|
58
|
+
|
|
59
|
+
Status-specific remediation guidance:
|
|
60
|
+
|
|
61
|
+
- `IDLE`: explain that the queue is currently quiet and no immediate operator action is required.
|
|
62
|
+
- `HEALTHY`: point operators to `/lisa:intake` or `/lisa:repair-intake` when they want Lisa to act on the reported state.
|
|
63
|
+
- `ATTENTION_NEEDED`: identify the most actionable blocked or stalled items and suggest the next Lisa or tracker-native command to investigate.
|
|
64
|
+
- `MISCONFIGURED`: show which queue contract is missing or unresolved and recommend fixing `.lisa.config.json`, adopting the lifecycle namespace, or rerunning the relevant setup flow.
|
|
65
|
+
|
|
66
|
+
## Rules
|
|
67
|
+
|
|
68
|
+
- Stay **read-only**. Never create, update, claim, relabel, repair, transition, or comment on queue items from this skill.
|
|
69
|
+
- Keep the report repo-scoped to the current project instead of aggregating unrelated repos or teams.
|
|
70
|
+
- Distinguish truly idle queues from lifecycle-namespace absence or unresolved config.
|
|
71
|
+
- Reuse `intake` and `repair-intake` contract semantics so queue health reporting does not drift from execution behavior.
|
|
72
|
+
- Keep observable queue facts separate from remediation guidance so operators can tell the current state from the recommended next step.
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "lisa-openclaw",
|
|
3
|
-
"version": "2.
|
|
3
|
+
"version": "2.92.0",
|
|
4
4
|
"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",
|
|
5
5
|
"author": {
|
|
6
6
|
"name": "Cody Swann"
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "lisa-openclaw",
|
|
3
|
-
"version": "2.
|
|
3
|
+
"version": "2.92.0",
|
|
4
4
|
"description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, across Claude and Codex.",
|
|
5
5
|
"author": {
|
|
6
6
|
"name": "Cody Swann"
|
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
---
|
|
2
|
-
description: "Audit whether the current repository is ready to use Lisa. Runs grouped read-only readiness checks for config, runtime surfaces, tracker/source access, automation prerequisites, and optional
|
|
2
|
+
description: "Audit whether the current repository is ready to use Lisa. Runs grouped read-only readiness checks for config, runtime surfaces, tracker/source access, automation prerequisites, and optional GitHub Project/wiki coordination, then reports PASS/WARN/FAIL/SKIP results plus an overall verdict."
|
|
3
3
|
argument-hint: "[--fix=false]"
|
|
4
4
|
---
|
|
5
5
|
|
|
@@ -0,0 +1,13 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: "Inspect the current project's PRD and build queues, summarize lifecycle counts, and surface actionable queue-health signals without mutating work."
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Use the /lisa:queue-status skill to inspect the current project's configured PRD source and build tracker, report queue-health verdicts, and highlight actionable backlog or stuck-state signals. $ARGUMENTS
|
|
6
|
+
|
|
7
|
+
Common operator usage:
|
|
8
|
+
|
|
9
|
+
- `/lisa:queue-status`
|
|
10
|
+
- `/lisa:queue-status queue=prd`
|
|
11
|
+
- `/lisa:queue-status queue=build`
|
|
12
|
+
|
|
13
|
+
This surface is read-only in v1. Use it to understand whether the repo's PRD and build queues are idle, healthy, attention-needed, or misconfigured before deciding whether to run `/lisa:intake`, `/lisa:repair-intake`, or deeper tracker-native investigation.
|
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
---
|
|
2
|
-
description: "Set up GitHub Issues as the tracker and/or PRD source for this project. Verifies the gh CLI, resolves org/repo, scaffolds the `status:*` (build) and/or `prd-*` (PRD) label namespaces, writes the `github` section of `.lisa.config.json`, and
|
|
2
|
+
description: "Set up GitHub Issues as the tracker and/or PRD source for this project. Verifies the gh CLI, resolves org/repo, scaffolds the `status:*` (build) and/or `prd-*` (PRD) label namespaces, writes the `github` section of `.lisa.config.json`, and can document optional GitHub ProjectV2 coordination before offering top-level `tracker: \"github\"` / `source: \"github\"`. No /lisa:setup:atlassian prerequisite."
|
|
3
3
|
allowed-tools: ["Skill"]
|
|
4
4
|
argument-hint: "[--repo=<org/repo>]"
|
|
5
5
|
---
|
|
@@ -0,0 +1,72 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: queue-status
|
|
3
|
+
description: "Read-only operator surface for the current project's PRD and build backlog health. Resolves the configured PRD source and build tracker from the same Lisa contract used by intake and repair, summarizes lifecycle-role counts, distinguishes idle queues from setup problems, and highlights actionable blocked, in-review, claimed, or shipped work."
|
|
4
|
+
allowed-tools: ["Skill", "Bash", "Read"]
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Queue Status: $ARGUMENTS
|
|
8
|
+
|
|
9
|
+
`/lisa:queue-status` is the operator-facing inspection surface for Lisa's live backlog state. It answers, for the **current repo only**, what Lisa's configured PRD queue and build queue currently look like, whether the queues appear healthy or stuck, and which items are most actionable next.
|
|
10
|
+
|
|
11
|
+
This command is **read-only** in v1. It does not create, claim, relabel, repair, transition, comment on, or otherwise mutate queue items. It complements `/lisa:intake`, `/lisa:repair-intake`, `/lisa:verify-prd`, `/lisa:automation-status`, and the underlying vendor trackers; it does not replace them.
|
|
12
|
+
|
|
13
|
+
## Confirmation policy
|
|
14
|
+
|
|
15
|
+
Do **not** ask for confirmation once invoked. This skill inspects queue state and reports what it finds. There are no write-side effects in the v1 surface.
|
|
16
|
+
|
|
17
|
+
## Scope
|
|
18
|
+
|
|
19
|
+
Inspect only the Lisa queues for the current project:
|
|
20
|
+
|
|
21
|
+
- the configured PRD source queue
|
|
22
|
+
- the configured build tracker queue
|
|
23
|
+
|
|
24
|
+
Resolve queue source, tracker, lifecycle roles, and queue arguments from the **same contract** Lisa already uses for `/lisa:intake` and `/lisa:repair-intake`. Do **not** invent a second source of truth for queue detection, lifecycle naming, or stack support.
|
|
25
|
+
|
|
26
|
+
Support a repo-scoped queue selector when requested:
|
|
27
|
+
|
|
28
|
+
- default: inspect both queues
|
|
29
|
+
- `queue=prd`: inspect only the PRD queue
|
|
30
|
+
- `queue=build`: inspect only the build queue
|
|
31
|
+
|
|
32
|
+
## What to report
|
|
33
|
+
|
|
34
|
+
For each inspected queue, report:
|
|
35
|
+
|
|
36
|
+
1. The queue source or tracker Lisa resolved.
|
|
37
|
+
2. Lifecycle counts using the repo's configured role names.
|
|
38
|
+
3. Whether the queue appears `IDLE`, `HEALTHY`, `ATTENTION_NEEDED`, or `MISCONFIGURED`.
|
|
39
|
+
4. Whether the lifecycle namespace appears adopted versus absent.
|
|
40
|
+
5. The oldest or most actionable blocked, in-review, claimed, shipped, or similar stuck items Lisa can surface without mutating work.
|
|
41
|
+
6. A concise remediation hint when attention is needed.
|
|
42
|
+
|
|
43
|
+
The report should stay terminal-first and immediately actionable: observable queue facts first, then the smallest useful next step.
|
|
44
|
+
|
|
45
|
+
## Runtime and vendor expectations
|
|
46
|
+
|
|
47
|
+
- Reuse the same config-resolution defaults and queue-routing rules that `intake` and `repair-intake` use.
|
|
48
|
+
- Work from the current repo's `.lisa.config.json` instead of hardcoding one vendor's lifecycle names.
|
|
49
|
+
- Support the vendor families already served by Lisa intake: GitHub, Linear, JIRA, Notion, and Confluence.
|
|
50
|
+
- If a queue cannot be resolved or its lifecycle namespace has not been adopted, report that explicitly as `MISCONFIGURED` rather than pretending the queue is empty.
|
|
51
|
+
|
|
52
|
+
## Verdicts and remediation
|
|
53
|
+
|
|
54
|
+
- `IDLE`: the queue resolved successfully and no actionable ready or stuck work is present.
|
|
55
|
+
- `HEALTHY`: the queue resolved successfully and the current backlog/state appears normal.
|
|
56
|
+
- `ATTENTION_NEEDED`: the queue resolved, but blocked, stalled, or accumulating work needs operator follow-up.
|
|
57
|
+
- `MISCONFIGURED`: Lisa could not resolve the queue, could not find the expected lifecycle namespace, or detected another setup/adoption problem.
|
|
58
|
+
|
|
59
|
+
Status-specific remediation guidance:
|
|
60
|
+
|
|
61
|
+
- `IDLE`: explain that the queue is currently quiet and no immediate operator action is required.
|
|
62
|
+
- `HEALTHY`: point operators to `/lisa:intake` or `/lisa:repair-intake` when they want Lisa to act on the reported state.
|
|
63
|
+
- `ATTENTION_NEEDED`: identify the most actionable blocked or stalled items and suggest the next Lisa or tracker-native command to investigate.
|
|
64
|
+
- `MISCONFIGURED`: show which queue contract is missing or unresolved and recommend fixing `.lisa.config.json`, adopting the lifecycle namespace, or rerunning the relevant setup flow.
|
|
65
|
+
|
|
66
|
+
## Rules
|
|
67
|
+
|
|
68
|
+
- Stay **read-only**. Never create, update, claim, relabel, repair, transition, or comment on queue items from this skill.
|
|
69
|
+
- Keep the report repo-scoped to the current project instead of aggregating unrelated repos or teams.
|
|
70
|
+
- Distinguish truly idle queues from lifecycle-namespace absence or unresolved config.
|
|
71
|
+
- Reuse `intake` and `repair-intake` contract semantics so queue health reporting does not drift from execution behavior.
|
|
72
|
+
- Keep observable queue facts separate from remediation guidance so operators can tell the current state from the recommended next step.
|