specweave 1.0.521 → 1.0.522
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/.claude-plugin/README.md +1 -1
- package/CLAUDE.md +1 -1
- package/README.md +1 -1
- package/bin/specweave.js +7 -7
- package/dist/src/adapters/codex/README.md +1 -1
- package/dist/src/adapters/gemini/README.md +1 -1
- package/dist/src/cli/commands/complete.d.ts +10 -7
- package/dist/src/cli/commands/complete.d.ts.map +1 -1
- package/dist/src/cli/commands/complete.js +60 -14
- package/dist/src/cli/commands/complete.js.map +1 -1
- package/dist/src/cli/commands/evaluate-completion.d.ts.map +1 -1
- package/dist/src/cli/commands/evaluate-completion.js +8 -38
- package/dist/src/cli/commands/evaluate-completion.js.map +1 -1
- package/dist/src/cli/helpers/init/claude-settings-lsp.js +1 -1
- package/dist/src/cli/helpers/init/claude-settings-lsp.js.map +1 -1
- package/dist/src/core/increment/completion-validator.d.ts.map +1 -1
- package/dist/src/core/increment/completion-validator.js +2 -3
- package/dist/src/core/increment/completion-validator.js.map +1 -1
- package/dist/src/core/increment/increment-utils.d.ts +7 -7
- package/dist/src/core/increment/increment-utils.d.ts.map +1 -1
- package/dist/src/core/increment/increment-utils.js +19 -13
- package/dist/src/core/increment/increment-utils.js.map +1 -1
- package/dist/src/core/repo-structure/setup-summary.js +1 -1
- package/dist/src/core/repo-structure/setup-summary.js.map +1 -1
- package/dist/src/dashboard/server/dashboard-server.js +1 -1
- package/dist/src/dashboard/server/dashboard-server.js.map +1 -1
- package/dist/src/locales/de/cli.json +1 -1
- package/dist/src/locales/en/cli.json +1 -1
- package/dist/src/locales/es/cli.json +1 -1
- package/dist/src/locales/fr/cli.json +1 -1
- package/dist/src/locales/ja/cli.json +1 -1
- package/dist/src/locales/ko/cli.json +1 -1
- package/dist/src/locales/pt/cli.json +1 -1
- package/dist/src/locales/ru/cli.json +1 -1
- package/dist/src/locales/zh/cli.json +1 -1
- package/dist/src/utils/resolve-increment-id.d.ts +24 -0
- package/dist/src/utils/resolve-increment-id.d.ts.map +1 -0
- package/dist/src/utils/resolve-increment-id.js +53 -0
- package/dist/src/utils/resolve-increment-id.js.map +1 -0
- package/package.json +1 -1
- package/plugins/specweave/.claude-plugin/plugin.json +2 -2
- package/plugins/specweave/commands/import-external.md +4 -4
- package/plugins/specweave/skills/team-lead/SKILL.md +68 -4
- package/scripts/check-node-version.js +1 -1
- package/src/templates/lsp-plugin/plugin.json +1 -1
|
@@ -451,10 +451,10 @@ No tasks defined.
|
|
|
451
451
|
## See Also
|
|
452
452
|
|
|
453
453
|
- `specweave init` - Initial project setup with external tool import
|
|
454
|
-
- [External Import Guide](https://
|
|
455
|
-
- [GitHub Integration](https://
|
|
456
|
-
- [JIRA Integration](https://
|
|
457
|
-
- [Azure DevOps Integration](https://
|
|
454
|
+
- [External Import Guide](https://spec-weave.com/docs/guides/external-import)
|
|
455
|
+
- [GitHub Integration](https://spec-weave.com/docs/integrations/github)
|
|
456
|
+
- [JIRA Integration](https://spec-weave.com/docs/integrations/jira)
|
|
457
|
+
- [Azure DevOps Integration](https://spec-weave.com/docs/integrations/ado)
|
|
458
458
|
|
|
459
459
|
---
|
|
460
460
|
|
|
@@ -111,7 +111,30 @@ Skip increment pre-flight entirely. Brainstorm doesn't need a spec — it explor
|
|
|
111
111
|
1. Create team: `TeamCreate({ team_name: "brainstorm-{slug}", description: "Brainstorm: {topic}" })`
|
|
112
112
|
2. Read agent templates from `agents/brainstorm-advocate.md`, `agents/brainstorm-critic.md`, `agents/brainstorm-pragmatist.md`
|
|
113
113
|
3. Replace `[BRAINSTORM_QUESTION]` with the user's question/topic
|
|
114
|
-
4. Spawn all 3 agents in parallel
|
|
114
|
+
4. Spawn all 3 agents in parallel — each call MUST include `team_name` so agents join the team (and get tmux panes):
|
|
115
|
+
```
|
|
116
|
+
Task({
|
|
117
|
+
team_name: "brainstorm-{slug}",
|
|
118
|
+
name: "brainstorm-advocate",
|
|
119
|
+
subagent_type: "general-purpose",
|
|
120
|
+
mode: "bypassPermissions",
|
|
121
|
+
prompt: <replaced brainstorm-advocate.md content>
|
|
122
|
+
})
|
|
123
|
+
Task({
|
|
124
|
+
team_name: "brainstorm-{slug}",
|
|
125
|
+
name: "brainstorm-critic",
|
|
126
|
+
subagent_type: "general-purpose",
|
|
127
|
+
mode: "bypassPermissions",
|
|
128
|
+
prompt: <replaced brainstorm-critic.md content>
|
|
129
|
+
})
|
|
130
|
+
Task({
|
|
131
|
+
team_name: "brainstorm-{slug}",
|
|
132
|
+
name: "brainstorm-pragmatist",
|
|
133
|
+
subagent_type: "general-purpose",
|
|
134
|
+
mode: "bypassPermissions",
|
|
135
|
+
prompt: <replaced brainstorm-pragmatist.md content>
|
|
136
|
+
})
|
|
137
|
+
```
|
|
115
138
|
5. **PASSIVE WAIT (CRITICAL)**: Do NOT apply §8b stuck detection to brainstorm agents.
|
|
116
139
|
Brainstorm agents send `STATUS:` heartbeats (not task-granularity `T-{N}/{total}`).
|
|
117
140
|
Wait patiently for `PERSPECTIVE_COMPLETE:` messages — expected 2-5 minutes per agent.
|
|
@@ -144,7 +167,23 @@ Planning mode runs PM and Architect agents in parallel for richer, faster spec c
|
|
|
144
167
|
2. **Spawn PM + Architect in parallel** (TRUE parallelism):
|
|
145
168
|
- Read `agents/pm.md`, replace `[INCREMENT_ID]`, `[MASTER_INCREMENT_PATH]`, `[FEATURE_DESCRIPTION]`
|
|
146
169
|
- Read `agents/architect.md`, replace `[INCREMENT_ID]`, `[MASTER_INCREMENT_PATH]`
|
|
147
|
-
- **Spawn BOTH
|
|
170
|
+
- **Spawn BOTH in a single step — each call MUST include `team_name`:**
|
|
171
|
+
```
|
|
172
|
+
Task({
|
|
173
|
+
team_name: "plan-{feature-slug}",
|
|
174
|
+
name: "pm-agent",
|
|
175
|
+
subagent_type: "general-purpose",
|
|
176
|
+
mode: "bypassPermissions",
|
|
177
|
+
prompt: <replaced pm.md content>
|
|
178
|
+
})
|
|
179
|
+
Task({
|
|
180
|
+
team_name: "plan-{feature-slug}",
|
|
181
|
+
name: "architect-agent",
|
|
182
|
+
subagent_type: "general-purpose",
|
|
183
|
+
mode: "bypassPermissions",
|
|
184
|
+
prompt: <replaced architect.md content>
|
|
185
|
+
})
|
|
186
|
+
```
|
|
148
187
|
- PM writes spec.md with user stories and ACs
|
|
149
188
|
- Architect starts codebase exploration immediately (does NOT need spec.md for this)
|
|
150
189
|
- Architect polls for spec.md, reads it when PM finishes, then designs architecture
|
|
@@ -196,7 +235,16 @@ Skip increment pre-flight. Research is exploratory — no spec needed.
|
|
|
196
235
|
- Multi-faceted topic: spawn 2-3 researchers with different scopes
|
|
197
236
|
(e.g., "research auth" → one agent on OAuth providers, one on session management, one on security best practices)
|
|
198
237
|
3. Replace `[RESEARCH_TOPIC]` and `[RESEARCH_SCOPE]` in each agent prompt
|
|
199
|
-
4. Spawn all researchers in parallel
|
|
238
|
+
4. Spawn all researchers in parallel — each call MUST include `team_name`:
|
|
239
|
+
```
|
|
240
|
+
Task({
|
|
241
|
+
team_name: "research-{slug}",
|
|
242
|
+
name: "researcher-{scope}",
|
|
243
|
+
subagent_type: "general-purpose",
|
|
244
|
+
mode: "bypassPermissions",
|
|
245
|
+
prompt: <replaced researcher.md content>
|
|
246
|
+
})
|
|
247
|
+
```
|
|
200
248
|
5. Collect `RESEARCH_COMPLETE:` messages
|
|
201
249
|
6. Merge findings into a unified research report:
|
|
202
250
|
- Cross-reference findings between agents
|
|
@@ -223,7 +271,23 @@ Testing mode requires an increment (it needs to know WHAT to test).
|
|
|
223
271
|
- **Unit test agent**: read `agents/testing.md`, override scope to unit tests only
|
|
224
272
|
- **E2E test agent**: read `agents/testing.md`, override scope to E2E tests only
|
|
225
273
|
- Split scope via the agent prompt, not via separate templates
|
|
226
|
-
4. Spawn both in parallel
|
|
274
|
+
4. Spawn both in parallel — each call MUST include `team_name`:
|
|
275
|
+
```
|
|
276
|
+
Task({
|
|
277
|
+
team_name: "test-{id}",
|
|
278
|
+
name: "unit-test-agent",
|
|
279
|
+
subagent_type: "general-purpose",
|
|
280
|
+
mode: "bypassPermissions",
|
|
281
|
+
prompt: <replaced testing.md content with unit-test scope>
|
|
282
|
+
})
|
|
283
|
+
Task({
|
|
284
|
+
team_name: "test-{id}",
|
|
285
|
+
name: "e2e-test-agent",
|
|
286
|
+
subagent_type: "general-purpose",
|
|
287
|
+
mode: "bypassPermissions",
|
|
288
|
+
prompt: <replaced testing.md content with e2e scope>
|
|
289
|
+
})
|
|
290
|
+
```
|
|
227
291
|
5. Collect `COMPLETION:` messages
|
|
228
292
|
6. Run test suites to verify: `npx vitest run` + `npx playwright test`
|
|
229
293
|
7. Report results: pass/fail counts, coverage, uncovered ACs
|
|
@@ -116,7 +116,7 @@ if (!isVersionSatisfied(CURRENT_NODE_VERSION, MIN_NODE_VERSION)) {
|
|
|
116
116
|
console.error(getUpgradeInstructions());
|
|
117
117
|
console.error('');
|
|
118
118
|
console.error(`${BOLD}Full guide:${RESET}`);
|
|
119
|
-
console.error(` ${CYAN}${UNDERLINE}https://
|
|
119
|
+
console.error(` ${CYAN}${UNDERLINE}https://spec-weave.com/docs/guides/troubleshooting/common-errors#node-version-error${RESET}`);
|
|
120
120
|
console.error('');
|
|
121
121
|
console.error(`${DIM}After upgrading, run: npm install -g specweave${RESET}`);
|
|
122
122
|
console.error('');
|
|
@@ -4,7 +4,7 @@
|
|
|
4
4
|
"description": "Auto-configured LSP servers for code intelligence (go-to-definition, find-references, hover)",
|
|
5
5
|
"author": {
|
|
6
6
|
"name": "SpecWeave",
|
|
7
|
-
"url": "https://
|
|
7
|
+
"url": "https://spec-weave.com"
|
|
8
8
|
},
|
|
9
9
|
"keywords": ["lsp", "typescript", "python", "code-intelligence"]
|
|
10
10
|
}
|