@codyswann/lisa 2.92.0 → 2.93.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/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/skills/queue-status/SKILL.md +23 -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/skills/queue-status/SKILL.md +23 -0
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.93.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": {
|
|
@@ -31,6 +31,12 @@ Support a repo-scoped queue selector when requested:
|
|
|
31
31
|
|
|
32
32
|
## What to report
|
|
33
33
|
|
|
34
|
+
Render the report in **grouped sections** so operators can scan it top-down without reading raw tracker dumps:
|
|
35
|
+
|
|
36
|
+
1. An optional overall queue-health summary when inspecting both queues.
|
|
37
|
+
2. One PRD queue section when the PRD queue is in scope.
|
|
38
|
+
3. One build queue section when the build queue is in scope.
|
|
39
|
+
|
|
34
40
|
For each inspected queue, report:
|
|
35
41
|
|
|
36
42
|
1. The queue source or tracker Lisa resolved.
|
|
@@ -42,6 +48,16 @@ For each inspected queue, report:
|
|
|
42
48
|
|
|
43
49
|
The report should stay terminal-first and immediately actionable: observable queue facts first, then the smallest useful next step.
|
|
44
50
|
|
|
51
|
+
## Output shape
|
|
52
|
+
|
|
53
|
+
Use a stable terminal-friendly shape:
|
|
54
|
+
|
|
55
|
+
1. `Overall verdict` line when both queues are shown.
|
|
56
|
+
2. `PRD queue` heading with resolved source, verdict, lifecycle counts, actionable highlights, and remediation.
|
|
57
|
+
3. `Build queue` heading with resolved tracker, verdict, lifecycle counts, actionable highlights, and remediation.
|
|
58
|
+
|
|
59
|
+
Queue sections should stay visually grouped. Do not interleave PRD and build facts item-by-item.
|
|
60
|
+
|
|
45
61
|
## Runtime and vendor expectations
|
|
46
62
|
|
|
47
63
|
- Reuse the same config-resolution defaults and queue-routing rules that `intake` and `repair-intake` use.
|
|
@@ -56,6 +72,13 @@ The report should stay terminal-first and immediately actionable: observable que
|
|
|
56
72
|
- `ATTENTION_NEEDED`: the queue resolved, but blocked, stalled, or accumulating work needs operator follow-up.
|
|
57
73
|
- `MISCONFIGURED`: Lisa could not resolve the queue, could not find the expected lifecycle namespace, or detected another setup/adoption problem.
|
|
58
74
|
|
|
75
|
+
When both queues are in scope, derive the **overall verdict** from the queue sections:
|
|
76
|
+
|
|
77
|
+
- `MISCONFIGURED` if any inspected queue is misconfigured.
|
|
78
|
+
- Otherwise `ATTENTION_NEEDED` if any inspected queue needs operator follow-up.
|
|
79
|
+
- Otherwise `HEALTHY` if any inspected queue has normal actionable work in motion.
|
|
80
|
+
- Otherwise `IDLE`.
|
|
81
|
+
|
|
59
82
|
Status-specific remediation guidance:
|
|
60
83
|
|
|
61
84
|
- `IDLE`: explain that the queue is currently quiet and no immediate operator action is required.
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "lisa-openclaw",
|
|
3
|
-
"version": "2.
|
|
3
|
+
"version": "2.93.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.93.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"
|
|
@@ -31,6 +31,12 @@ Support a repo-scoped queue selector when requested:
|
|
|
31
31
|
|
|
32
32
|
## What to report
|
|
33
33
|
|
|
34
|
+
Render the report in **grouped sections** so operators can scan it top-down without reading raw tracker dumps:
|
|
35
|
+
|
|
36
|
+
1. An optional overall queue-health summary when inspecting both queues.
|
|
37
|
+
2. One PRD queue section when the PRD queue is in scope.
|
|
38
|
+
3. One build queue section when the build queue is in scope.
|
|
39
|
+
|
|
34
40
|
For each inspected queue, report:
|
|
35
41
|
|
|
36
42
|
1. The queue source or tracker Lisa resolved.
|
|
@@ -42,6 +48,16 @@ For each inspected queue, report:
|
|
|
42
48
|
|
|
43
49
|
The report should stay terminal-first and immediately actionable: observable queue facts first, then the smallest useful next step.
|
|
44
50
|
|
|
51
|
+
## Output shape
|
|
52
|
+
|
|
53
|
+
Use a stable terminal-friendly shape:
|
|
54
|
+
|
|
55
|
+
1. `Overall verdict` line when both queues are shown.
|
|
56
|
+
2. `PRD queue` heading with resolved source, verdict, lifecycle counts, actionable highlights, and remediation.
|
|
57
|
+
3. `Build queue` heading with resolved tracker, verdict, lifecycle counts, actionable highlights, and remediation.
|
|
58
|
+
|
|
59
|
+
Queue sections should stay visually grouped. Do not interleave PRD and build facts item-by-item.
|
|
60
|
+
|
|
45
61
|
## Runtime and vendor expectations
|
|
46
62
|
|
|
47
63
|
- Reuse the same config-resolution defaults and queue-routing rules that `intake` and `repair-intake` use.
|
|
@@ -56,6 +72,13 @@ The report should stay terminal-first and immediately actionable: observable que
|
|
|
56
72
|
- `ATTENTION_NEEDED`: the queue resolved, but blocked, stalled, or accumulating work needs operator follow-up.
|
|
57
73
|
- `MISCONFIGURED`: Lisa could not resolve the queue, could not find the expected lifecycle namespace, or detected another setup/adoption problem.
|
|
58
74
|
|
|
75
|
+
When both queues are in scope, derive the **overall verdict** from the queue sections:
|
|
76
|
+
|
|
77
|
+
- `MISCONFIGURED` if any inspected queue is misconfigured.
|
|
78
|
+
- Otherwise `ATTENTION_NEEDED` if any inspected queue needs operator follow-up.
|
|
79
|
+
- Otherwise `HEALTHY` if any inspected queue has normal actionable work in motion.
|
|
80
|
+
- Otherwise `IDLE`.
|
|
81
|
+
|
|
59
82
|
Status-specific remediation guidance:
|
|
60
83
|
|
|
61
84
|
- `IDLE`: explain that the queue is currently quiet and no immediate operator action is required.
|