bmad-method 6.0.0-Beta.5 → 6.0.0-Beta.7

package/src/bmm/workflows/4-implementation/retrospective/workflow.yaml

@@ -53,6 +53,3 @@ input_file_patterns:
 sprint_status_file: "{implementation_artifacts}/sprint-status.yaml"
 story_directory: "{implementation_artifacts}"
 retrospectives_folder: "{implementation_artifacts}"
-
-standalone: true
-web_bundle: false

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

@@ -49,7 +49,3 @@ input_file_patterns:
 
 # Output configuration
 default_output_file: "{status_file}"
-
-standalone: true
-
-web_bundle: false

package/src/bmm/workflows/4-implementation/sprint-status/workflow.yaml

@@ -28,9 +28,3 @@ input_file_patterns:
     description: "Sprint status file generated by sprint-planning"
     whole: "{implementation_artifacts}/sprint-status.yaml"
     load_strategy: "FULL_LOAD"
-
-# Standalone so IDE commands get generated
-standalone: true
-
-# No web bundle needed
-web_bundle: false

package/src/bmm/workflows/bmad-quick-flow/quick-spec/workflow.md

@@ -2,7 +2,6 @@
 name: quick-spec
 description: Conversational spec engineering - ask questions, investigate code, produce implementation-ready tech-spec.
 main_config: '{project-root}/_bmad/bmm/config.yaml'
-web_bundle: true
 
 # Checkpoint handler paths
 advanced_elicitation: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'

package/src/bmm/workflows/document-project/workflow.yaml

@@ -20,11 +20,3 @@ validation: "{installed_path}/checklist.md"
 
 # Required data files - CRITICAL for project type detection and documentation requirements
 documentation_requirements_csv: "{installed_path}/documentation-requirements.csv"
-
-# Output configuration - Multiple files generated in output folder
-# Primary output: {output_folder}/project-documentation/
-# Additional files generated by sub-workflows based on project structure
-
-standalone: true
-
-web_bundle: false

package/src/bmm/workflows/qa/automate/workflow.yaml

@@ -45,5 +45,3 @@ execution_hints:
   interactive: false
   autonomous: true
   iterative: false
-
-web_bundle: false

package/src/core/tasks/editorial-review-prose.xml

@@ -1,7 +1,6 @@
 <task id="_bmad/core/tasks/editorial-review-prose.xml"
   name="Editorial Review - Prose"
-  description="Clinical copy-editor that reviews text for communication issues"
-  standalone="true">
+  description="Clinical copy-editor that reviews text for communication issues">
 
   <objective>Review text for communication issues that impede comprehension and output suggested fixes in a three-column table</objective>
 
@@ -10,7 +9,7 @@
     <input name="style_guide" required="false"
       desc="Project-specific style guide. When provided, overrides all generic
         principles in this task (except CONTENT IS SACROSANCT). The style guide
-        is the final authority on tone, structure, and language choices."/>
+        is the final authority on tone, structure, and language choices." />
     <input name="reader_type" required="false" default="humans" desc="'humans' (default) for standard editorial, 'llm' for precision focus" />
   </inputs>
 
@@ -62,7 +61,8 @@
     </step>
 
     <step n="3" title="Editorial Review" critical="true">
-      <action if="style_guide provided">Consult style_guide now and note its key requirements—these override default principles for this review</action>
+      <action if="style_guide provided">Consult style_guide now and note its key requirements—these override default principles for this
+        review</action>
       <action>Review all prose sections (skip code blocks, frontmatter, structural markup)</action>
       <action>Identify communication issues that impede comprehension</action>
       <action>For each issue, determine the minimal fix that achieves clarity</action>
@@ -77,16 +77,18 @@
       <action if="no issues found">Output: "No editorial issues identified"</action>
 
       <output-format>
-| Original Text | Revised Text | Changes |
-|---------------|--------------|---------|
-| The exact original passage | The suggested revision | Brief explanation of what changed and why |
+        | Original Text | Revised Text | Changes |
+        |---------------|--------------|---------|
+        | The exact original passage | The suggested revision | Brief explanation of what changed and why |
       </output-format>
 
       <example title="Correct output format">
-| Original Text | Revised Text | Changes |
-|---------------|--------------|---------|
-| The system will processes data and it handles errors. | The system processes data and handles errors. | Fixed subject-verb agreement ("will processes" to "processes"); removed redundant "it" |
-| Users can chose from options (lines 12, 45, 78) | Users can choose from options | Fixed spelling: "chose" to "choose" (appears in 3 locations) |
+        | Original Text | Revised Text | Changes |
+        |---------------|--------------|---------|
+        | The system will processes data and it handles errors. | The system processes data and handles errors. | Fixed subject-verb
+        agreement ("will processes" to "processes"); removed redundant "it" |
+        | Users can chose from options (lines 12, 45, 78) | Users can choose from options | Fixed spelling: "chose" to "choose" (appears in
+        3 locations) |
       </example>
     </step>
   </flow>
@@ -97,4 +99,4 @@
     <condition>If no issues found after thorough review, output "No editorial issues identified" (this is valid completion, not an error)</condition>
   </halt-conditions>
 
-</task>
+</task>

package/src/core/tasks/editorial-review-structure.xml

@@ -4,29 +4,28 @@
 <task id="_bmad/core/tasks/editorial-review-structure.xml"
   name="Editorial Review - Structure"
   description="Structural editor that proposes cuts, reorganization,
-    and simplification while preserving comprehension"
-  standalone="true">
+    and simplification while preserving comprehension">
   <objective>Review document structure and propose substantive changes
     to improve clarity and flow-run this BEFORE copy editing</objective>
   <inputs>
     <input name="content" required="true"
-      desc="Document to review (markdown, plain text, or structured content)"/>
+      desc="Document to review (markdown, plain text, or structured content)" />
     <input name="style_guide" required="false"
       desc="Project-specific style guide. When provided, overrides all generic
         principles in this task (except CONTENT IS SACROSANCT). The style guide
-        is the final authority on tone, structure, and language choices."/>
+        is the final authority on tone, structure, and language choices." />
     <input name="purpose" required="false"
       desc="Document's intended purpose (e.g., 'quickstart tutorial',
-        'API reference', 'conceptual overview')"/>
+        'API reference', 'conceptual overview')" />
     <input name="target_audience" required="false"
       desc="Who reads this? (e.g., 'new users', 'experienced developers',
-        'decision makers')"/>
+        'decision makers')" />
     <input name="reader_type" required="false" default="humans"
       desc="'humans' (default) preserves comprehension aids;
-        'llm' optimizes for precision and density"/>
+        'llm' optimizes for precision and density" />
     <input name="length_target" required="false"
       desc="Target reduction (e.g., '30% shorter', 'half the length',
-        'no limit')"/>
+        'no limit')" />
   </inputs>
   <llm critical="true">
     <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
@@ -69,7 +68,7 @@
       <i>Cut emotional language, encouragement, and orientation sections</i>
       <i>
         IF concept is well-known from training (e.g., "conventional
-          commits", "REST APIs"): Reference the standard-don't re-teach it
+        commits", "REST APIs"): Reference the standard-don't re-teach it
         ELSE: Be explicit-don't assume the LLM will infer correctly
       </i>
       <i>Use consistent terminology-same word for same concept throughout</i>
@@ -132,7 +131,8 @@
       <action>Note reader_type and which principles apply (human-reader-principles or llm-reader-principles)</action>
     </step>
     <step n="3" title="Structural Analysis" critical="true">
-      <action if="style_guide provided">Consult style_guide now and note its key requirements—these override default principles for this analysis</action>
+      <action if="style_guide provided">Consult style_guide now and note its key requirements—these override default principles for this
+        analysis</action>
       <action>Map the document structure: list each major section with its word count</action>
       <action>Evaluate structure against the selected model's primary rules
         (e.g., 'Does recommendation come first?' for Pyramid)</action>
@@ -176,27 +176,27 @@
       <action>Output estimated total reduction if all recommendations accepted</action>
       <action if="no recommendations">Output: "No substantive changes recommended-document structure is sound"</action>
       <output-format>
-## Document Summary
-- **Purpose:** [inferred or provided purpose]
-- **Audience:** [inferred or provided audience]
-- **Reader type:** [selected reader type]
-- **Structure model:** [selected structure model]
-- **Current length:** [X] words across [Y] sections
+        ## Document Summary
+        - **Purpose:** [inferred or provided purpose]
+        - **Audience:** [inferred or provided audience]
+        - **Reader type:** [selected reader type]
+        - **Structure model:** [selected structure model]
+        - **Current length:** [X] words across [Y] sections
 
-## Recommendations
+        ## Recommendations
 
-### 1. [CUT/MERGE/MOVE/CONDENSE/QUESTION/PRESERVE] - [Section or element name]
-**Rationale:** [One sentence explanation]
-**Impact:** ~[X] words
-**Comprehension note:** [If applicable, note impact on reader understanding]
+        ### 1. [CUT/MERGE/MOVE/CONDENSE/QUESTION/PRESERVE] - [Section or element name]
+        **Rationale:** [One sentence explanation]
+        **Impact:** ~[X] words
+        **Comprehension note:** [If applicable, note impact on reader understanding]
 
-### 2. ...
+        ### 2. ...
 
-## Summary
-- **Total recommendations:** [N]
-- **Estimated reduction:** [X] words ([Y]% of original)
-- **Meets length target:** [Yes/No/No target specified]
-- **Comprehension trade-offs:** [Note any cuts that sacrifice reader engagement for brevity]
+        ## Summary
+        - **Total recommendations:** [N]
+        - **Estimated reduction:** [X] words ([Y]% of original)
+        - **Meets length target:** [Yes/No/No target specified]
+        - **Comprehension trade-offs:** [Note any cuts that sacrifice reader engagement for brevity]
       </output-format>
     </step>
   </flow>
@@ -206,4 +206,4 @@
     <condition>If no structural issues found, output "No substantive changes
       recommended" (this is valid completion, not an error)</condition>
   </halt-conditions>
-</task>
+</task>

package/src/core/tasks/help.md

@@ -1,12 +1,11 @@
 ---
 name: help
 description: Get unstuck by showing what workflow steps come next or answering questions about what to do
-standalone: true
 ---
 
 # Task: BMAD Help
 
-## KEY RULES
+## ROUTING RULES
 
 - **Empty `phase` = anytime** — Universal tools work regardless of workflow state
 - **Numbered phases indicate sequence** — Phases like `1-discover` → `2-define` → `3-build` → `4-ship` flow in order (naming varies by module)
@@ -15,6 +14,26 @@ standalone: true
 - **`required=true` blocks progress** — Required workflows must complete before proceeding to later phases
 - **Artifacts reveal completion** — Search resolved output paths for `outputs` patterns, fuzzy-match found files to workflow rows
 
+## DISPLAY RULES
+
+### Command-Based Workflows
+When `command` field has a value:
+- Show the command prefixed with `/` (e.g., `/bmad-bmm-create-prd`)
+
+### Agent-Based Workflows
+When `command` field is empty:
+- User loads agent first via `/agent-command`
+- Then invokes by referencing the `code` field or describing the `name` field
+- Do NOT show a slash command — show the code value and agent load instruction instead
+
+Example presentation for empty command:
+```
+Explain Concept (EC)
+Load: /tech-writer, then ask to "EC about [topic]"
+Agent: Tech Writer
+Description: Create clear technical explanations with examples...
+```
+
 ## MODULE DETECTION
 
 - **Empty `module` column** → universal tools (work across all modules)
@@ -25,10 +44,10 @@ Detect the active module from conversation context, recent workflows, or user qu
 ## INPUT ANALYSIS
 
 Determine what was just completed:
-- Did someone state they completed something? Proceed as if that was the input.
-- Was a workflow just completed in this conversation? Proceed as if that was the input.
-- Search resolved artifact locations for files; fuzzy-match to workflow `outputs` patterns.
-- If an `index.md` exists, read it for additional context.
+- Explicit completion stated by user
+- Workflow completed in current conversation
+- Artifacts found matching `outputs` patterns
+- If `index.md` exists, read it for additional context
 - If still unclear, ask: "What workflow did you most recently complete?"
 
 ## EXECUTION
@@ -37,26 +56,27 @@ Determine what was just completed:
 
 2. **Resolve output locations** — Scan each folder under `_bmad/` (except `_config`) for `config.yaml`. For each workflow row, resolve its `output-location` variables against that module's config so artifact paths can be searched.
 
-3. **Analyze input** — Task may provide a workflow name/code, conversational phrase, or nothing. Infer what was just completed using INPUT ANALYSIS above.
-
-4. **Detect active module** — Use MODULE DETECTION above to determine which module the user is working in.
+3. **Detect active module** — Use MODULE DETECTION above
 
-5. **Present recommendations** — Show next steps based on completed workflows, phase/sequence ordering (KEY RULES), and artifact detection. Format per the following
+4. **Analyze input** — Task may provide a workflow name/code, conversational phrase, or nothing. Infer what was just completed using INPUT ANALYSIS above.
 
-## RECOMMENDED OUTPUT FORMAT
+5. **Present recommendations** — Show next steps based on:
+   - Completed workflows detected
+   - Phase/sequence ordering (ROUTING RULES)
+   - Artifact presence
 
    **Optional items first** — List optional workflows until a required step is reached
    **Required items next** — List the next required workflow
-   For each item show:
+
+   For each item, apply DISPLAY RULES above and include:
    - Workflow **name**
-   - **Command** (prefixed with `/`, e.g., `/bmad:example:build-prototype`)
+   - **Command** OR **Code + Agent load instruction** (per DISPLAY RULES)
    - **Agent** title and display name from the CSV (e.g., "🎨 Alex (Designer)")
    - Brief **description**
 
-   ### Additional response output guidance to convey:
+6. **Additional guidance to convey**:
    - Run each workflow in a **fresh context window**
-   - Load the agent using (`/` + `agent-command`), or run the workflow command directly
    - For **validation workflows**: recommend using a different high-quality LLM if available
    - For conversational requests: match the user's tone while presenting clearly
 
-6. Return to the calling process after presenting recommendations.
+7. Return to the calling process after presenting recommendations.

package/src/core/tasks/index-docs.xml

@@ -1,5 +1,5 @@
 <task id="_bmad/core/tasks/index-docs" name="Index Docs"
-  description="Generates or updates an index.md of all documents in the specified directory" webskip="true" standalone="true">
+  description="Generates or updates an index.md of all documents in the specified directory">
   <llm critical="true">
     <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
     <i>DO NOT skip steps or change the sequence</i>

package/src/core/tasks/review-adversarial-general.xml

@@ -1,7 +1,7 @@
 <!-- if possible, run this in a separate subagent or process with read access to the project, 
   but no context except the content to review -->
 
-<task id="_bmad/core/tasks/review-adversarial-general.xml" name="Adversarial Review (General)" standalone="true">
+<task id="_bmad/core/tasks/review-adversarial-general.xml" name="Adversarial Review (General)">
   <objective>Cynically review content and produce findings</objective>
 
   <inputs>
@@ -45,4 +45,4 @@
     <condition>HALT if content is empty or unreadable</condition>
   </halt-conditions>
 
-</task>
+</task>

package/src/core/tasks/shard-doc.xml

@@ -1,6 +1,5 @@
 <task id="_bmad/core/tasks/shard-doc" name="Shard Document"
-  description="Splits large markdown documents into smaller, organized files based on level 2 (default) sections" webskip="true"
-  standalone="true">
+  description="Splits large markdown documents into smaller, organized files based on level 2 (default) sections">
   <objective>Split large markdown documents into smaller, organized files based on level 2 sections using @kayvan/markdown-tree-parser tool</objective>
 
   <llm critical="true">

package/src/core/tasks/workflow.xml

@@ -1,4 +1,4 @@
-<task id="_bmad/core/tasks/workflow.xml" name="Execute Workflow" standalone="false">
+<task id="_bmad/core/tasks/workflow.xml" name="Execute Workflow" internal="true">
   <objective>Execute given workflow by loading its configuration, following instructions, and producing output</objective>
 
   <llm critical="true">

package/src/core/workflows/advanced-elicitation/workflow.xml

@@ -1,4 +1,4 @@
-<task id="_bmad/core/workflows/advanced-elicitation/workflow.xml" name="Advanced Elicitation" standalone="true"
+<task id="_bmad/core/workflows/advanced-elicitation/workflow.xml" name="Advanced Elicitation"
   methods="{project-root}/_bmad/core/workflows/advanced-elicitation/methods.csv"
   agent-party="{project-root}/_bmad/_config/agent-manifest.csv">
   <llm critical="true">

package/test/test-installation-components.js

@@ -164,7 +164,7 @@ async function runTests() {
 
   try {
     const builder = new YamlXmlBuilder();
-    const qaAgentPath = path.join(projectRoot, 'src/bmm/agents/quinn.agent.yaml');
+    const qaAgentPath = path.join(projectRoot, 'src/bmm/agents/qa.agent.yaml');
     const tempOutput = path.join(__dirname, 'temp-qa-agent.md');
 
     try {

package/tools/build-docs.js

@@ -38,6 +38,7 @@ const LLM_EXCLUDE_PATTERNS = [
   'faq',
   'reference/glossary/',
   'explanation/game-dev/',
+  'bmgd/',
   // Note: Files/dirs starting with _ (like _STYLE_GUIDE.md, _archive/) are excluded in shouldExcludeFromLlm()
 ];
 
@@ -194,7 +195,7 @@ function generateLlmsFullTxt(docsDir, outputDir) {
   console.log('  → Generating llms-full.txt...');
 
   const date = new Date().toISOString().split('T')[0];
-  const files = getAllMarkdownFiles(docsDir);
+  const files = getAllMarkdownFiles(docsDir).sort(compareLlmDocs);
 
   const output = [
     '# BMAD Method Documentation (Full)',
@@ -236,6 +237,25 @@ function generateLlmsFullTxt(docsDir, outputDir) {
   );
 }
 
+function compareLlmDocs(a, b) {
+  const aKey = getLlmSortKey(a);
+  const bKey = getLlmSortKey(b);
+
+  if (aKey !== bKey) return aKey - bKey;
+  return a.localeCompare(b);
+}
+
+function getLlmSortKey(filePath) {
+  if (filePath === 'index.md') return 0;
+  if (filePath === 'downloads.md') return 1;
+  if (filePath.startsWith(`tutorials${path.sep}`) || filePath.startsWith('tutorials/')) return 2;
+  if (filePath.startsWith(`how-to${path.sep}`) || filePath.startsWith('how-to/')) return 3;
+  if (filePath.startsWith(`explanation${path.sep}`) || filePath.startsWith('explanation/')) return 4;
+  if (filePath.startsWith(`reference${path.sep}`) || filePath.startsWith('reference/')) return 5;
+  if (filePath.startsWith(`bmgd${path.sep}`) || filePath.startsWith('bmgd/')) return 6;
+  return 7;
+}
+
 /**
  * Collects all Markdown (.md) files under a directory and returns their paths relative to a base directory.
  * @param {string} dir - Directory to search for Markdown files.

package/tools/cli/bmad-cli.js

@@ -1,6 +1,48 @@
 const { program } = require('commander');
 const path = require('node:path');
 const fs = require('node:fs');
+const { execSync } = require('node:child_process');
+
+// Check for updates - do this asynchronously so it doesn't block startup
+const packageJson = require('../../package.json');
+const packageName = 'bmad-method';
+checkForUpdate().catch(() => {
+  // Silently ignore errors - version check is best-effort
+});
+
+async function checkForUpdate() {
+  try {
+    // For beta versions, check the beta tag; otherwise check latest
+    const isBeta =
+      packageJson.version.includes('Beta') ||
+      packageJson.version.includes('beta') ||
+      packageJson.version.includes('alpha') ||
+      packageJson.version.includes('rc');
+    const tag = isBeta ? 'beta' : 'latest';
+
+    const result = execSync(`npm view ${packageName}@${tag} version`, {
+      encoding: 'utf8',
+      stdio: 'pipe',
+      timeout: 5000,
+    }).trim();
+
+    if (result && result !== packageJson.version) {
+      console.warn('');
+      console.warn('  ╔═══════════════════════════════════════════════════════════════════════════════╗');
+      console.warn('  ║  UPDATE AVAILABLE                                                             ║');
+      console.warn('  ║                                                                               ║');
+      console.warn(`  ║  You are using version ${packageJson.version} but ${result} is available.     ║`);
+      console.warn('  ║                                                                               ║');
+      console.warn('  ║  To update,exir and first run:                                                ║');
+      console.warn(`  ║    npm cache clean --force && npx bmad-method@${tag} install                  ║`);
+      console.warn('  ║                                                                               ║');
+      console.warn('  ╚═══════════════════════════════════════════════════════════════════════════════╝');
+      console.warn('');
+    }
+  } catch {
+    // Silently fail - network issues or npm not available
+  }
+}
 
 // Fix for stdin issues when running through npm on Windows
 // Ensures keyboard interaction works properly with CLI prompts
@@ -20,9 +62,6 @@ if (process.stdin.isTTY) {
   }
 }
 
-// Load package.json from root for version info
-const packageJson = require('../../package.json');
-
 // Load all command modules
 const commandsPath = path.join(__dirname, 'commands');
 const commandFiles = fs.readdirSync(commandsPath).filter((file) => file.endsWith('.js'));

package/tools/cli/installers/lib/core/config-collector.js

@@ -586,7 +586,11 @@ class ConfigCollector {
       console.log();
       console.log(chalk.cyan('?') + ' ' + chalk.magenta(moduleDisplayName));
       let customize = true;
-      if (moduleName !== 'core') {
+      if (moduleName === 'core') {
+        // Core module: no confirm prompt, so add spacing manually to match visual style
+        console.log(chalk.gray('│'));
+      } else {
+        // Non-core modules: show "Accept Defaults?" confirm prompt (clack adds spacing)
         const customizeAnswer = await prompts.prompt([
           {
             type: 'confirm',

package/tools/cli/installers/lib/core/dependency-resolver.js

@@ -146,7 +146,7 @@ class DependencyResolver {
       const content = await fs.readFile(file.path, 'utf8');
 
       // Parse YAML frontmatter for explicit dependencies
-      const frontmatterMatch = content.match(/^---\n([\s\S]*?)\n---/);
+      const frontmatterMatch = content.match(/^---\r?\n([\s\S]*?)\r?\n---/);
       if (frontmatterMatch) {
         try {
           // Pre-process to handle backticks in YAML values

package/tools/cli/installers/lib/core/installer.js

@@ -17,9 +17,7 @@ const { ManifestGenerator } = require('./manifest-generator');
 const { IdeConfigManager } = require('./ide-config-manager');
 const { CustomHandler } = require('../custom/handler');
 const prompts = require('../../../lib/prompts');
-
-// BMAD installation folder name - this is constant and should never change
-const BMAD_FOLDER_NAME = '_bmad';
+const { BMAD_FOLDER_NAME } = require('../ide/shared/path-utils');
 
 class Installer {
   constructor() {
@@ -697,9 +695,6 @@ class Installer {
       config.skipIde = toolSelection.skipIde;
       const ideConfigurations = toolSelection.configurations;
 
-      // Add spacing after prompts before installation progress
-      console.log('');
-
       if (spinner.isSpinning) {
         spinner.text = 'Continuing installation...';
       } else {