bms-speckit-plugin 2.0.1 → 2.1.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bms-speckit-plugin",
-  "version": "2.0.1",
+  "version": "2.1.1",
   "description": "Single-command automated development pipeline: /bms-speckit takes requirements and runs constitution → specify → plan → tasks → analyze → implement → verify",
   "files": [
     ".claude-plugin/",

package/skills/speckit/SKILL.md

@@ -58,7 +58,10 @@ All work follows these principles:
   - Risk assessment
 - Commit: `feat: add implementation plan for {feature-name}`
 
-### Step 4: Create Task List
+### Step 4: Compact context (first)
+- Run `/compact` to free up context window after the heavy specification and planning work
+
+### Step 5: Create Task List
 - Read the plan
 - Create `specs/{feature-name}/tasks.md` with granular tasks (5-15 min each)
 - Each task includes:
@@ -78,7 +81,7 @@ All work follows these principles:
 - Order: setup → data layer → business logic → UI → integration → polish
 - Commit: `feat: add task list for {feature-name}`
 
-### Step 5: Analyze Tasks
+### Step 6: Analyze Tasks
 - Review all tasks for quality:
   - Granular enough? (5-15 min each)
   - Each independently testable?
@@ -88,30 +91,24 @@ All work follows these principles:
 - Fix any issues found in tasks.md
 - Commit if changes made
 
-### Step 6: Implement ALL Tasks
-For each pending task, execute the TDD cycle:
-
-1. Update task status to `in_progress` in tasks.md
-2. **Write the test first** — meaningful tests that verify behavior
-3. **Run tests — verify they FAIL** (if they pass, tests are wrong)
-4. **Write minimal implementation** to make tests pass
-5. **Run ALL tests — verify they PASS** (fix regressions)
-6. **Commit** with the task's commit message
-7. Update task status to `completed` and increment completed count
-8. Move to next pending task
-
-If a task is blocked, mark as `blocked` with reason and continue.
-
-### Step 7: Final Verification
-- Run the full test suite
-- Review all specification requirements are met
-- Check for security issues
-- Run the analyze step again on completed code
-- If issues found, create new tasks and implement them
-- Commit any final fixes
-
-### Step 8: Summary Report
-Output a final report:
+### Step 7: Commit and push
+- Commit all spec files created so far
+- Push to remote if configured
+- This preserves work before the long implementation phase
+
+### Step 8: Compact context (second)
+- Run `/compact` to free up context window before implementation
+
+### Step 9: Implement with ralph-loop
+Invoke ralph-loop to implement all tasks automatically:
+
+```
+/ralph-loop:ralph-loop "Read specs/*/tasks.md and implement the next pending task using TDD (write test first, verify fail, implement, verify pass, commit). Update task status to completed after each task. Do not ask for any confirmation. Once all tasks are done, run analysis: read specs/*/tasks.md and verify all tasks are completed, run the full test suite, check all specification requirements are met, fix any issues found, and output <promise>FINISHED</promise> only after all tasks are completed and revalidated" --completion-promise "FINISHED" --max-iterations 10
+```
+
+### After ralph-loop completes
+
+Output a final summary:
 - What was built
 - Total tests passing
 - Files created/modified