bms-speckit-plugin 4.0.1 → 4.1.0

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "bms-speckit",
-  "version": "4.0.0",
+  "version": "4.1.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

@@ -4,14 +4,18 @@
 # This blueprint defines the chain sequence, I/O contracts, error handling,
 # and timeout constraints for each step. The SKILL.md orchestrator executes
 # this chain via Claude Code's Skill tool.
+#
+# Commit strategy: every artifact-producing step commits and pushes immediately
+# to prevent loss and provide traceability per the project constitution.
 
 id: bms_speckit_development_pipeline
-version: 4.0.0
+version: 4.1.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.
 category: Development
 
 # ─── Chain Sequence ────────────────────────────────────────────────────────────
@@ -20,7 +24,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
@@ -30,6 +34,10 @@ chain_sequence:
       requirement: "$ARGUMENTS"
     output:
       artifacts: [detailed_specification]
+    post_action:
+      commit: true
+      message: "feat(speckit): brainstorm — explore requirements and design"
+      push: true
     error_handling:
       on_failure: stop
       max_retries: 1
@@ -38,7 +46,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 +79,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
@@ -80,6 +88,10 @@ chain_sequence:
     input:
       constitution_path: specs/constitution.md
       target_path: CLAUDE.md
+    post_action:
+      commit: true
+      message: "feat(speckit): add constitution and sync CLAUDE.md"
+      push: true
     error_handling:
       on_failure: continue
       max_retries: 1
@@ -88,16 +100,20 @@ 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 brainstorm output
     timeout_seconds: 300
     input:
-      requirement: "{{step_0_brainstorm.output}}"
+      requirement: "{{step_1_brainstorm.output}}"
     output:
       artifacts: [specs/*/spec.md]
+    post_action:
+      commit: true
+      message: "feat(speckit): add feature specification"
+      push: true
     error_handling:
       on_failure: stop
       max_retries: 2
@@ -106,16 +122,20 @@ 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]
+    post_action:
+      commit: true
+      message: "feat(speckit): add implementation plan"
+      push: true
     error_handling:
       on_failure: stop
       max_retries: 2
@@ -124,16 +144,20 @@ 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]
+    post_action:
+      commit: true
+      message: "feat(speckit): add task list"
+      push: true
     error_handling:
       on_failure: stop
       max_retries: 2
@@ -142,16 +166,20 @@ 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]
+    post_action:
+      commit: true
+      message: "feat(speckit): add cross-artifact analysis report"
+      push: true
     error_handling:
       on_failure: continue
       max_retries: 1
@@ -160,20 +188,6 @@ chain_sequence:
         Check spec ↔ plan ↔ tasks consistency. Flag gaps, contradictions,
         and missing test coverage. Non-destructive — report only.
 
-  - step_id: step_7_commit
-    skill_id: internal.git_commit_push
-    action: execute
-    phase: 1
-    description: Commit all specification artifacts and push
-    timeout_seconds: 120
-    error_handling:
-      on_failure: continue
-      max_retries: 1
-    opinionated_prompts:
-      system_context: >
-        Commit all files in specs/ with a descriptive message.
-        Push to remote if configured.
-
   # ── Phase 2: Implementation (main context) ────────────────────────────────
 
   - step_id: step_8_compact
@@ -199,6 +213,10 @@ chain_sequence:
       max_iterations: 10
     output:
       artifacts: [source_code, tests, commits]
+    post_action:
+      commit: per_task
+      message: "feat: implement <task_name>"
+      push: true
     error_handling:
       on_failure: continue
       max_retries: 3
@@ -219,6 +237,10 @@ chain_sequence:
     phase: 2
     description: Final validation pass — confirm production-grade quality
     timeout_seconds: 300
+    post_action:
+      commit: true
+      message: "chore(speckit): final verification pass complete"
+      push: true
     error_handling:
       on_failure: stop
       max_retries: 1
@@ -227,6 +249,22 @@ chain_sequence:
         Final gate. Verify all tasks completed, tests passing,
         no regressions, code quality standards met.
 
+  - step_id: step_11_merge
+    skill_id: internal.git_merge_to_main
+    action: execute
+    phase: 2
+    description: Merge feature branch into main
+    timeout_seconds: 120
+    post_action:
+      push: true
+    error_handling:
+      on_failure: stop
+      max_retries: 1
+    opinionated_prompts:
+      system_context: >
+        Switch to main branch, merge the feature branch (fast-forward if possible),
+        push main to remote, then clean up the feature branch.
+
 # ─── Metadata ──────────────────────────────────────────────────────────────────
 
 metadata:
@@ -234,14 +272,15 @@ metadata:
   created_at: "2026-03-29"
   tags: [speckit, tdd, workflow, development, chain, engineering]
   estimated_duration_seconds: 6000
+  commit_strategy: per_step
   phases:
     phase_1:
       name: Specification & Planning
-      steps: [step_0 through step_7]
+      steps: [step_1 through step_7]
       execution: subagent
       reason: Preserve main context window for implementation
     phase_2:
-      name: Implementation & Verification
-      steps: [step_8 through step_10]
+      name: Implementation & Verification & Merge
+      steps: [step_8 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.1",
+  "version": "4.1.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,8 +14,9 @@ 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 0 (brainstorm). Step 3 (specify) receives the **output from step 0**, not raw `$ARGUMENTS`
-5. Do NOT ask for confirmation between steps
+4. Pass `$ARGUMENTS` (the user's requirement) to step 1 (brainstorm). Step 4 (specify) receives the **output from step 1**, not raw `$ARGUMENTS`
+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
 
 ---
 
@@ -26,54 +27,56 @@ Chain blueprint: `blueprints/bms-speckit-pipeline.yaml`
 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.
+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. **Commit and push after every important step.**
 
-### 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
+- **Post-action:** Commit all files and push. Message: `feat(speckit): brainstorm — explore requirements and design`
 
-### 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
+- **Post-action:** Commit all files and push. Message: `feat(speckit): add constitution and sync CLAUDE.md`
 
-### Step 3 — Specify `[on_failure: STOP]`
+### Step 4 — Specify `[on_failure: STOP]`
 - **Skill:** `speckit.specify`
-- **Input:** Use the detailed specification output from Step 0 (brainstorm) as the argument
+- **Input:** Use the detailed specification output from Step 1 (brainstorm) as the argument
 - **Output:** `specs/*/spec.md`
 - **Timeout:** 300s
 - **Retry:** up to 2 attempts
+- **Post-action:** Commit all files and push. Message: `feat(speckit): add feature specification`
 
-### 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
+- **Post-action:** Commit all files and push. Message: `feat(speckit): add implementation plan`
 
-### 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
+- **Post-action:** Commit all files and push. Message: `feat(speckit): add task list`
 
-### 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]`
-- **Action:** Commit all files and push to remote if configured.
-- **Timeout:** 120s
+- **Post-action:** Commit all files and push. Message: `feat(speckit): add cross-artifact analysis report`
 
 After all steps complete, return: the feature name, number of tasks created, and the path to tasks.md.
 """
@@ -91,23 +94,33 @@ After all steps complete, return: the feature name, number of tasks created, and
 - **Engine:** ralph-loop
 - **Completion promise:** `FINISHED`
 - **Max iterations:** 10
+- **Commit strategy:** Atomic commit after each completed task
 - **Action:** Run:
 
 `/ralph-loop:ralph-loop "systematically execute speckit.implement via the Skill tool to complete every task defined in specs/*/tasks.md with strict adherence to specification requirements, enforce TDD workflow including writing and passing unit, integration, and end-to-end tests before marking any task complete, ensure code quality through linting, static analysis, and consistent architecture with reusable components and centralized business logic, maintain atomic commits after each successful task with clear traceability, avoid requesting confirmation and proceed autonomously, once all tasks are implemented invoke speckit.analyze via the Skill tool to perform a full validation pass, automatically apply all recommended improvements or corrections, re-run all tests to confirm stability and zero regression, and only output <promise>FINISHED</promise> after every task is fully completed, validated, and aligned with production-grade quality standards" --completion-promise "FINISHED" --max-iterations 10`
 
+### Step 10 — Verify `[on_failure: STOP]`
+- **Skill:** `speckit.analyze`
+- **Purpose:** Final validation — confirm all tasks completed, tests passing, no regressions, code quality standards met.
+- **Timeout:** 300s
+- **Post-action:** Commit all files and push. Message: `chore(speckit): final verification pass complete`
+
+### Step 11 — Merge to Main `[on_failure: STOP]`
+- **Action:** Switch to main branch, merge the feature branch (fast-forward if possible), push main to remote, then clean up the feature branch.
+- **Timeout:** 120s
+
 ---
 
 ## Chain Summary
 
 ```
-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 ─────┘
+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
+Step 6: tasks ────────STOP── commit
+Step 7: analyze ──────────── commit
 ```