bms-speckit-plugin 4.0.0 → 4.0.2

package/blueprints/bms-speckit-pipeline.yaml

@@ -20,7 +20,7 @@ chain_sequence:
 
   # ── Phase 1: Specification & Planning (subagent context) ──────────────────
 
-  - step_id: step_0_brainstorm
+  - step_id: step_1_brainstorm
     skill_id: superpowers.brainstorm
     action: execute
     phase: 1
@@ -38,7 +38,7 @@ chain_sequence:
         Write a detailed specification from the user's requirement.
         Explore edge cases, constraints, and design alternatives.
 
-  - step_id: step_1_constitution
+  - step_id: step_2_constitution
     skill_id: speckit.constitution
     action: execute
     phase: 1
@@ -71,7 +71,7 @@ chain_sequence:
         TDD is non-negotiable. Constitution must enforce testing at all levels,
         atomic commits, reusable components, and centralized business logic.
 
-  - step_id: step_2_claude_md_sync
+  - step_id: step_3_claude_md_sync
     skill_id: internal.claude_md_verify
     action: execute
     phase: 1
@@ -88,14 +88,14 @@ chain_sequence:
         Read CLAUDE.md and verify it complies with specs/constitution.md.
         Update CLAUDE.md if it conflicts with or is missing constitution rules.
 
-  - step_id: step_3_specify
+  - step_id: step_4_specify
     skill_id: speckit.specify
     action: execute
     phase: 1
-    description: Create feature specification from requirement
+    description: Create feature specification from brainstorm output
     timeout_seconds: 300
     input:
-      requirement: "$ARGUMENTS"
+      requirement: "{{step_1_brainstorm.output}}"
     output:
       artifacts: [specs/*/spec.md]
     error_handling:
@@ -106,14 +106,14 @@ chain_sequence:
         Generate a complete, testable specification. Include acceptance criteria,
         data models, API contracts, and edge cases.
 
-  - step_id: step_4_plan
+  - step_id: step_5_plan
     skill_id: speckit.plan
     action: execute
     phase: 1
     description: Generate implementation plan from specification
     timeout_seconds: 300
     input:
-      source: "{{step_3_specify.artifacts}}"
+      source: "{{step_4_specify.artifacts}}"
     output:
       artifacts: [specs/*/plan.md]
     error_handling:
@@ -124,14 +124,14 @@ chain_sequence:
         Plan in ordered steps. Include file paths, component boundaries,
         test strategy, and rollback considerations.
 
-  - step_id: step_5_tasks
+  - step_id: step_6_tasks
     skill_id: speckit.tasks
     action: execute
     phase: 1
     description: Generate dependency-ordered task list
     timeout_seconds: 300
     input:
-      source: "{{step_4_plan.artifacts}}"
+      source: "{{step_5_plan.artifacts}}"
     output:
       artifacts: [specs/*/tasks.md]
     error_handling:
@@ -142,14 +142,14 @@ chain_sequence:
         Tasks must be atomic, dependency-ordered, and each independently testable.
         Include clear acceptance criteria per task.
 
-  - step_id: step_6_analyze
+  - step_id: step_7_analyze
     skill_id: speckit.analyze
     action: execute
     phase: 1
     description: Cross-artifact consistency and quality check
     timeout_seconds: 300
     input:
-      source: "{{step_5_tasks.artifacts}}"
+      source: "{{step_6_tasks.artifacts}}"
     output:
       artifacts: [analysis_report]
     error_handling:
@@ -160,7 +160,7 @@ chain_sequence:
         Check spec ↔ plan ↔ tasks consistency. Flag gaps, contradictions,
         and missing test coverage. Non-destructive — report only.
 
-  - step_id: step_7_commit
+  - step_id: step_8_commit
     skill_id: internal.git_commit_push
     action: execute
     phase: 1
@@ -176,7 +176,7 @@ chain_sequence:
 
   # ── Phase 2: Implementation (main context) ────────────────────────────────
 
-  - step_id: step_8_compact
+  - step_id: step_9_compact
     skill_id: internal.compact
     action: execute
     phase: 2
@@ -186,7 +186,7 @@ chain_sequence:
       on_failure: continue
       max_retries: 0
 
-  - step_id: step_9_implement
+  - step_id: step_10_implement
     skill_id: speckit.implement
     action: execute_loop
     phase: 2
@@ -213,7 +213,7 @@ chain_sequence:
         apply improvements, re-run all tests, confirm zero regression.
         Only output FINISHED after everything is validated.
 
-  - step_id: step_10_verify
+  - step_id: step_11_verify
     skill_id: speckit.analyze
     action: execute
     phase: 2
@@ -237,11 +237,11 @@ metadata:
   phases:
     phase_1:
       name: Specification & Planning
-      steps: [step_0 through step_7]
+      steps: [step_1 through step_8]
       execution: subagent
       reason: Preserve main context window for implementation
     phase_2:
       name: Implementation & Verification
-      steps: [step_8 through step_10]
+      steps: [step_9 through step_11]
       execution: main_context
       reason: Implementation needs full tool access and ralph-loop

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bms-speckit-plugin",
-  "version": "4.0.0",
+  "version": "4.0.2",
   "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) only to steps that accept `requirement` input (step 0 and step 3)
+4. Pass `$ARGUMENTS` (the user's requirement) to step 1 (brainstorm). Step 4 (specify) receives the **output from step 1**, not raw `$ARGUMENTS`
 5. Do NOT ask for confirmation between steps
 
 ---
@@ -28,50 +28,50 @@ Subagent prompt:
 """
 You are running the BMS Speckit specification and planning chain. Execute each step in order using the Skill tool. Do NOT ask for confirmation. Follow error handling policies exactly.
 
-### Step 0 — Brainstorm `[on_failure: STOP]`
+### Step 1 — Brainstorm `[on_failure: STOP]`
 - **Skill:** `superpowers.brainstorm`
 - **Input:** "$ARGUMENTS"
 - **Purpose:** Explore intent, requirements, design alternatives, and edge cases
 - **Output:** Detailed specification document
 - **Timeout:** 300s
 
-### Step 1 — Constitution `[on_failure: STOP]`
+### Step 2 — Constitution `[on_failure: STOP]`
 - **Skill:** `speckit.constitution`
 - **Input:** "Establish and enforce a comprehensive set of engineering principles that prioritize high code quality, strict adherence to Test-Driven Development (TDD) practices, and well-defined testing standards across unit, component, integration, and API levels to ensure system reliability and maintainability, maintain a consistent, user-friendly, and professional user interface aligned with strong user experience (UX) guidelines, optimize application performance through efficient architecture and resource management; enforce disciplined version control practices with frequent, atomic commits to minimize risk and improve traceability, promote the development and reuse of modular components and functions while centralizing business logic to avoid duplication and ensure consistency, provide clear, informative user feedback and progress reporting throughout system interactions, and leverage all available tools, frameworks, and domain-specific expertise to support developers in delivering robust, scalable, and high-quality applications."
 - **Output:** `specs/constitution.md`
 - **Timeout:** 300s
 
-### Step 2 — CLAUDE.md Sync `[on_failure: CONTINUE]`
+### Step 3 — CLAUDE.md Sync `[on_failure: CONTINUE]`
 - **Action:** Read CLAUDE.md and verify it complies with the constitution in `specs/constitution.md`. Update CLAUDE.md if it conflicts with or is missing constitution rules.
 - **Timeout:** 120s
 
-### Step 3 — Specify `[on_failure: STOP]`
+### Step 4 — Specify `[on_failure: STOP]`
 - **Skill:** `speckit.specify`
-- **Input:** "$ARGUMENTS"
+- **Input:** Use the detailed specification output from Step 1 (brainstorm) as the argument
 - **Output:** `specs/*/spec.md`
 - **Timeout:** 300s
 - **Retry:** up to 2 attempts
 
-### Step 4 — Plan `[on_failure: STOP]`
+### Step 5 — Plan `[on_failure: STOP]`
 - **Skill:** `speckit.plan`
-- **Input:** reads from step 3 artifacts
+- **Input:** reads from step 4 artifacts
 - **Output:** `specs/*/plan.md`
 - **Timeout:** 300s
 - **Retry:** up to 2 attempts
 
-### Step 5 — Tasks `[on_failure: STOP]`
+### Step 6 — Tasks `[on_failure: STOP]`
 - **Skill:** `speckit.tasks`
-- **Input:** reads from step 4 artifacts
+- **Input:** reads from step 5 artifacts
 - **Output:** `specs/*/tasks.md`
 - **Timeout:** 300s
 - **Retry:** up to 2 attempts
 
-### Step 6 — Analyze `[on_failure: CONTINUE]`
+### Step 7 — Analyze `[on_failure: CONTINUE]`
 - **Skill:** `speckit.analyze`
 - **Purpose:** Cross-artifact consistency check (spec ↔ plan ↔ tasks). Non-destructive — report only.
 - **Timeout:** 300s
 
-### Step 7 — Commit & Push `[on_failure: CONTINUE]`
+### Step 8 — Commit & Push `[on_failure: CONTINUE]`
 - **Action:** Commit all files and push to remote if configured.
 - **Timeout:** 120s
 
@@ -84,10 +84,10 @@ After all steps complete, return: the feature name, number of tasks created, and
 
 > **Execution context:** Runs in main context after subagent completes.
 
-### Step 8 — Compact `[on_failure: CONTINUE]`
+### Step 9 — Compact `[on_failure: CONTINUE]`
 - **Action:** Run `/compact` to free context window before implementation.
 
-### Step 9 — Implement (loop) `[on_failure: CONTINUE | max_retries: 3]`
+### Step 10 — Implement (loop) `[on_failure: CONTINUE | max_retries: 3]`
 - **Engine:** ralph-loop
 - **Completion promise:** `FINISHED`
 - **Max iterations:** 10
@@ -102,12 +102,12 @@ After all steps complete, return: the feature name, number of tasks created, and
 ```
 Phase 1 (subagent)                    Phase 2 (main context)
 ─────────────────────                 ──────────────────────
-Step 0: brainstorm ──STOP──┐          Step 8:  compact
-Step 1: constitution ─STOP─┤          Step 9:  implement (ralph-loop)
-Step 2: CLAUDE.md sync ────┤          Step 10: verify (via step 9)
-Step 3: specify ──────STOP─┤
-Step 4: plan ─────────STOP─┤
-Step 5: tasks ────────STOP─┤
-Step 6: analyze ───────────┤
-Step 7: commit & push ─────┘
+Step 1:  brainstorm ──STOP──┐         Step 9:  compact
+Step 2:  constitution ─STOP─┤         Step 10: implement (ralph-loop)
+Step 3:  CLAUDE.md sync ────┤         Step 11: verify (via step 10)
+Step 4:  specify ──────STOP─┤
+Step 5:  plan ─────────STOP─┤
+Step 6:  tasks ────────STOP─┤
+Step 7:  analyze ───────────┤
+Step 8:  commit & push ─────┘
 ```