@codyswann/lisa 1.33.0 → 1.33.1
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.
|
@@ -40,23 +40,26 @@ Evaluate the scope of work:
|
|
|
40
40
|
|
|
41
41
|
## Step 4: Phase 1 - Research (parallel)
|
|
42
42
|
|
|
43
|
-
Create an Agent Team and spawn three research teammates simultaneously
|
|
43
|
+
Create an Agent Team and spawn three research teammates simultaneously. **All agents spawned in Steps 4–7 must include the `team_name` parameter from the TeamCreate call.**
|
|
44
44
|
|
|
45
45
|
#### Researcher
|
|
46
46
|
- **Name**: `researcher`
|
|
47
47
|
- **Agent type**: `general-purpose`
|
|
48
48
|
- **Mode**: `bypassPermissions`
|
|
49
|
+
- **Team**: use the `team_name` from TeamCreate
|
|
49
50
|
- **Prompt**: Research the input (ticket, file, or description). If a ticket URL, fetch full details via JIRA MCP or GitHub CLI. If a bug, attempt to reproduce it empirically (Playwright, browser, direct API call, etc.). Extract requirements, acceptance criteria, and context.
|
|
50
51
|
|
|
51
52
|
#### Codebase Explorer
|
|
52
53
|
- **Name**: `explorer`
|
|
53
54
|
- **Agent type**: `Explore`
|
|
55
|
+
- **Team**: use the `team_name` from TeamCreate
|
|
54
56
|
- **Prompt**: Explore the codebase for relevant code, existing patterns, and reusable scripts. Read lint and format rules to understand project standards. Identify files that would need modification, existing utilities that can be reused, and architecture constraints. Check for existing scripts in `package.json` that could be used for replication or verification.
|
|
55
57
|
|
|
56
58
|
#### Spec Gap Analyst
|
|
57
59
|
- **Name**: `spec-analyst`
|
|
58
60
|
- **Agent type**: `spec-analyst`
|
|
59
61
|
- **Mode**: `bypassPermissions`
|
|
62
|
+
- **Team**: use the `team_name` from TeamCreate
|
|
60
63
|
- **Prompt**: Analyze the input for specification gaps. Read `package.json` and existing code for project context. Identify every ambiguity or unstated assumption that could lead to wrong architectural decisions. Report as a numbered list of clarifying questions, sorted by impact.
|
|
61
64
|
|
|
62
65
|
Wait for all three to report back via SendMessage.
|
|
@@ -89,24 +92,28 @@ Spawn four domain planners simultaneously, passing each the Research Brief:
|
|
|
89
92
|
- **Name**: `arch-planner`
|
|
90
93
|
- **Agent type**: `architecture-planner`
|
|
91
94
|
- **Mode**: `bypassPermissions`
|
|
95
|
+
- **Team**: use the `team_name` from TeamCreate
|
|
92
96
|
- **Prompt**: [Research Brief] + Design the technical implementation approach. Identify files to create/modify, map dependencies, recommend patterns, flag risks.
|
|
93
97
|
|
|
94
98
|
#### Test Strategist
|
|
95
99
|
- **Name**: `test-strategist`
|
|
96
100
|
- **Agent type**: `test-strategist`
|
|
97
101
|
- **Mode**: `bypassPermissions`
|
|
102
|
+
- **Team**: use the `team_name` from TeamCreate
|
|
98
103
|
- **Prompt**: [Research Brief] + Design the test matrix. Identify edge cases, set coverage targets, define verification commands, plan TDD sequence.
|
|
99
104
|
|
|
100
105
|
#### Security Planner
|
|
101
106
|
- **Name**: `security-planner`
|
|
102
107
|
- **Agent type**: `security-planner`
|
|
103
108
|
- **Mode**: `bypassPermissions`
|
|
109
|
+
- **Team**: use the `team_name` from TeamCreate
|
|
104
110
|
- **Prompt**: [Research Brief] + Perform lightweight threat modeling (STRIDE). Identify auth/validation gaps, secrets exposure risks, and security measures needed.
|
|
105
111
|
|
|
106
112
|
#### Product Planner
|
|
107
113
|
- **Name**: `product-planner`
|
|
108
114
|
- **Agent type**: `product-planner`
|
|
109
115
|
- **Mode**: `bypassPermissions`
|
|
116
|
+
- **Team**: use the `team_name` from TeamCreate
|
|
110
117
|
- **Prompt**: [Research Brief] + Define user flows in Gherkin. Write acceptance criteria from user perspective. Identify UX concerns and error states.
|
|
111
118
|
|
|
112
119
|
Wait for all four to report back via SendMessage.
|
|
@@ -119,12 +126,14 @@ Spawn two reviewers simultaneously, passing them all sub-plans:
|
|
|
119
126
|
- **Name**: `devils-advocate`
|
|
120
127
|
- **Agent type**: `general-purpose`
|
|
121
128
|
- **Mode**: `bypassPermissions`
|
|
129
|
+
- **Team**: use the `team_name` from TeamCreate
|
|
122
130
|
- **Prompt**: [All sub-plans] + Review critically. Identify anti-patterns, N+1 queries, missing edge cases, security concerns, and performance issues. Do not assume anti-patterns are acceptable just because they exist in the codebase — undocumented anti-patterns should be flagged, not used as reference. Challenge assumptions and propose alternatives for weak points.
|
|
123
131
|
|
|
124
132
|
#### Consistency Checker
|
|
125
133
|
- **Name**: `consistency-checker`
|
|
126
134
|
- **Agent type**: `consistency-checker`
|
|
127
135
|
- **Mode**: `bypassPermissions`
|
|
136
|
+
- **Team**: use the `team_name` from TeamCreate
|
|
128
137
|
- **Prompt**: [All sub-plans] + Verify cross-plan consistency. Check that file lists align, test strategy covers architecture changes, security measures are reflected in acceptance criteria, and no sub-plans contradict each other.
|
|
129
138
|
|
|
130
139
|
Wait for both to report back via SendMessage.
|
package/package.json
CHANGED
|
@@ -88,7 +88,7 @@
|
|
|
88
88
|
"@isaacs/brace-expansion": "^5.0.1"
|
|
89
89
|
},
|
|
90
90
|
"name": "@codyswann/lisa",
|
|
91
|
-
"version": "1.33.
|
|
91
|
+
"version": "1.33.1",
|
|
92
92
|
"description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
|
|
93
93
|
"main": "dist/index.js",
|
|
94
94
|
"bin": {
|