bms-speckit-plugin 4.1.1 → 4.3.0

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "bms-speckit",
-  "version": "4.1.0",
+  "version": "4.3.0",
   "description": "Chain-orchestrated development pipeline with per-step error handling. /bms-speckit runs brainstorm → constitution → specify → plan → tasks → analyze → implement → verify.",
   "author": {
     "name": "manoirx"

package/blueprints/bms-speckit-pipeline.yaml

@@ -9,13 +9,14 @@
 # to prevent loss and provide traceability per the project constitution.
 
 id: bms_speckit_development_pipeline
-version: 4.1.0
+version: 4.3.0
 name: BMS Speckit Automated Development Pipeline
 description: >
   Full engineering workflow from requirement to verified implementation.
   Chains brainstorming, constitution, specification, planning, task generation,
   analysis, implementation (TDD), and final verification.
-  Commits after every important step for traceability and safety.
+  Commits after every important step. Uses knowledge-mcp during brainstorm
+  and specify steps to ground specs in real HOSxP data.
 category: Development
 
 # ─── Chain Sequence ────────────────────────────────────────────────────────────
@@ -45,6 +46,10 @@ chain_sequence:
       system_context: >
         Write a detailed specification from the user's requirement.
         Explore edge cases, constraints, and design alternatives.
+        Use mcp__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 to the feature.
 
   - step_id: step_2_constitution
     skill_id: speckit.constitution
@@ -104,7 +109,7 @@ chain_sequence:
     skill_id: speckit.specify
     action: execute
     phase: 1
-    description: Create feature specification from brainstorm output
+    description: Create feature specification enriched with HOSxP knowledge
     timeout_seconds: 300
     input:
       requirement: "{{step_1_brainstorm.output}}"
@@ -121,6 +126,10 @@ chain_sequence:
       system_context: >
         Generate a complete, testable specification. Include acceptance criteria,
         data models, API contracts, and edge cases.
+        Use mcp__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, not assumed ones.
 
   - step_id: step_5_plan
     skill_id: speckit.plan
@@ -270,9 +279,14 @@ chain_sequence:
 metadata:
   author: manoirx
   created_at: "2026-03-29"
-  tags: [speckit, tdd, workflow, development, chain, engineering]
+  tags: [speckit, tdd, workflow, development, chain, engineering, hosxp, knowledge]
   estimated_duration_seconds: 6000
   commit_strategy: per_step
+  knowledge_collections:
+    hosxp: "Data dictionaries, ER diagrams, table schemas, module architecture"
+    bms: "BMS tools, organization, API info"
+    moph: "Ministry of Public Health regulations"
+    nhso: "NHSO reimbursement rules and announcements"
   phases:
     phase_1:
       name: Specification & Planning

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bms-speckit-plugin",
-  "version": "4.1.1",
+  "version": "4.3.0",
   "description": "Chain-orchestrated development pipeline: /bms-speckit takes requirements and runs brainstorm → constitution → specify → plan → tasks → analyze → implement → verify with per-step error handling",
   "files": [
     ".claude-plugin/",

package/skills/bms-speckit-auto/SKILL.md

@@ -14,7 +14,7 @@ Chain blueprint: `blueprints/bms-speckit-pipeline.yaml`
 3. On step failure, check the **error policy** before proceeding:
    - `on_failure: stop` → halt the chain and report which step failed
    - `on_failure: continue` → log the failure and proceed to next step
-4. Pass `$ARGUMENTS` (the user's requirement) to step 1 (brainstorm). Step 4 (specify) receives the **output from step 1**, not raw `$ARGUMENTS`
+4. Pass `$ARGUMENTS` (the user's requirement) to step 1 (brainstorm). Step 4 (specify) receives the **output from step 1**
 5. **Commit and push after every important step** — each artifact-producing step must commit its output before proceeding to the next step
 6. Do NOT ask for confirmation between steps
 
@@ -33,6 +33,7 @@ You are running the BMS Speckit specification and planning chain. Execute each s
 - **Skill:** `superpowers.brainstorm`
 - **Input:** "$ARGUMENTS"
 - **Purpose:** Explore intent, requirements, design alternatives, and edge cases
+- **Knowledge lookup:** Use `mcp__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.
 - **Output:** Detailed specification document
 - **Timeout:** 300s
 - **Post-action:** Commit all files and push. Message: `feat(speckit): brainstorm — explore requirements and design`
@@ -51,6 +52,7 @@ You are running the BMS Speckit specification and planning chain. Execute each s
 ### Step 4 — Specify `[on_failure: STOP]`
 - **Skill:** `speckit.specify`
 - **Input:** Use the detailed specification output from Step 1 (brainstorm) as the argument
+- **Knowledge lookup:** Use `mcp__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.
 - **Output:** `specs/*/spec.md`
 - **Timeout:** 300s
 - **Retry:** up to 2 attempts
@@ -118,10 +120,12 @@ After all steps complete, return: the feature name, number of tasks created, and
 Phase 1 (subagent)                          Phase 2 (main context)
 ──────────────────────────────              ──────────────────────────────
 Step 1: brainstorm ──STOP── commit          Step 8:  compact
-Step 2: constitution ─STOP─┐               Step 9:  implement (ralph-loop)
-Step 3: CLAUDE.md sync ────┘ commit                  commit per task
-Step 4: specify ──────STOP── commit         Step 10: verify ── commit
-Step 5: plan ─────────STOP── commit         Step 11: merge to main + push
+        + knowledge search (hosxp)          Step 9:  implement (ralph-loop)
+Step 2: constitution ─STOP─┐                         commit per task
+Step 3: CLAUDE.md sync ───┘ commit          Step 10: verify ── commit
+Step 4: specify ──────STOP── commit         Step 11: merge to main + push
+        + knowledge search (hosxp)
+Step 5: plan ─────────STOP── commit
 Step 6: tasks ────────STOP── commit
 Step 7: analyze ──────────── commit
 ```