fix: addressed Brian 2nd round of comments

CHANGELOG.md

@@ -1,41 +1,5 @@
 # Changelog
 
-## [6.0.0-Beta.4]
-
-### 🐛 Bug Fixes
-
-- **Activation steps formatting fix**: Fixed missing opening quote that caused infrequent menu rendering issues
-- **Custom module installation fix**: Added missing yaml require in manifest.js to fix custom module installation
-
----
-
-## [6.0.0-Beta.3]
-
-### 🌟 Key Highlights
-
-1. **SDET Module Replaces TEA**: TEA module removed from core, SDET module added with "automate" workflow for test automation
-2. **Gemini CLI TOML Support**: IDE integration now supports the TOML config format used by Gemini CLI
-3. **File System Sprint Status**: Default project_key support for file-system based sprint status tracking
-
-### 🔧 Features & Improvements
-
-**Module Changes:**
-- **TEA Module Moved to External** (#1430, #1443): The TEA module is now external. SDET module added with a single "automate" workflow focused on test automation
-- **SDET Module**: New module with streamlined test automation capabilities
-
-**IDE Integration:**
-- **Gemini CLI TOML Format** (#1431): Previous update accidentally switched Gemini to md instead of toml.
-
-**Sprint Status:**
-- **Default project_key** (#1446): File-system based sprint status now uses a default project_key so certain LLMs do not complain
-
-### 🐛 Bug Fixes
-
-- **Quick-flow workflow path fix** (#1368): Fixed incorrect workflow_path in bmad-quick-flow/quick-spec steps (step-01, step-02, step-03) - changed from non-existent 'create-tech-spec' to correct 'quick-spec'
-- **PRD edit flow paths**: Fixed path references in PRD editing workflow
-- **Agent file handling**: Changes to prevent double agent files and use .agent.md file extensions
-- **README link fix**: Corrected broken documentation links
-
 ## [6.0.0-Beta.2]
 
 - Fix installer so commands match what is installed, centralize most ide into a central file instead of separate files for each ide.

package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "bmad-method",
-  "version": "6.0.0-Beta.4",
+  "version": "6.0.0-Beta.2",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "bmad-method",
-      "version": "6.0.0-Beta.4",
+      "version": "6.0.0-Beta.2",
       "license": "MIT",
       "dependencies": {
         "@clack/prompts": "^0.11.0",

package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method",
-  "version": "6.0.0-Beta.4",
+  "version": "6.0.0-Beta.2",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "keywords": [
     "agile",

src/bmm/workflows/2-plan-workflows/create-prd/validation-report-prd-workflow.md

@@ -8,7 +8,7 @@ validationStatus: COMPLETE - PRODUCTION READY
 
 # PRD Workflow Validation Report
 
-**Workflow Being Validated:** _bmad/bmm/workflows/2-plan-workflows/create-prd
+**Workflow Being Validated:** /Users/brianmadison/dev/BMAD-METHOD/src/bmm/workflows/2-plan-workflows/create-prd
 **Validation Date:** 2026-01-08
 **Validator:** BMAD Workflow Validation System
 

src/bmm/workflows/4-implementation/sprint-planning/sprint-status-template.yaml

@@ -36,7 +36,7 @@
 
 generated: 05-06-2-2025 21:30
 project: My Awesome Project
-project_key: NOKEY
+project_key: jira-1234
 tracking_system: file-system
 story_location: "{story_location}"
 

src/bmm/workflows/4-implementation/sprint-planning/workflow.yaml

@@ -26,7 +26,6 @@ variables:
 
   # Tracking system configuration
   tracking_system: "file-system" # Options: file-system, Future will support other options from config of mcp such as jira, linear, trello
-  project_key: "NOKEY" # Placeholder for tracker integrations; file-system uses a no-op key
   story_location: "{config_source}:implementation_artifacts" # Relative path for file-system, Future will support URL for Jira/Linear/Trello
   story_location_absolute: "{config_source}:implementation_artifacts" # Absolute path for file operations
 

src/utility/agent-components/activation-steps.txt

@@ -8,7 +8,7 @@
     <step n="3">Remember: user's name is {user_name}</step>
     {AGENT_SPECIFIC_STEPS}
     <step n="{MENU_STEP}">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of ALL menu items from menu section</step>
-    <step n="{HELP_STEP}">Let {user_name} know they can type command `/bmad-help` at any time to get advice on what to do next, and that they can combine that with what they need help with <example>`/bmad-help where should I start with an idea I have that does XYZ`</example></step>
+    <step n={HELP_STEP}">-Let {user_name} know they can type command `/bmad-help` at any time to get advice on what to do next, and that they can combine that with what they need help with <example>`/bmad-help where should I start with an idea I have that does XYZ`</example></step>
     <step n="{HALT_STEP}">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command match</step>
     <step n="{INPUT_STEP}">On user input: Number → process menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user to clarify | No match → show "Not recognized"</step>
     <step n="{EXECUTE_STEP}">When processing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>

tools/cli/installers/lib/core/manifest.js

@@ -835,7 +835,6 @@ class Manifest {
    */
   async getModuleVersionInfo(moduleName, bmadDir, moduleSourcePath = null) {
     const os = require('node:os');
-    const yaml = require('yaml');
 
     // Built-in modules use BMad version (only core and bmm are in BMAD-METHOD repo)
     if (['core', 'bmm'].includes(moduleName)) {

tools/cli/lib/activation-builder.js

@@ -121,10 +121,9 @@ class ActivationBuilder {
 
     // Calculate final step numbers
     const menuStep = currentStepNum;
-    const helpStep = currentStepNum + 1;
-    const haltStep = currentStepNum + 2;
-    const inputStep = currentStepNum + 3;
-    const executeStep = currentStepNum + 4;
+    const haltStep = currentStepNum + 1;
+    const inputStep = currentStepNum + 2;
+    const executeStep = currentStepNum + 3;
 
     // Replace placeholders
     const processed = stepsTemplate
@@ -132,7 +131,6 @@ class ActivationBuilder {
       .replace('{{module}}', metadata.module || 'core') // Fixed to use {{module}}
       .replace('{AGENT_SPECIFIC_STEPS}', agentStepsXml)
       .replace('{MENU_STEP}', menuStep.toString())
-      .replace('{HELP_STEP}', helpStep.toString())
       .replace('{HALT_STEP}', haltStep.toString())
       .replace('{INPUT_STEP}', inputStep.toString())
       .replace('{EXECUTE_STEP}', executeStep.toString());