bms-speckit-plugin 4.3.0 → 4.3.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.
|
@@ -46,7 +46,7 @@ chain_sequence:
|
|
|
46
46
|
system_context: >
|
|
47
47
|
Write a detailed specification from the user's requirement.
|
|
48
48
|
Explore edge cases, constraints, and design alternatives.
|
|
49
|
-
Use
|
|
49
|
+
Use mcp__bms-knowledge-mcp__search_knowledge to search the hosxp
|
|
50
50
|
collection for relevant data dictionaries, table schemas, and
|
|
51
51
|
system architecture. Also search bms, moph, nhso collections
|
|
52
52
|
if relevant to the feature.
|
|
@@ -126,7 +126,7 @@ chain_sequence:
|
|
|
126
126
|
system_context: >
|
|
127
127
|
Generate a complete, testable specification. Include acceptance criteria,
|
|
128
128
|
data models, API contracts, and edge cases.
|
|
129
|
-
Use
|
|
129
|
+
Use mcp__bms-knowledge-mcp__search_knowledge to search the hosxp
|
|
130
130
|
collection for exact table names, field names, data types, and
|
|
131
131
|
relationships needed by this feature. Reference actual HOSxP
|
|
132
132
|
data structures in the spec, not assumed ones.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "bms-speckit-plugin",
|
|
3
|
-
"version": "4.3.
|
|
3
|
+
"version": "4.3.1",
|
|
4
4
|
"description": "Chain-orchestrated development pipeline: /bms-speckit takes requirements and runs brainstorm → constitution → specify → plan → tasks → analyze → implement → verify with per-step error handling",
|
|
5
5
|
"files": [
|
|
6
6
|
".claude-plugin/",
|
|
@@ -33,7 +33,7 @@ You are running the BMS Speckit specification and planning chain. Execute each s
|
|
|
33
33
|
- **Skill:** `superpowers.brainstorm`
|
|
34
34
|
- **Input:** "$ARGUMENTS"
|
|
35
35
|
- **Purpose:** Explore intent, requirements, design alternatives, and edge cases
|
|
36
|
-
- **Knowledge lookup:** Use `
|
|
36
|
+
- **Knowledge lookup:** Use `mcp__bms-knowledge-mcp__search_knowledge` to search the `hosxp` collection for relevant data dictionaries, table schemas, and system architecture. Also search `bms`, `moph`, `nhso` collections if relevant.
|
|
37
37
|
- **Output:** Detailed specification document
|
|
38
38
|
- **Timeout:** 300s
|
|
39
39
|
- **Post-action:** Commit all files and push. Message: `feat(speckit): brainstorm — explore requirements and design`
|
|
@@ -52,7 +52,7 @@ You are running the BMS Speckit specification and planning chain. Execute each s
|
|
|
52
52
|
### Step 4 — Specify `[on_failure: STOP]`
|
|
53
53
|
- **Skill:** `speckit.specify`
|
|
54
54
|
- **Input:** Use the detailed specification output from Step 1 (brainstorm) as the argument
|
|
55
|
-
- **Knowledge lookup:** Use `
|
|
55
|
+
- **Knowledge lookup:** Use `mcp__bms-knowledge-mcp__search_knowledge` to search the `hosxp` collection for exact table names, field names, data types, and relationships needed by this feature. Reference actual HOSxP data structures in the spec.
|
|
56
56
|
- **Output:** `specs/*/spec.md`
|
|
57
57
|
- **Timeout:** 300s
|
|
58
58
|
- **Retry:** up to 2 attempts
|