From c0f5d33c615a8edb2a62ba97b531b952140c806c Mon Sep 17 00:00:00 2001 From: Brian Madison Date: Tue, 23 Dec 2025 20:52:06 +0800 Subject: [PATCH 1/4] core module always asks its questions (no accept defaults --- .../installers/lib/core/config-collector.js | 36 +++++++------------ 1 file changed, 13 insertions(+), 23 deletions(-) diff --git a/tools/cli/installers/lib/core/config-collector.js b/tools/cli/installers/lib/core/config-collector.js index 2d916c2f..fad0f108 100644 --- a/tools/cli/installers/lib/core/config-collector.js +++ b/tools/cli/installers/lib/core/config-collector.js @@ -582,26 +582,23 @@ class ConfigCollector { // If there are questions to ask, prompt for accepting defaults vs customizing if (questions.length > 0) { - // Get friendly module name from config or use uppercase module name const moduleDisplayName = moduleConfig.header || `${moduleName.toUpperCase()} Module`; - - // Add blank line for better readability console.log(); - - // Display the module name in color first console.log(chalk.cyan('?') + ' ' + chalk.magenta(moduleDisplayName)); + let customize = true; + if (moduleName !== 'core') { + const customizeAnswer = await inquirer.prompt([ + { + type: 'confirm', + name: 'customize', + message: 'Accept Defaults (no to customize)?', + default: true, + }, + ]); + customize = customizeAnswer.customize; + } - // Ask user if they want to accept defaults or customize on the next line - const { customize } = await inquirer.prompt([ - { - type: 'confirm', - name: 'customize', - message: 'Accept Defaults (no to customize)?', - default: true, - }, - ]); - - if (customize) { + if (customize && moduleName !== 'core') { // Accept defaults - only ask questions that have NO default value const questionsWithoutDefaults = questions.filter((q) => q.default === undefined || q.default === null || q.default === ''); @@ -621,8 +618,6 @@ class ConfigCollector { allAnswers[question.name] = question.default; } } else { - // Customize - ask all questions - console.log(chalk.dim(`\n Configuring ${moduleName.toUpperCase()}...`)); const promptedAnswers = await inquirer.prompt(questions); Object.assign(allAnswers, promptedAnswers); } @@ -647,8 +642,6 @@ class ConfigCollector { // For arrays (multi-select), handle differently if (Array.isArray(value)) { - // If there's a result template and it's a string, don't use it for arrays - // Just use the array value directly result = value; } else if (item.result) { result = item.result; @@ -663,11 +656,9 @@ class ConfigCollector { if (result === '{value}') { result = value; } else { - // Otherwise replace in the string result = result.replace('{value}', value); } } else { - // For non-string values, use directly result = value; } @@ -719,7 +710,6 @@ class ConfigCollector { } } } else { - // No result template, use value directly result = value; } From 4195eb3b30bdb4c5e8b468b9b12371769bc43b9e Mon Sep 17 00:00:00 2001 From: Brian Madison Date: Tue, 23 Dec 2025 21:43:29 +0800 Subject: [PATCH 2/4] installation intro and outtro custom messages, configurable in install-messages.yaml --- .github/workflows/quality.yaml | 3 - package.json | 3 +- tools/cli/commands/install.js | 16 ++-- tools/cli/installers/install-messages.yaml | 52 +++++++++++++ tools/cli/installers/lib/message-loader.js | 85 +++++++++++++++++++++ tools/cli/lib/ui.js | 5 +- tools/validate-bundles.js | 87 ---------------------- 7 files changed, 153 insertions(+), 98 deletions(-) create mode 100644 tools/cli/installers/install-messages.yaml create mode 100644 tools/cli/installers/lib/message-loader.js delete mode 100644 tools/validate-bundles.js diff --git a/.github/workflows/quality.yaml b/.github/workflows/quality.yaml index 8111ca44..495b66f5 100644 --- a/.github/workflows/quality.yaml +++ b/.github/workflows/quality.yaml @@ -92,6 +92,3 @@ jobs: - name: Test agent compilation components run: npm run test:install - - - name: Validate web bundles - run: npm run validate:bundles diff --git a/package.json b/package.json index e8583be3..b116ecbd 100644 --- a/package.json +++ b/package.json @@ -39,11 +39,10 @@ "release:minor": "gh workflow run \"Manual Release\" -f version_bump=minor", "release:patch": "gh workflow run \"Manual Release\" -f version_bump=patch", "release:watch": "gh run watch", - "test": "npm run test:schemas && npm run test:install && npm run validate:bundles && npm run validate:schemas && npm run lint && npm run lint:md && npm run format:check", + "test": "npm run test:schemas && npm run test:install && npm run validate:schemas && npm run lint && npm run lint:md && npm run format:check", "test:coverage": "c8 --reporter=text --reporter=html npm run test:schemas", "test:install": "node test/test-installation-components.js", "test:schemas": "node test/test-agent-schema.js", - "validate:bundles": "node tools/validate-bundles.js", "validate:schemas": "node tools/validate-agent-schema.js" }, "lint-staged": { diff --git a/tools/cli/commands/install.js b/tools/cli/commands/install.js index d2f72ef6..6e241610 100644 --- a/tools/cli/commands/install.js +++ b/tools/cli/commands/install.js @@ -26,11 +26,12 @@ module.exports = { const result = await installer.quickUpdate(config); console.log(chalk.green('\n✨ Quick update complete!')); console.log(chalk.cyan(`Updated ${result.moduleCount} modules with preserved settings`)); - console.log( - chalk.magenta( - "\nπŸ“‹ Want to see what's new? Check out the changelog: https://github.com/bmad-code-org/BMAD-METHOD/blob/main/CHANGELOG.md", - ), - ); + + // Display version-specific end message + const { MessageLoader } = require('../installers/lib/message-loader'); + const messageLoader = new MessageLoader(); + messageLoader.displayEndMessage(); + process.exit(0); return; } @@ -97,6 +98,11 @@ module.exports = { } } + // Display version-specific end message from install-messages.yaml + const { MessageLoader } = require('../installers/lib/message-loader'); + const messageLoader = new MessageLoader(); + messageLoader.displayEndMessage(); + process.exit(0); } } catch (error) { diff --git a/tools/cli/installers/install-messages.yaml b/tools/cli/installers/install-messages.yaml new file mode 100644 index 00000000..1de5c070 --- /dev/null +++ b/tools/cli/installers/install-messages.yaml @@ -0,0 +1,52 @@ +# BMAD Installer Messages +# These messages are displayed during installation +# Edit this file to change what users see during the install process + +# Display at the START of installation (after logo, before prompts) +startMessage: | + ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ + + πŸŽ‰πŸŽ‰ Happy Holidays and New Year 🍾🍾 + + IMPORTANT Changes with Version Alpha.20 - PLEASE READ THIS if upgrading from earlier Alpha Versions: + + 1. The BMad Core default output folder has changed from docs to `_bmad-output`. `docs` is meant for long-term artifacts, which you can always decide to move content to. + + 2. If utilizing the BMad Method Module (BMM) please be aware of the following important recent changes: + + - Phases 1-3 (Analysis, Planning, Solutioning) will now default output to _bmad-output/planning-artifacts + - Phase 4 (Implementation) will now default output to _bmad-output/implementation-artifacts + - Long term project knowledge (research, docs, references, document-project output) will now default to docs/ + + IT IS STRONGLY SUGGESTED to align with these folder conventions instead of dumping all to docs/ - if you are upgrading from a prior + version where all output was going to docs or docs/sprint-artifacts, it is suggested to reset configs to these new values. + + If you have anything in progress, you can move what was in sprint-artifacts to _bmad-output/implementation-artifacts, and if you had brainstorming + content, a PRD, UX or Architecture, you can move the content to _bmad-output/planning-artifacts. + + Read the latest updates before continuing: + https://github.com/bmad-code-org/BMAD-METHOD/blob/main/CHANGELOG.md + + ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ + +# Display at the END of installation (after all setup completes) +endMessage: | + ════════════════════════════════════════════════════════════════════════════════ + + ✨ BMAD IS READY TO USE! + + ONE FINAL NOTE WITH VERSION Alpha.20: Phase 4 (Implementation) is still in the process of being migrated to the improved workflow progressive disclosure system. + Along with this, the full conversion to the new path locations for content being searched may possibly be incomplete. If you run a workflow that relies on finding input documents automatically, and you notice they are not being found / looking in the wrong location, either: + 1. Manually specify the correct input location when prompted + 2. Open an issue on GitHub so we can address the problem quickly if you think its a bug. + 3. Ensure your content is in the new locations for best results: + - Planning Artifacts (Phases 1-3): _bmad-output/planning-artifacts + - Implementation Artifacts (Phase 4): _bmad-output/implementation-artifacts + - Long Term Project Knowledge (docs, research, references): docs/ + + Thank you for helping test the early release version of the new BMad Core and BMad Method! + Stable Beta coming soon - please read the full README.md and linked documentation to get started. + + And again, here is the Change Log with all the details of recent updates: https://github.com/bmad-code-org/BMAD-METHOD/blob/main/CHANGELOG.md + + ════════════════════════════════════════════════════════════════════════════════ diff --git a/tools/cli/installers/lib/message-loader.js b/tools/cli/installers/lib/message-loader.js new file mode 100644 index 00000000..dd112669 --- /dev/null +++ b/tools/cli/installers/lib/message-loader.js @@ -0,0 +1,85 @@ +const fs = require('fs-extra'); +const path = require('node:path'); +const yaml = require('yaml'); +const chalk = require('chalk'); + +/** + * Load and display installer messages from messages.yaml + */ +class MessageLoader { + constructor() {} + + /** + * Load messages from the YAML file + * @returns {Object|null} Messages object or null if not found + */ + load() { + if (this.messages) { + return this.messages; + } + + const messagesPath = path.join(__dirname, '..', 'install-messages.yaml'); + + try { + const content = fs.readFileSync(messagesPath, 'utf8'); + this.messages = yaml.parse(content); + return this.messages; + } catch { + // File doesn't exist or is invalid - return null + return null; + } + } + + /** + * Get the start message for display + * @returns {string|null} Start message or null + */ + getStartMessage() { + const messages = this.load(); + return messages?.startMessage || null; + } + + /** + * Get the end message for display + * @returns {string|null} End message or null + */ + getEndMessage() { + const messages = this.load(); + return messages?.endMessage || null; + } + + /** + * Display the start message (after logo, before prompts) + */ + displayStartMessage() { + const message = this.getStartMessage(); + if (message) { + console.log(chalk.cyan(message)); + console.log(); + } + } + + /** + * Display the end message (after installation completes) + */ + displayEndMessage() { + const message = this.getEndMessage(); + if (message) { + console.log(); + console.log(chalk.cyan(message)); + } + } + + /** + * Check if messages exist for the current version + * @param {string} currentVersion - Current package version + * @returns {boolean} True if messages match current version + */ + isCurrent(currentVersion) { + const messages = this.load(); + return messages && messages.version === currentVersion; + } + messages = null; +} + +module.exports = { MessageLoader }; diff --git a/tools/cli/lib/ui.js b/tools/cli/lib/ui.js index 7aae6456..ab055643 100644 --- a/tools/cli/lib/ui.js +++ b/tools/cli/lib/ui.js @@ -17,7 +17,10 @@ class UI { async promptInstall() { CLIUtils.displayLogo(); - console.log(chalk.cyan('\nRead the latest updates: https://github.com/bmad-code-org/BMAD-METHOD/blob/main/CHANGELOG.md\n')); + // Display version-specific start message from install-messages.yaml + const { MessageLoader } = require('../installers/lib/message-loader'); + const messageLoader = new MessageLoader(); + messageLoader.displayStartMessage(); const confirmedDirectory = await this.getConfirmedDirectory(); diff --git a/tools/validate-bundles.js b/tools/validate-bundles.js deleted file mode 100644 index 674e4c63..00000000 --- a/tools/validate-bundles.js +++ /dev/null @@ -1,87 +0,0 @@ -const fs = require('fs-extra'); -const path = require('node:path'); -const xml2js = require('xml2js'); -const chalk = require('chalk'); -const glob = require('glob'); - -async function validateXmlFile(filePath) { - try { - const content = await fs.readFile(filePath, 'utf8'); - await xml2js.parseStringPromise(content, { - strict: true, - explicitArray: false, - }); - return { valid: true }; - } catch (error) { - return { valid: false, error: error.message }; - } -} - -async function validateAllBundles() { - console.log(chalk.cyan.bold('\n═══════════════════════════════════════════════')); - console.log(chalk.cyan.bold(' VALIDATING WEB BUNDLE XML FILES')); - console.log(chalk.cyan.bold('═══════════════════════════════════════════════\n')); - - const bundlesDir = path.join(__dirname, '..', 'web-bundles'); - - // Find all XML files in web-bundles - const pattern = path.join(bundlesDir, '**/*.xml'); - const files = glob.sync(pattern); - - if (files.length === 0) { - console.log(chalk.yellow('No XML files found in web-bundles directory')); - return; - } - - console.log(`Found ${chalk.bold(files.length)} XML files to validate\n`); - - let validCount = 0; - let invalidCount = 0; - const invalidFiles = []; - - for (const file of files) { - const relativePath = path.relative(bundlesDir, file); - const result = await validateXmlFile(file); - - if (result.valid) { - console.log(`${chalk.green('βœ“')} ${relativePath}`); - validCount++; - } else { - console.log(`${chalk.red('βœ—')} ${relativePath}`); - console.log(` ${chalk.red('β†’')} ${result.error}`); - invalidCount++; - invalidFiles.push({ path: relativePath, error: result.error }); - } - } - - // Summary - console.log(chalk.cyan.bold('\n═══════════════════════════════════════════════')); - console.log(chalk.cyan.bold(' SUMMARY')); - console.log(chalk.cyan.bold('═══════════════════════════════════════════════\n')); - - console.log(` Total files checked: ${chalk.bold(files.length)}`); - console.log(` Valid XML files: ${chalk.green(validCount)}`); - console.log(` Invalid XML files: ${invalidCount > 0 ? chalk.red(invalidCount) : chalk.green(invalidCount)}`); - - if (invalidFiles.length > 0) { - console.log(chalk.red.bold('\n Invalid Files:')); - for (const { path, error } of invalidFiles) { - console.log(` ${chalk.red('β€’')} ${path}`); - if (error.length > 100) { - console.log(` ${error.slice(0, 100)}...`); - } else { - console.log(` ${error}`); - } - } - } - - console.log(chalk.cyan.bold('\n═══════════════════════════════════════════════\n')); - - process.exit(invalidCount > 0 ? 1 : 0); -} - -// Run validation -validateAllBundles().catch((error) => { - console.error(chalk.red('Error running validation:'), error); - process.exit(1); -}); From e4a4f47a1e176a103ac39b9992a229c7dd8b763b Mon Sep 17 00:00:00 2001 From: Brian Madison Date: Tue, 23 Dec 2025 22:21:59 +0800 Subject: [PATCH 3/4] remove unnecessary \ before _ and disable md auto fix --- package.json | 3 +-- .../templates/step-01-init-continuable-template.md | 14 +++++++------- .../3-technical/game-architecture/instructions.md | 2 +- .../create-architecture/steps/step-01-init.md | 8 ++++---- 4 files changed, 13 insertions(+), 14 deletions(-) diff --git a/package.json b/package.json index b116ecbd..6848282d 100644 --- a/package.json +++ b/package.json @@ -58,8 +58,7 @@ "npm run format:fix" ], "*.md": [ - "markdownlint-cli2", - "npm run format:fix" + "markdownlint-cli2" ] }, "dependencies": { diff --git a/src/modules/bmb/docs/workflows/templates/step-01-init-continuable-template.md b/src/modules/bmb/docs/workflows/templates/step-01-init-continuable-template.md index beb56dff..9b5794ef 100644 --- a/src/modules/bmb/docs/workflows/templates/step-01-init-continuable-template.md +++ b/src/modules/bmb/docs/workflows/templates/step-01-init-continuable-template.md @@ -13,16 +13,16 @@ description: 'Initialize the [workflow-type] workflow by detecting continuation -workflow\*path: '{project-root}/\_bmad/[module-path]/workflows/[workflow-name]' +workflow\*path: `{project-root}/_bmad/[module-path]/workflows/[workflow-name]` # File References (all use {variable} format in file) -thisStepFile: '{workflow_path}/steps/step-01-init.md' -nextStepFile: '{workflow_path}/steps/step-02-[step-name].md' -workflowFile: '{workflow_path}/workflow.md' -outputFile: '{output_folder}/[output-file-name]-{project_name}.md' -continueFile: '{workflow_path}/steps/step-01b-continue.md' -templateFile: '{workflow_path}/templates/[main-template].md' +thisStepFile: `{workflow_path}/steps/step-01-init.md` +nextStepFile: `{workflow_path}/steps/step-02-[step-name].md` +workflowFile: `{workflow_path}/workflow.md` +outputFile: `{output_folder}/[output-file-name]-{project_name}.md` +continueFile: `{workflow_path}/steps/step-01b-continue.md` +templateFile: `{workflow_path}/templates/[main-template].md` # Template References diff --git a/src/modules/bmgd/workflows/3-technical/game-architecture/instructions.md b/src/modules/bmgd/workflows/3-technical/game-architecture/instructions.md index 20bb9a1f..673ed07e 100644 --- a/src/modules/bmgd/workflows/3-technical/game-architecture/instructions.md +++ b/src/modules/bmgd/workflows/3-technical/game-architecture/instructions.md @@ -74,7 +74,7 @@ For Level {{project_level}}, we'll keep the architecture appropriately scoped. Decision Architecture works from your Product Requirements Document (PRD). -Looking for: _prd_.md, or prd/index.md + files in {output_folder} +Looking for: `*prd*.md`, or `prd/index.md` + files in {output_folder} Please run the PRD workflow first to define your requirements. diff --git a/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-01-init.md b/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-01-init.md index 4d661420..8cbcaa47 100644 --- a/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-01-init.md +++ b/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-01-init.md @@ -58,14 +58,14 @@ Discover and load context documents using smart discovery: **PRD Document (Priority: Analysis β†’ Main β†’ Sharded β†’ Whole):** -1. Check analysis folders: {output*folder} and {planning_artifacts} for a \_prd*.md +1. Check analysis folders: {output_folder} and {planning_artifacts} for a `*prd*.md` 2. If no main files: Check for sharded PRD folder: `**/*prd*/**/*.md` 3. If sharded folder exists: Load EVERY file in that folder completely 4. Add discovered files to `inputDocuments` frontmatter **Epics/Stories Document (Priority: Analysis β†’ Main β†’ Sharded β†’ Whole):** -1. Check folders: {output*folder} and {planning_artifacts} for a \_epic*.md +1. Check folders: {output_folder} and {planning_artifacts} for a `*epic*.md` 2. If no analysis files: Try main folder: `{output_folder}/*epic*.md` 3. If no main files: Check for sharded epics folder: `{output_folder}/*epic*/**/*.md` 4. If sharded folder exists: Load EVERY file in that folder completely @@ -73,14 +73,14 @@ Discover and load context documents using smart discovery: **UX Design Specification (Priority: Analysis β†’ Main β†’ Sharded β†’ Whole):** -1. Check folders: {output*folder} and {planning_artifacts} for a \_ux*.md +1. Check folders: {output_folder} and {planning_artifacts} for a `*ux*.md` 2. If no main files: Check for sharded UX folder: `{output_folder}/*ux*/**/*.md` 3. If sharded folder exists: Load EVERY file in that folder completely 4. Add discovered files to `inputDocuments` frontmatter **Research Documents (Priority: Analysis β†’ Main):** -1. Check folders {output*folder} and {planning_artifacts} for /research/\_research*.md +1. Check folders {output_folder} and {planning_artifacts} for `/research/*research*.md` 2. If no files: Try folder: `{output_folder}/*research*.md` 3. Add discovered files to `inputDocuments` frontmatter From 925b715d4f7bf92cbdb5f84e7f105bcd01dcf5c0 Mon Sep 17 00:00:00 2001 From: Brian Madison Date: Tue, 23 Dec 2025 22:29:51 +0800 Subject: [PATCH 4/4] prettier no longer should screw up md files underscores --- .../toolsmith-sidecar/knowledge/installers.md | 4 ++-- .../toolsmith/toolsmith-sidecar/knowledge/modules.md | 2 +- .../workflows/quiz-master/steps/step-01-init.md | 2 +- .../workflows/quiz-master/workflow.md | 2 +- package.json | 4 ++-- .../bmb/docs/agents/expert-agent-architecture.md | 4 ++-- .../bmb/docs/agents/understanding-agent-types.md | 2 +- .../bmb/docs/workflows/templates/step-1b-template.md | 2 +- .../bmb/docs/workflows/templates/step-template.md | 6 +++--- .../bmb/docs/workflows/templates/workflow-template.md | 2 +- src/modules/bmb/docs/workflows/templates/workflow.md | 2 +- .../workflows/meal-prep-nutrition/workflow.md | 2 +- .../bmb/workflows-legacy/edit-module/checklist.md | 2 +- .../bmb/workflows-legacy/edit-module/instructions.md | 6 +++--- .../bmb/workflows-legacy/module-brief/instructions.md | 4 ++-- .../workflows/meal-prep-nutrition/workflow.md | 2 +- .../create-agent/templates/expert-agent.template.md | 6 +++--- .../workflows/create-module/steps/step-04-structure.md | 2 +- .../workflows/create-module/steps/step-08-installer.md | 10 +++++----- .../create-module/templates/agent.template.md | 2 +- src/modules/bmb/workflows/create-module/validation.md | 4 ++-- src/modules/bmb/workflows/create-module/workflow.md | 2 +- .../workflows/create-workflow/steps/step-07-build.md | 4 ++-- src/modules/bmb/workflows/create-workflow/workflow.md | 2 +- src/modules/bmb/workflows/edit-agent/workflow.md | 2 +- src/modules/bmb/workflows/edit-workflow/workflow.md | 2 +- .../steps/step-02-workflow-validation.md | 2 +- .../workflows/workflow-compliance-check/workflow.md | 2 +- .../1-preproduction/brainstorm-game/instructions.md | 2 +- .../1-preproduction/game-brief/instructions.md | 2 +- .../2-design/narrative/instructions-narrative.md | 2 +- .../3-technical/game-architecture/instructions.md | 2 +- .../generate-project-context/steps/step-02-generate.md | 4 ++-- .../workflows/4-production/correct-course/checklist.md | 2 +- .../4-production/correct-course/instructions.md | 4 ++-- .../4-production/retrospective/instructions.md | 4 ++-- .../4-production/sprint-planning/instructions.md | 4 ++-- .../4-production/sprint-status/instructions.md | 4 ++-- .../workflows/workflow-status/init/instructions.md | 2 +- .../bmgd/workflows/workflow-status/instructions.md | 4 ++-- .../1-analysis/create-product-brief/workflow.md | 2 +- .../create-ux-design/steps/step-02-discovery.md | 4 ++-- .../create-ux-design/steps/step-03-core-experience.md | 8 ++++---- .../steps/step-04-emotional-response.md | 8 ++++---- .../create-ux-design/steps/step-05-inspiration.md | 8 ++++---- .../create-ux-design/steps/step-06-design-system.md | 8 ++++---- .../steps/step-07-defining-experience.md | 8 ++++---- .../steps/step-08-visual-foundation.md | 8 ++++---- .../steps/step-09-design-directions.md | 8 ++++---- .../create-ux-design/steps/step-10-user-journeys.md | 8 ++++---- .../steps/step-11-component-strategy.md | 8 ++++---- .../create-ux-design/steps/step-12-ux-patterns.md | 8 ++++---- .../steps/step-13-responsive-accessibility.md | 8 ++++---- .../2-plan-workflows/prd/steps/step-03-success.md | 8 ++++---- .../2-plan-workflows/prd/steps/step-04-journeys.md | 8 ++++---- .../2-plan-workflows/prd/steps/step-05-domain.md | 8 ++++---- .../2-plan-workflows/prd/steps/step-06-innovation.md | 8 ++++---- .../2-plan-workflows/prd/steps/step-07-project-type.md | 8 ++++---- .../2-plan-workflows/prd/steps/step-08-scoping.md | 8 ++++---- .../2-plan-workflows/prd/steps/step-09-functional.md | 8 ++++---- .../prd/steps/step-10-nonfunctional.md | 8 ++++---- .../check-implementation-readiness/workflow.md | 2 +- .../create-architecture/steps/step-02-context.md | 8 ++++---- .../create-architecture/steps/step-03-starter.md | 4 ++-- .../create-architecture/steps/step-04-decisions.md | 8 ++++---- .../create-architecture/steps/step-05-patterns.md | 8 ++++---- .../create-architecture/steps/step-06-structure.md | 8 ++++---- .../create-architecture/steps/step-07-validation.md | 8 ++++---- .../3-solutioning/create-epics-and-stories/workflow.md | 2 +- .../4-implementation/correct-course/checklist.md | 2 +- .../4-implementation/correct-course/instructions.md | 4 ++-- .../4-implementation/retrospective/instructions.md | 4 ++-- .../4-implementation/sprint-planning/instructions.md | 4 ++-- .../4-implementation/sprint-status/instructions.md | 4 ++-- .../bmm/workflows/document-project/instructions.md | 4 ++-- .../generate-project-context/steps/step-02-generate.md | 4 ++-- .../bmm/workflows/workflow-status/init/instructions.md | 2 +- .../bmm/workflows/workflow-status/instructions.md | 4 ++-- .../cis/workflows/design-thinking/instructions.md | 4 ++-- .../cis/workflows/innovation-strategy/instructions.md | 4 ++-- .../cis/workflows/problem-solving/instructions.md | 4 ++-- 81 files changed, 187 insertions(+), 187 deletions(-) diff --git a/docs/sample-custom-modules/sample-unitary-module/agents/toolsmith/toolsmith-sidecar/knowledge/installers.md b/docs/sample-custom-modules/sample-unitary-module/agents/toolsmith/toolsmith-sidecar/knowledge/installers.md index 75c925f6..65db8645 100644 --- a/docs/sample-custom-modules/sample-unitary-module/agents/toolsmith/toolsmith-sidecar/knowledge/installers.md +++ b/docs/sample-custom-modules/sample-unitary-module/agents/toolsmith/toolsmith-sidecar/knowledge/installers.md @@ -30,7 +30,7 @@ ### IDE Manager & Base - @/tools/cli/installers/lib/ide/manager.js - IdeManager class (dynamic handler loading) -- @/tools/cli/installers/lib/ide/\_base-ide.js - BaseIdeSetup class (all handlers extend this) +- @/tools/cli/installers/lib/ide/_base-ide.js - BaseIdeSetup class (all handlers extend this) ### Shared Utilities @@ -116,7 +116,7 @@ Contains: - Add new IDE handler: Create file in /tools/cli/installers/lib/ide/, extend BaseIdeSetup - Fix installer bug: Check installer.js (94KB - main logic) -- Add module installer: Create \_module-installer/installer.js if custom installer logic needed +- Add module installer: Create _module-installer/installer.js if custom installer logic needed - Update shared generators: Modify files in /shared/ directory ## Relationships diff --git a/docs/sample-custom-modules/sample-unitary-module/agents/toolsmith/toolsmith-sidecar/knowledge/modules.md b/docs/sample-custom-modules/sample-unitary-module/agents/toolsmith/toolsmith-sidecar/knowledge/modules.md index 496356f6..663fcc60 100644 --- a/docs/sample-custom-modules/sample-unitary-module/agents/toolsmith/toolsmith-sidecar/knowledge/modules.md +++ b/docs/sample-custom-modules/sample-unitary-module/agents/toolsmith/toolsmith-sidecar/knowledge/modules.md @@ -142,7 +142,7 @@ Defined in @/tools/cli/lib/platform-codes.js ## Common Tasks -- Create new module installer: Add \_module-installer/installer.js +- Create new module installer: Add _module-installer/installer.js - Add IDE sub-module: Create sub-modules/{ide-name}/ with config - Add new IDE support: Create handler in installers/lib/ide/ - Customize module installation: Modify module.yaml diff --git a/docs/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-01-init.md b/docs/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-01-init.md index 9551dee2..9ed3ffe2 100644 --- a/docs/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-01-init.md +++ b/docs/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-01-init.md @@ -66,7 +66,7 @@ To set up the quiz game by selecting game mode, choosing a category, and prepari ### 1. Welcome and Configuration Loading -Load config from {project-root}/\_bmad/bmb/config.yaml to get user_name. +Load config from {project-root}/_bmad/bmb/config.yaml to get user_name. Present dramatic welcome: "🎺 _DRAMATIC MUSIC PLAYS_ 🎺 diff --git a/docs/sample-custom-modules/sample-unitary-module/workflows/quiz-master/workflow.md b/docs/sample-custom-modules/sample-unitary-module/workflows/quiz-master/workflow.md index d0e72459..badf9c51 100644 --- a/docs/sample-custom-modules/sample-unitary-module/workflows/quiz-master/workflow.md +++ b/docs/sample-custom-modules/sample-unitary-module/workflows/quiz-master/workflow.md @@ -45,7 +45,7 @@ web_bundle: true ### 1. Module Configuration Loading -Load and read full config from {project-root}/\_bmad/bmb/config.yaml and resolve: +Load and read full config from {project-root}/_bmad/bmb/config.yaml and resolve: - `user_name`, `output_folder`, `communication_language`, `document_output_language` diff --git a/package.json b/package.json index 6848282d..a640704c 100644 --- a/package.json +++ b/package.json @@ -27,8 +27,8 @@ "bmad:install": "node tools/cli/bmad-cli.js install", "bundle": "node tools/cli/bundlers/bundle-web.js all", "flatten": "node tools/flattener/main.js", - "format:check": "prettier --check \"**/*.{js,cjs,mjs,json,md,yaml}\"", - "format:fix": "prettier --write \"**/*.{js,cjs,mjs,json,md,yaml}\"", + "format:check": "prettier --check \"**/*.{js,cjs,mjs,json,yaml}\"", + "format:fix": "prettier --write \"**/*.{js,cjs,mjs,json,yaml}\"", "install:bmad": "node tools/cli/bmad-cli.js install", "lint": "eslint . --ext .js,.cjs,.mjs,.yaml --max-warnings=0", "lint:fix": "eslint . --ext .js,.cjs,.mjs,.yaml --fix", diff --git a/src/modules/bmb/docs/agents/expert-agent-architecture.md b/src/modules/bmb/docs/agents/expert-agent-architecture.md index abfa6c29..84731543 100644 --- a/src/modules/bmb/docs/agents/expert-agent-architecture.md +++ b/src/modules/bmb/docs/agents/expert-agent-architecture.md @@ -355,8 +355,8 @@ identity: | - [ ] Sidecar folder structure created and populated - [ ] memories.md has clear section structure - [ ] instructions.md contains core directives -- [ ] Menu actions reference \_bmad/\_memory correctly -- [ ] File paths use \_bmad/\_memory/[agentname]-sidecar/ to reference sidecar content +- [ ] Menu actions reference _bmad/_memory correctly +- [ ] File paths use _bmad/_memory/[agentname]-sidecar/ to reference sidecar content - [ ] Install config personalizes sidecar references - [ ] Agent folder named consistently: `{agent-name}/` - [ ] YAML file named: `{agent-name}.agent.yaml` diff --git a/src/modules/bmb/docs/agents/understanding-agent-types.md b/src/modules/bmb/docs/agents/understanding-agent-types.md index 80cc0395..08e35345 100644 --- a/src/modules/bmb/docs/agents/understanding-agent-types.md +++ b/src/modules/bmb/docs/agents/understanding-agent-types.md @@ -7,7 +7,7 @@ ALL agent types can: - βœ“ Write to {output_folder}, {project-root}, or anywhere on system - βœ“ Update artifacts and files - βœ“ Execute bash commands -- βœ“ Use core variables (\_bmad, {output_folder}, etc.) +- βœ“ Use core variables (_bmad, {output_folder}, etc.) - βœ“ Have complex prompts and logic - βœ“ Invoke external tools diff --git a/src/modules/bmb/docs/workflows/templates/step-1b-template.md b/src/modules/bmb/docs/workflows/templates/step-1b-template.md index 3f5273ac..8e34bdd4 100644 --- a/src/modules/bmb/docs/workflows/templates/step-1b-template.md +++ b/src/modules/bmb/docs/workflows/templates/step-1b-template.md @@ -13,7 +13,7 @@ description: 'Handle workflow continuation from previous session' -workflow\*path: '{project-root}/\_bmad/[module-path]/workflows/[workflow-name]' +workflow\*path: '{project-root}/_bmad/[module-path]/workflows/[workflow-name]' # File References (all use {variable} format in file) diff --git a/src/modules/bmb/docs/workflows/templates/step-template.md b/src/modules/bmb/docs/workflows/templates/step-template.md index 55612989..5c4c8578 100644 --- a/src/modules/bmb/docs/workflows/templates/step-template.md +++ b/src/modules/bmb/docs/workflows/templates/step-template.md @@ -11,7 +11,7 @@ description: '[Brief description of what this step accomplishes]' -workflow\*path: '{project-root}/\_bmad/[module]/reference/workflows/[workflow-name]' # the folder the workflow.md file is in +workflow\*path: '{project-root}/_bmad/[module]/reference/workflows/[workflow-name]' # the folder the workflow.md file is in # File References (all use {variable} format in file) @@ -23,8 +23,8 @@ outputFile: '{output_folder}/[output-file-name]-{project_name}.md' # Task References (IF THE workflow uses and it makes sense in this step to have these ) -advancedElicitationTask: '{project-root}/\_bmad/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/\_bmad/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md' # Template References (if this step uses a specific templates) diff --git a/src/modules/bmb/docs/workflows/templates/workflow-template.md b/src/modules/bmb/docs/workflows/templates/workflow-template.md index 109eb820..5cc687a3 100644 --- a/src/modules/bmb/docs/workflows/templates/workflow-template.md +++ b/src/modules/bmb/docs/workflows/templates/workflow-template.md @@ -53,7 +53,7 @@ web_bundle: [true/false] # Set to true for inclusion in web bundle builds ### 1. Module Configuration Loading -Load and read full config from {project-root}/\_bmad/[MODULE FOLDER]/config.yaml and resolve: +Load and read full config from {project-root}/_bmad/[MODULE FOLDER]/config.yaml and resolve: - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, [MODULE VARS] diff --git a/src/modules/bmb/docs/workflows/templates/workflow.md b/src/modules/bmb/docs/workflows/templates/workflow.md index e68f52cd..65a8eb26 100644 --- a/src/modules/bmb/docs/workflows/templates/workflow.md +++ b/src/modules/bmb/docs/workflows/templates/workflow.md @@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution: ### 1. Configuration Loading -Load and read full config from {project-root}/\_bmad/{{targetModule}}/config.yaml and resolve: +Load and read full config from {project-root}/_bmad/{{targetModule}}/config.yaml and resolve: - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language` diff --git a/src/modules/bmb/reference/workflows/meal-prep-nutrition/workflow.md b/src/modules/bmb/reference/workflows/meal-prep-nutrition/workflow.md index 8db13c65..54b5b495 100644 --- a/src/modules/bmb/reference/workflows/meal-prep-nutrition/workflow.md +++ b/src/modules/bmb/reference/workflows/meal-prep-nutrition/workflow.md @@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution: ### 1. Configuration Loading -Load and read full config from {project-root}/\_bmad/core/config.yaml and resolve: +Load and read full config from {project-root}/_bmad/core/config.yaml and resolve: - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language` diff --git a/src/modules/bmb/workflows-legacy/edit-module/checklist.md b/src/modules/bmb/workflows-legacy/edit-module/checklist.md index 40b0759c..779ec5c4 100644 --- a/src/modules/bmb/workflows-legacy/edit-module/checklist.md +++ b/src/modules/bmb/workflows-legacy/edit-module/checklist.md @@ -126,7 +126,7 @@ Use this checklist to validate module edits meet BMAD Core standards. - [ ] Web bundles configured in workflow.yaml files - [ ] All referenced files included in web_bundle_files -- [ ] Paths are \_bmad/-relative (not project-root) +- [ ] Paths are _bmad/-relative (not project-root) - [ ] No config_source references in web bundles - [ ] Invoked workflows included in dependencies diff --git a/src/modules/bmb/workflows-legacy/edit-module/instructions.md b/src/modules/bmb/workflows-legacy/edit-module/instructions.md index 364daf39..6f3e2b8b 100644 --- a/src/modules/bmb/workflows-legacy/edit-module/instructions.md +++ b/src/modules/bmb/workflows-legacy/edit-module/instructions.md @@ -1,7 +1,7 @@ # Edit Module - Module Editor Instructions -The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml -You MUST have already loaded and processed: {project-root}/\_bmad/bmb/workflows/edit-module/workflow.yaml +The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project-root}/_bmad/bmb/workflows/edit-module/workflow.yaml This workflow uses ADAPTIVE FACILITATION - adjust your communication based on context and user needs The goal is COLLABORATIVE IMPROVEMENT - work WITH the user, not FOR them Communicate all responses in {communication_language} @@ -186,7 +186,7 @@ Let the conversation flow naturally. Build a shared vision of what "better" look **If setting up cross-module integration:** - Identify which workflows from other modules are needed -- Show how to reference workflows properly: {project-root}/\_bmad/{{module}}/workflows/{{workflow}}/workflow.yaml +- Show how to reference workflows properly: {project-root}/_bmad/{{module}}/workflows/{{workflow}}/workflow.yaml - Document the integration in README - Ensure dependencies are clear - Consider adding example usage diff --git a/src/modules/bmb/workflows-legacy/module-brief/instructions.md b/src/modules/bmb/workflows-legacy/module-brief/instructions.md index 384fa101..1693c3c5 100644 --- a/src/modules/bmb/workflows-legacy/module-brief/instructions.md +++ b/src/modules/bmb/workflows-legacy/module-brief/instructions.md @@ -1,7 +1,7 @@ # Module Brief Instructions -The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml -You MUST have already loaded and processed: {project-root}/\_bmad/bmb/workflows/module-brief/workflow.yaml +The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project-root}/_bmad/bmb/workflows/module-brief/workflow.yaml Communicate in {communication_language} throughout the module brief creation process ⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. diff --git a/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/workflow.md b/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/workflow.md index 6b6fd9db..a63fa50f 100644 --- a/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/workflow.md +++ b/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/workflow.md @@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution: ### 1. Configuration Loading -Load and read full config from {project-root}/\_bmad/bmm/config.yaml and resolve: +Load and read full config from {project-root}/_bmad/bmm/config.yaml and resolve: - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, `user_skill_level` diff --git a/src/modules/bmb/workflows/create-agent/templates/expert-agent.template.md b/src/modules/bmb/workflows/create-agent/templates/expert-agent.template.md index bcc2444b..069512cc 100644 --- a/src/modules/bmb/workflows/create-agent/templates/expert-agent.template.md +++ b/src/modules/bmb/workflows/create-agent/templates/expert-agent.template.md @@ -313,7 +313,7 @@ critical_actions: 1. **Load sidecar files in critical_actions** - Must be explicit and MANDATORY 2. **Enforce domain restrictions** - Clear boundaries prevent scope creep -3. **Use \_bmad/\_memory/[agentname]-sidcar/ paths** - For reference to any sidecar content +3. **Use _bmad/_memory/[agentname]-sidcar/ paths** - For reference to any sidecar content 4. **Design for memory growth** - Structure sidecar files for accumulation 5. **Reference past naturally** - Don't dump memory, weave it into conversation 6. **Separate concerns** - Memories, instructions, knowledge in distinct files @@ -356,8 +356,8 @@ identity: | - [ ] Sidecar folder structure created and populated - [ ] memories.md has clear section structure - [ ] instructions.md contains core directives -- [ ] Menu actions reference \_bmad/\_memory/[agentname]-sidcar/ correctly if needing sidecar content reference -- [ ] File paths use \_bmad/\_memory/[agentname]-sidcar/ to reference where the file will be after sidecar content is installed +- [ ] Menu actions reference _bmad/_memory/[agentname]-sidcar/ correctly if needing sidecar content reference +- [ ] File paths use _bmad/_memory/[agentname]-sidcar/ to reference where the file will be after sidecar content is installed - [ ] Install config personalizes sidecar references - [ ] Agent folder named consistently: `{agent-name}/` - [ ] YAML file named: `{agent-name}.agent.yaml` diff --git a/src/modules/bmb/workflows/create-module/steps/step-04-structure.md b/src/modules/bmb/workflows/create-module/steps/step-04-structure.md index 2a02d91a..5d857d67 100644 --- a/src/modules/bmb/workflows/create-module/steps/step-04-structure.md +++ b/src/modules/bmb/workflows/create-module/steps/step-04-structure.md @@ -129,7 +129,7 @@ Create all directories in {bmb_creations_output_folder}/{module_name}/: 3. **tasks/** - For task files (if tasks planned) 4. **templates/** - For shared templates 5. **data/** - For module data -6. **\_module-installer/** - For installation configuration +6. **_module-installer/** - For installation configuration ### 4. Create Placeholder README diff --git a/src/modules/bmb/workflows/create-module/steps/step-08-installer.md b/src/modules/bmb/workflows/create-module/steps/step-08-installer.md index ea981793..cc0cd553 100644 --- a/src/modules/bmb/workflows/create-module/steps/step-08-installer.md +++ b/src/modules/bmb/workflows/create-module/steps/step-08-installer.md @@ -71,8 +71,8 @@ From step 5, we planned these configuration fields: ### 2. Create Installer Directory -Ensure \_module-installer directory exists -Directory: {bmb_creations_output_folder}/{module_name}/\_module-installer/ +Ensure _module-installer directory exists +Directory: {bmb_creations_output_folder}/{module_name}/_module-installer/ ### 3. Create module.yaml @@ -95,7 +95,7 @@ Does your module need any special setup during installation? For example: "I'll create an installer.js file for custom logic." -Create file: {bmb_creations_output_folder}/{module_name}/\_module-installer/installer.js from {installerTemplate} +Create file: {bmb_creations_output_folder}/{module_name}/_module-installer/installer.js from {installerTemplate} Update installer.js with module-specific logic @@ -105,7 +105,7 @@ Update installer.js with module-specific logic If your module needs to copy files during installation (templates, examples, documentation), we can add them to the assets directory." -Create directory: \_module-installer/assets/ +Create directory: _module-installer/assets/ Add note about what assets to include ### 6. Document Installer Setup @@ -131,7 +131,7 @@ Update module-plan.md with installer section: 1. User runs: `bmad install {module_name}` 2. Installer asks: [list of questions] -3. Creates: \_bmad/{module_name}/ +3. Creates: _bmad/{module_name}/ 4. Generates: config.yaml with user settings ### Validation diff --git a/src/modules/bmb/workflows/create-module/templates/agent.template.md b/src/modules/bmb/workflows/create-module/templates/agent.template.md index 94db0a5f..fc81f385 100644 --- a/src/modules/bmb/workflows/create-module/templates/agent.template.md +++ b/src/modules/bmb/workflows/create-module/templates/agent.template.md @@ -264,7 +264,7 @@ Analyze the visual design with my signature dramatic flair menu: # Core interactions - multi: "[CH] Chat with Caravaggio or [SPM] Start Party Mode" triggers: - party-mode: input: SPM or fuzzy match start party mode -route: "{project-root}/\_bmad/core/workflows/edit-agent/workflow.md" +route: "{project-root}/_bmad/core/workflows/edit-agent/workflow.md" data: what's being discussed, plus custom party agents if specified type: exec - expert-chat: input: CH or fuzzy match validate agent diff --git a/src/modules/bmb/workflows/create-module/validation.md b/src/modules/bmb/workflows/create-module/validation.md index 3783b2aa..147664d3 100644 --- a/src/modules/bmb/workflows/create-module/validation.md +++ b/src/modules/bmb/workflows/create-module/validation.md @@ -11,11 +11,11 @@ This document provides the validation criteria used in step-11-validate.md to en - [ ] tasks/ - Task files (if needed) - [ ] templates/ - Shared templates - [ ] data/ - Module data -- [ ] \_module-installer/ - Installation config +- [ ] _module-installer/ - Installation config - [ ] README.md - Module documentation - [ ] module.yaml - module config file -### Optional File in \_module-installer/ +### Optional File in _module-installer/ - [ ] installer.js - Custom logic (if needed) diff --git a/src/modules/bmb/workflows/create-module/workflow.md b/src/modules/bmb/workflows/create-module/workflow.md index 7541f2fa..46badff8 100644 --- a/src/modules/bmb/workflows/create-module/workflow.md +++ b/src/modules/bmb/workflows/create-module/workflow.md @@ -46,7 +46,7 @@ installed_path: '{project-root}/_bmad/bmb/workflows/create-module' ### 1. Module Configuration Loading -Load and read full config from {project-root}/\_bmad/bmb/config.yaml and resolve: +Load and read full config from {project-root}/_bmad/bmb/config.yaml and resolve: - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, `bmb_creations_output_folder` diff --git a/src/modules/bmb/workflows/create-workflow/steps/step-07-build.md b/src/modules/bmb/workflows/create-workflow/steps/step-07-build.md index 0998631d..9dab2ab7 100644 --- a/src/modules/bmb/workflows/create-workflow/steps/step-07-build.md +++ b/src/modules/bmb/workflows/create-workflow/steps/step-07-build.md @@ -72,7 +72,7 @@ To generate all the workflow files (workflow.md, step files, templates, and supp - When building continuable step-01-init.md files, use template `{project-root}/_bmad/bmb/docs/workflows/templates/step-01-init-continuable-template.md` - When building continuation steps, use template `{project-root}/_bmad/bmb/docs/workflows/templates/step-1b-template.md` - When building the main workflow.md file, you must follow template `{project-root}/_bmad/bmb/docs/workflows/templates/workflow-template.md` -- Example step files from {project-root}/\_bmad/bmb/reference/workflows/meal-prep-nutrition/workflow.md for patterns +- Example step files from {project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition/workflow.md for patterns ## FILE GENERATION SEQUENCE: @@ -117,7 +117,7 @@ Load and follow {workflowTemplate}: - Create workflow.md using template structure - Insert workflow name and description -- Configure all path variables ({project-root}, \_bmad, {workflow_path}) +- Configure all path variables ({project-root}, _bmad, {workflow_path}) - Set web_bundle flag to true unless user has indicated otherwise - Define role and goal - Include initialization path to step-01 diff --git a/src/modules/bmb/workflows/create-workflow/workflow.md b/src/modules/bmb/workflows/create-workflow/workflow.md index 500097ba..22dd4484 100644 --- a/src/modules/bmb/workflows/create-workflow/workflow.md +++ b/src/modules/bmb/workflows/create-workflow/workflow.md @@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution: ### 1. Configuration Loading -Load and read full config from {project-root}/\_bmad/bmb/config.yaml and resolve: +Load and read full config from {project-root}/_bmad/bmb/config.yaml and resolve: - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, `bmb_creations_output_folder` diff --git a/src/modules/bmb/workflows/edit-agent/workflow.md b/src/modules/bmb/workflows/edit-agent/workflow.md index 9cb9529c..e26cc99b 100644 --- a/src/modules/bmb/workflows/edit-agent/workflow.md +++ b/src/modules/bmb/workflows/edit-agent/workflow.md @@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution: ### 1. Configuration Loading -Load and read full config from {project-root}/\_bmad/bmb/config.yaml and resolve: +Load and read full config from {project-root}/_bmad/bmb/config.yaml and resolve: - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language` diff --git a/src/modules/bmb/workflows/edit-workflow/workflow.md b/src/modules/bmb/workflows/edit-workflow/workflow.md index 35f6124e..1daaca4d 100644 --- a/src/modules/bmb/workflows/edit-workflow/workflow.md +++ b/src/modules/bmb/workflows/edit-workflow/workflow.md @@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution: ### 1. Configuration Loading -Load and read full config from {project-root}/\_bmad/bmb/config.yaml and resolve: +Load and read full config from {project-root}/_bmad/bmb/config.yaml and resolve: - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language` diff --git a/src/modules/bmb/workflows/workflow-compliance-check/steps/step-02-workflow-validation.md b/src/modules/bmb/workflows/workflow-compliance-check/steps/step-02-workflow-validation.md index 24cebddc..6028ee28 100644 --- a/src/modules/bmb/workflows/workflow-compliance-check/steps/step-02-workflow-validation.md +++ b/src/modules/bmb/workflows/workflow-compliance-check/steps/step-02-workflow-validation.md @@ -135,7 +135,7 @@ For each deviation: - Configuration Loading uses correct path format: `{project-root}/_bmad/[module]/config.yaml` (variable substitution pattern) - First step follows pattern: `step-01-init.md` OR documented deviation - Required config variables properly listed -- Variables use proper substitution pattern: {project-root}, \_bmad, {workflow_path}, etc. +- Variables use proper substitution pattern: {project-root}, _bmad, {workflow_path}, etc. For violations: diff --git a/src/modules/bmb/workflows/workflow-compliance-check/workflow.md b/src/modules/bmb/workflows/workflow-compliance-check/workflow.md index 7d944650..1f95ea1d 100644 --- a/src/modules/bmb/workflows/workflow-compliance-check/workflow.md +++ b/src/modules/bmb/workflows/workflow-compliance-check/workflow.md @@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution: ### 1. Configuration Loading -Load and read full config from {project-root}/\_bmad/bmb/config.yaml and resolve: +Load and read full config from {project-root}/_bmad/bmb/config.yaml and resolve: - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language` diff --git a/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/instructions.md b/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/instructions.md index f3a4602e..55574a3a 100644 --- a/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/instructions.md +++ b/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/instructions.md @@ -1,4 +1,4 @@ -The workflow execution engine is governed by: {project_root}/\_bmad/core/tasks/workflow.xml +The workflow execution engine is governed by: {project_root}/_bmad/core/tasks/workflow.xml You MUST have already loaded and processed: {installed_path}/workflow.yaml Communicate all responses in {communication_language} This is a meta-workflow that orchestrates the CIS brainstorming workflow with game-specific context and additional game design techniques diff --git a/src/modules/bmgd/workflows/1-preproduction/game-brief/instructions.md b/src/modules/bmgd/workflows/1-preproduction/game-brief/instructions.md index 291a2952..cf17000e 100644 --- a/src/modules/bmgd/workflows/1-preproduction/game-brief/instructions.md +++ b/src/modules/bmgd/workflows/1-preproduction/game-brief/instructions.md @@ -1,6 +1,6 @@ # Game Brief - Interactive Workflow Instructions -The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml +The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml You MUST have already loaded and processed: {installed_path}/workflow.yaml Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level} Generate all documents in {document_output_language} diff --git a/src/modules/bmgd/workflows/2-design/narrative/instructions-narrative.md b/src/modules/bmgd/workflows/2-design/narrative/instructions-narrative.md index 12cbe75c..d47263ea 100644 --- a/src/modules/bmgd/workflows/2-design/narrative/instructions-narrative.md +++ b/src/modules/bmgd/workflows/2-design/narrative/instructions-narrative.md @@ -2,7 +2,7 @@ -The workflow execution engine is governed by: {project_root}/\_bmad/core/tasks/workflow.xml +The workflow execution engine is governed by: {project_root}/_bmad/core/tasks/workflow.xml You MUST have already completed the GDD workflow Communicate all responses in {communication_language} This workflow creates detailed narrative content for story-driven games diff --git a/src/modules/bmgd/workflows/3-technical/game-architecture/instructions.md b/src/modules/bmgd/workflows/3-technical/game-architecture/instructions.md index 673ed07e..e59e7c69 100644 --- a/src/modules/bmgd/workflows/3-technical/game-architecture/instructions.md +++ b/src/modules/bmgd/workflows/3-technical/game-architecture/instructions.md @@ -2,7 +2,7 @@ -The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml +The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml You MUST have already loaded and processed: {installed_path}/workflow.yaml This workflow uses ADAPTIVE FACILITATION - adjust your communication style based on {user_skill_level} The goal is ARCHITECTURAL DECISIONS that prevent AI agent conflicts, not detailed implementation specs diff --git a/src/modules/bmgd/workflows/3-technical/generate-project-context/steps/step-02-generate.md b/src/modules/bmgd/workflows/3-technical/generate-project-context/steps/step-02-generate.md index 75e978cb..90c76f2b 100644 --- a/src/modules/bmgd/workflows/3-technical/generate-project-context/steps/step-02-generate.md +++ b/src/modules/bmgd/workflows/3-technical/generate-project-context/steps/step-02-generate.md @@ -28,8 +28,8 @@ This step will generate content and present choices for each rule category: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode +- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed - User accepts/rejects protocol changes before proceeding diff --git a/src/modules/bmgd/workflows/4-production/correct-course/checklist.md b/src/modules/bmgd/workflows/4-production/correct-course/checklist.md index 06f7c4f6..1eb33830 100644 --- a/src/modules/bmgd/workflows/4-production/correct-course/checklist.md +++ b/src/modules/bmgd/workflows/4-production/correct-course/checklist.md @@ -1,6 +1,6 @@ # Change Navigation Checklist -This checklist is executed as part of: {project-root}/\_bmad/bmgd/workflows/4-production/correct-course/workflow.yaml +This checklist is executed as part of: {project-root}/_bmad/bmgd/workflows/4-production/correct-course/workflow.yaml Work through each section systematically with the user, recording findings and impacts diff --git a/src/modules/bmgd/workflows/4-production/correct-course/instructions.md b/src/modules/bmgd/workflows/4-production/correct-course/instructions.md index 6e3f0419..1eb776c3 100644 --- a/src/modules/bmgd/workflows/4-production/correct-course/instructions.md +++ b/src/modules/bmgd/workflows/4-production/correct-course/instructions.md @@ -1,7 +1,7 @@ # Correct Course - Sprint Change Management Instructions -The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml -You MUST have already loaded and processed: {project-root}/\_bmad/bmgd/workflows/4-production/correct-course/workflow.yaml +The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project-root}/_bmad/bmgd/workflows/4-production/correct-course/workflow.yaml Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level} Generate all documents in {document_output_language} diff --git a/src/modules/bmgd/workflows/4-production/retrospective/instructions.md b/src/modules/bmgd/workflows/4-production/retrospective/instructions.md index 87419473..01352cfc 100644 --- a/src/modules/bmgd/workflows/4-production/retrospective/instructions.md +++ b/src/modules/bmgd/workflows/4-production/retrospective/instructions.md @@ -1,7 +1,7 @@ # Retrospective - Epic Completion Review Instructions -The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml -You MUST have already loaded and processed: {project-root}/\_bmad/bmgd/workflows/4-production/retrospective/workflow.yaml +The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project-root}/_bmad/bmgd/workflows/4-production/retrospective/workflow.yaml Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level} Generate all documents in {document_output_language} ⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. diff --git a/src/modules/bmgd/workflows/4-production/sprint-planning/instructions.md b/src/modules/bmgd/workflows/4-production/sprint-planning/instructions.md index ab959d2b..9ec3fe12 100644 --- a/src/modules/bmgd/workflows/4-production/sprint-planning/instructions.md +++ b/src/modules/bmgd/workflows/4-production/sprint-planning/instructions.md @@ -1,7 +1,7 @@ # Sprint Planning - Sprint Status Generator -The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml -You MUST have already loaded and processed: {project-root}/\_bmad/bmgd/workflows/4-production/sprint-planning/workflow.yaml +The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project-root}/_bmad/bmgd/workflows/4-production/sprint-planning/workflow.yaml ## πŸ“š Document Discovery - Full Epic Loading diff --git a/src/modules/bmgd/workflows/4-production/sprint-status/instructions.md b/src/modules/bmgd/workflows/4-production/sprint-status/instructions.md index b38e441c..e160775e 100644 --- a/src/modules/bmgd/workflows/4-production/sprint-status/instructions.md +++ b/src/modules/bmgd/workflows/4-production/sprint-status/instructions.md @@ -1,7 +1,7 @@ # Sprint Status - Multi-Mode Service -The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml -You MUST have already loaded and processed: {project-root}/\_bmad/bmgd/workflows/4-production/sprint-status/workflow.yaml +The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project-root}/_bmad/bmgd/workflows/4-production/sprint-status/workflow.yaml Modes: interactive (default), validate, data ⚠️ ABSOLUTELY NO TIME ESTIMATES. Do NOT mention hours, days, weeks, or timelines. diff --git a/src/modules/bmgd/workflows/workflow-status/init/instructions.md b/src/modules/bmgd/workflows/workflow-status/init/instructions.md index 6d6f1d23..57cae373 100644 --- a/src/modules/bmgd/workflows/workflow-status/init/instructions.md +++ b/src/modules/bmgd/workflows/workflow-status/init/instructions.md @@ -1,6 +1,6 @@ # Workflow Init - Game Project Setup Instructions -The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml +The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml You MUST have already loaded and processed: workflow-init/workflow.yaml Communicate in {communication_language} with {user_name} This workflow handles BOTH new game projects AND existing game projects diff --git a/src/modules/bmgd/workflows/workflow-status/instructions.md b/src/modules/bmgd/workflows/workflow-status/instructions.md index 20dd846a..ae95e313 100644 --- a/src/modules/bmgd/workflows/workflow-status/instructions.md +++ b/src/modules/bmgd/workflows/workflow-status/instructions.md @@ -1,7 +1,7 @@ # Workflow Status Check - Multi-Mode Service (BMGD) -The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml -You MUST have already loaded and processed: {project-root}/\_bmad/bmgd/workflows/workflow-status/workflow.yaml +The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project-root}/_bmad/bmgd/workflows/workflow-status/workflow.yaml This workflow operates in multiple modes: interactive (default), validate, data, init-check, update Other workflows can call this as a service to avoid duplicating status logic ⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. diff --git a/src/modules/bmm/workflows/1-analysis/create-product-brief/workflow.md b/src/modules/bmm/workflows/1-analysis/create-product-brief/workflow.md index afb92d96..0cbcca44 100644 --- a/src/modules/bmm/workflows/1-analysis/create-product-brief/workflow.md +++ b/src/modules/bmm/workflows/1-analysis/create-product-brief/workflow.md @@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution: ### 1. Configuration Loading -Load and read full config from {project-root}/\_bmad/bmm/config.yaml and resolve: +Load and read full config from {project-root}/_bmad/bmm/config.yaml and resolve: - `project_name`, `output_folder`, `planning_artifacts`, `user_name`, `communication_language`, `document_output_language`, `user_skill_level` diff --git a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-02-discovery.md b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-02-discovery.md index f42a4c1f..ce6f8ea8 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-02-discovery.md +++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-02-discovery.md @@ -29,8 +29,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding diff --git a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-03-core-experience.md b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-03-core-experience.md index e3fe2c27..ac4bc45e 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-03-core-experience.md +++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-03-core-experience.md @@ -29,8 +29,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -160,7 +160,7 @@ Show the generated core experience content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current core experience content +- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current core experience content - Process the enhanced experience insights that come back - Ask user: "Accept these improvements to the core experience definition? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -168,7 +168,7 @@ Show the generated core experience content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current core experience definition +- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current core experience definition - Process the collaborative experience improvements that come back - Ask user: "Accept these changes to the core experience definition? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-04-emotional-response.md b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-04-emotional-response.md index 12f13976..165b20ba 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-04-emotional-response.md +++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-04-emotional-response.md @@ -29,8 +29,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -163,7 +163,7 @@ Show the generated emotional response content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current emotional response content +- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current emotional response content - Process the enhanced emotional insights that come back - Ask user: "Accept these improvements to the emotional response definition? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -171,7 +171,7 @@ Show the generated emotional response content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current emotional response definition +- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current emotional response definition - Process the collaborative emotional insights that come back - Ask user: "Accept these changes to the emotional response definition? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-05-inspiration.md b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-05-inspiration.md index 45d4183a..a98b0bbc 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-05-inspiration.md +++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-05-inspiration.md @@ -29,8 +29,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -178,7 +178,7 @@ Show the generated inspiration analysis content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current inspiration analysis content +- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current inspiration analysis content - Process the enhanced pattern insights that come back - Ask user: "Accept these improvements to the inspiration analysis? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -186,7 +186,7 @@ Show the generated inspiration analysis content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current inspiration analysis +- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current inspiration analysis - Process the collaborative pattern insights that come back - Ask user: "Accept these changes to the inspiration analysis? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-06-design-system.md b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-06-design-system.md index e0773f39..e0f0741d 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-06-design-system.md +++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-06-design-system.md @@ -29,8 +29,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -196,7 +196,7 @@ Show the generated design system content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current design system content +- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current design system content - Process the enhanced design system insights that come back - Ask user: "Accept these improvements to the design system decision? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -204,7 +204,7 @@ Show the generated design system content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current design system choice +- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current design system choice - Process the collaborative design system insights that come back - Ask user: "Accept these changes to the design system decision? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-07-defining-experience.md b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-07-defining-experience.md index adb4380e..d2afb46c 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-07-defining-experience.md +++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-07-defining-experience.md @@ -29,8 +29,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -198,7 +198,7 @@ Show the generated defining experience content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current defining experience content +- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current defining experience content - Process the enhanced experience insights that come back - Ask user: "Accept these improvements to the defining experience? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -206,7 +206,7 @@ Show the generated defining experience content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current defining experience +- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current defining experience - Process the collaborative experience insights that come back - Ask user: "Accept these changes to the defining experience? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-08-visual-foundation.md b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-08-visual-foundation.md index 7d02f67c..d9445771 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-08-visual-foundation.md +++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-08-visual-foundation.md @@ -29,8 +29,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -168,7 +168,7 @@ Show the generated visual foundation content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current visual foundation content +- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current visual foundation content - Process the enhanced visual insights that come back - Ask user: "Accept these improvements to the visual foundation? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -176,7 +176,7 @@ Show the generated visual foundation content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current visual foundation +- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current visual foundation - Process the collaborative visual insights that come back - Ask user: "Accept these changes to the visual foundation? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-09-design-directions.md b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-09-design-directions.md index ad0b5b66..188a31ed 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-09-design-directions.md +++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-09-design-directions.md @@ -29,8 +29,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -168,7 +168,7 @@ Show the generated design direction content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current design direction content +- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current design direction content - Process the enhanced design insights that come back - Ask user: "Accept these improvements to the design direction? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -176,7 +176,7 @@ Show the generated design direction content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current design direction +- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current design direction - Process the collaborative design insights that come back - Ask user: "Accept these changes to the design direction? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-10-user-journeys.md b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-10-user-journeys.md index 1392c4bf..81816ec0 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-10-user-journeys.md +++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-10-user-journeys.md @@ -29,8 +29,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -186,7 +186,7 @@ Show the generated user journey content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current user journey content +- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current user journey content - Process the enhanced journey insights that come back - Ask user: "Accept these improvements to the user journeys? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -194,7 +194,7 @@ Show the generated user journey content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current user journeys +- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current user journeys - Process the collaborative journey insights that come back - Ask user: "Accept these changes to the user journeys? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-11-component-strategy.md b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-11-component-strategy.md index 3cb00b2e..d84059e2 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-11-component-strategy.md +++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-11-component-strategy.md @@ -29,8 +29,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -192,7 +192,7 @@ Show the generated component strategy content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current component strategy content +- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current component strategy content - Process the enhanced component insights that come back - Ask user: "Accept these improvements to the component strategy? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -200,7 +200,7 @@ Show the generated component strategy content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current component strategy +- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current component strategy - Process the collaborative component insights that come back - Ask user: "Accept these changes to the component strategy? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-12-ux-patterns.md b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-12-ux-patterns.md index 36091dcf..cabea2bb 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-12-ux-patterns.md +++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-12-ux-patterns.md @@ -29,8 +29,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -181,7 +181,7 @@ Show the generated UX patterns content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current UX patterns content +- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current UX patterns content - Process the enhanced pattern insights that come back - Ask user: "Accept these improvements to the UX patterns? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -189,7 +189,7 @@ Show the generated UX patterns content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current UX patterns +- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current UX patterns - Process the collaborative pattern insights that come back - Ask user: "Accept these changes to the UX patterns? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-13-responsive-accessibility.md b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-13-responsive-accessibility.md index c636cdc9..9f3a0c70 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-13-responsive-accessibility.md +++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-13-responsive-accessibility.md @@ -29,8 +29,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -208,7 +208,7 @@ Show the generated responsive and accessibility content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current responsive/accessibility content +- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current responsive/accessibility content - Process the enhanced insights that come back - Ask user: "Accept these improvements to the responsive/accessibility strategy? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -216,7 +216,7 @@ Show the generated responsive and accessibility content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current responsive/accessibility strategy +- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current responsive/accessibility strategy - Process the collaborative insights that come back - Ask user: "Accept these changes to the responsive/accessibility strategy? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-03-success.md b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-03-success.md index 5ebe63d2..29ea708c 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-03-success.md +++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-03-success.md @@ -49,8 +49,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -228,7 +228,7 @@ Show the generated content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current success criteria content +- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current success criteria content - Process the enhanced success metrics that come back - Ask user: "Accept these improvements to the success criteria? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -236,7 +236,7 @@ Show the generated content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current success criteria +- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current success criteria - Process the collaborative improvements to metrics and scope - Ask user: "Accept these changes to the success criteria? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-04-journeys.md b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-04-journeys.md index 5fb0a855..095480d1 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-04-journeys.md +++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-04-journeys.md @@ -49,8 +49,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -222,7 +222,7 @@ Show the generated journey content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current journey content +- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current journey content - Process the enhanced journey insights that come back - Ask user: "Accept these improvements to the user journeys? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -230,7 +230,7 @@ Show the generated journey content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current journeys +- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current journeys - Process the collaborative journey improvements and additions - Ask user: "Accept these changes to the user journeys? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-05-domain.md b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-05-domain.md index 1fe4192d..e050af3e 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-05-domain.md +++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-05-domain.md @@ -52,8 +52,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -207,7 +207,7 @@ Show the generated domain content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current domain content +- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current domain content - Process the enhanced domain insights that come back - Ask user: "Accept these domain requirement improvements? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -215,7 +215,7 @@ Show the generated domain content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current domain requirements +- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current domain requirements - Process the collaborative domain expertise and validation - Ask user: "Accept these changes to domain requirements? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md index 9630d333..709edad2 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md +++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md @@ -52,8 +52,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -186,7 +186,7 @@ Show the generated innovation content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current innovation content +- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current innovation content - Process the enhanced innovation insights that come back - Ask user: "Accept these improvements to the innovation analysis? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -194,7 +194,7 @@ Show the generated innovation content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current innovation content +- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current innovation content - Process the collaborative innovation exploration and ideation - Ask user: "Accept these changes to the innovation analysis? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md index 5b234de0..adca0967 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md +++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md @@ -52,8 +52,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -182,7 +182,7 @@ Show the generated project-type content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current project-type content +- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current project-type content - Process the enhanced technical insights that come back - Ask user: "Accept these improvements to the technical requirements? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -190,7 +190,7 @@ Show the generated project-type content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current project-type requirements +- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current project-type requirements - Process the collaborative technical expertise and validation - Ask user: "Accept these changes to the technical requirements? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-08-scoping.md b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-08-scoping.md index 34f8e1c4..ca03d214 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-08-scoping.md +++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-08-scoping.md @@ -50,8 +50,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed - User accepts/rejects protocol changes before proceeding @@ -243,7 +243,7 @@ Show the scoping decisions and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with current scoping analysis +- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with current scoping analysis - Process enhanced scoping insights that come back - Ask user: "Accept these improvements to the scoping decisions? (y/n)" - If yes: Update content, then return to A/P/C menu @@ -251,7 +251,7 @@ Show the scoping decisions and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with scoping context +- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with scoping context - Process collaborative insights on MVP and roadmap decisions - Ask user: "Accept these changes to the scoping decisions? (y/n)" - If yes: Update content, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-09-functional.md b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-09-functional.md index de3ff379..5d8df8bd 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-09-functional.md +++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-09-functional.md @@ -49,8 +49,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -209,7 +209,7 @@ Show the generated functional requirements and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current FR list +- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current FR list - Process the enhanced capability coverage that comes back - Ask user: "Accept these additions to the functional requirements? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -217,7 +217,7 @@ Show the generated functional requirements and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current FR list +- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current FR list - Process the collaborative capability validation and additions - Ask user: "Accept these changes to the functional requirements? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-10-nonfunctional.md b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-10-nonfunctional.md index 4a0793b3..4982519f 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-10-nonfunctional.md +++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-10-nonfunctional.md @@ -49,8 +49,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -209,7 +209,7 @@ Show the generated NFR content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current NFR content +- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current NFR content - Process the enhanced quality attribute insights that come back - Ask user: "Accept these improvements to the non-functional requirements? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -217,7 +217,7 @@ Show the generated NFR content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current NFR list +- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current NFR list - Process the collaborative technical validation and additions - Ask user: "Accept these changes to the non-functional requirements? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md b/src/modules/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md index 0a266eb7..11ac56bb 100644 --- a/src/modules/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md +++ b/src/modules/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md @@ -45,7 +45,7 @@ web_bundle: false ### 1. Module Configuration Loading -Load and read full config from {project-root}/\_bmad/bmm/config.yaml and resolve: +Load and read full config from {project-root}/_bmad/bmm/config.yaml and resolve: - `project_name`, `output_folder`, `planning_artifacts`, `user_name`, `communication_language`, `document_output_language` diff --git a/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-02-context.md b/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-02-context.md index cb6d83d6..84b34629 100644 --- a/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-02-context.md +++ b/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-02-context.md @@ -30,8 +30,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed - User accepts/rejects protocol changes before proceeding @@ -169,7 +169,7 @@ Show the generated content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current context analysis +- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current context analysis - Process the enhanced architectural insights that come back - Ask user: "Accept these enhancements to the project context analysis? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -177,7 +177,7 @@ Show the generated content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current project context +- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current project context - Process the collaborative improvements to architectural understanding - Ask user: "Accept these changes to the project context analysis? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-03-starter.md b/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-03-starter.md index 02f44275..7480b79e 100644 --- a/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-03-starter.md +++ b/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-03-starter.md @@ -30,8 +30,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed - User accepts/rejects protocol changes before proceeding diff --git a/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-04-decisions.md b/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-04-decisions.md index b1a580ca..1b145cfd 100644 --- a/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-04-decisions.md +++ b/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-04-decisions.md @@ -31,8 +31,8 @@ This step will generate content and present choices for each decision category: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed - User accepts/rejects protocol changes before proceeding @@ -263,7 +263,7 @@ Show the generated decisions content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with specific decision categories +- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with specific decision categories - Process enhanced insights about particular decisions - Ask user: "Accept these enhancements to the architectural decisions? (y/n)" - If yes: Update content, then return to A/P/C menu @@ -271,7 +271,7 @@ Show the generated decisions content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with architectural decisions context +- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with architectural decisions context - Process collaborative insights about decision trade-offs - Ask user: "Accept these changes to the architectural decisions? (y/n)" - If yes: Update content, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-05-patterns.md b/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-05-patterns.md index 68b13e53..ec5a85a6 100644 --- a/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-05-patterns.md +++ b/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-05-patterns.md @@ -31,8 +31,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed - User accepts/rejects protocol changes before proceeding @@ -304,7 +304,7 @@ Show the generated patterns content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with current patterns +- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with current patterns - Process enhanced consistency rules that come back - Ask user: "Accept these additional pattern refinements? (y/n)" - If yes: Update content, then return to A/P/C menu @@ -312,7 +312,7 @@ Show the generated patterns content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with implementation patterns context +- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with implementation patterns context - Process collaborative insights about potential conflicts - Ask user: "Accept these changes to the implementation patterns? (y/n)" - If yes: Update content, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-06-structure.md b/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-06-structure.md index e9be2cc0..9628ad18 100644 --- a/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-06-structure.md +++ b/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-06-structure.md @@ -31,8 +31,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed - User accepts/rejects protocol changes before proceeding @@ -324,7 +324,7 @@ Show the generated project structure content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with current project structure +- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with current project structure - Process enhanced organizational insights that come back - Ask user: "Accept these changes to the project structure? (y/n)" - If yes: Update content, then return to A/P/C menu @@ -332,7 +332,7 @@ Show the generated project structure content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with project structure context +- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with project structure context - Process collaborative insights about organization trade-offs - Ask user: "Accept these changes to the project structure? (y/n)" - If yes: Update content, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-07-validation.md b/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-07-validation.md index 4c68d449..aa6d8e38 100644 --- a/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-07-validation.md +++ b/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-07-validation.md @@ -31,8 +31,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed - User accepts/rejects protocol changes before proceeding @@ -304,7 +304,7 @@ Show the validation results and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with validation issues +- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with validation issues - Process enhanced solutions for complex concerns - Ask user: "Accept these architectural improvements? (y/n)" - If yes: Update content, then return to A/P/C menu @@ -312,7 +312,7 @@ Show the validation results and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with validation context +- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with validation context - Process collaborative insights on implementation readiness - Ask user: "Accept these changes to the validation results? (y/n)" - If yes: Update content, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md b/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md index e0a595bb..dee834f5 100644 --- a/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md +++ b/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md @@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution: ### 1. Configuration Loading -Load and read full config from {project-root}/\_bmad/bmm/config.yaml and resolve: +Load and read full config from {project-root}/_bmad/bmm/config.yaml and resolve: - `project_name`, `output_folder`, `planning_artifacts`, `user_name`, `communication_language`, `document_output_language` diff --git a/src/modules/bmm/workflows/4-implementation/correct-course/checklist.md b/src/modules/bmm/workflows/4-implementation/correct-course/checklist.md index 76d4a827..68a0a445 100644 --- a/src/modules/bmm/workflows/4-implementation/correct-course/checklist.md +++ b/src/modules/bmm/workflows/4-implementation/correct-course/checklist.md @@ -1,6 +1,6 @@ # Change Navigation Checklist -This checklist is executed as part of: {project-root}/\_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml +This checklist is executed as part of: {project-root}/_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml Work through each section systematically with the user, recording findings and impacts diff --git a/src/modules/bmm/workflows/4-implementation/correct-course/instructions.md b/src/modules/bmm/workflows/4-implementation/correct-course/instructions.md index 95a7ea51..82e8b6a2 100644 --- a/src/modules/bmm/workflows/4-implementation/correct-course/instructions.md +++ b/src/modules/bmm/workflows/4-implementation/correct-course/instructions.md @@ -1,7 +1,7 @@ # Correct Course - Sprint Change Management Instructions -The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml -You MUST have already loaded and processed: {project-root}/\_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml +The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project-root}/_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level} Generate all documents in {document_output_language} diff --git a/src/modules/bmm/workflows/4-implementation/retrospective/instructions.md b/src/modules/bmm/workflows/4-implementation/retrospective/instructions.md index 64e129df..70b1ae80 100644 --- a/src/modules/bmm/workflows/4-implementation/retrospective/instructions.md +++ b/src/modules/bmm/workflows/4-implementation/retrospective/instructions.md @@ -1,7 +1,7 @@ # Retrospective - Epic Completion Review Instructions -The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml -You MUST have already loaded and processed: {project-root}/\_bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml +The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project-root}/_bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level} Generate all documents in {document_output_language} ⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. diff --git a/src/modules/bmm/workflows/4-implementation/sprint-planning/instructions.md b/src/modules/bmm/workflows/4-implementation/sprint-planning/instructions.md index 387fb627..c4f4bd42 100644 --- a/src/modules/bmm/workflows/4-implementation/sprint-planning/instructions.md +++ b/src/modules/bmm/workflows/4-implementation/sprint-planning/instructions.md @@ -1,7 +1,7 @@ # Sprint Planning - Sprint Status Generator -The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml -You MUST have already loaded and processed: {project-root}/\_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml +The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project-root}/_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml ## πŸ“š Document Discovery - Full Epic Loading diff --git a/src/modules/bmm/workflows/4-implementation/sprint-status/instructions.md b/src/modules/bmm/workflows/4-implementation/sprint-status/instructions.md index 593231fc..978b9229 100644 --- a/src/modules/bmm/workflows/4-implementation/sprint-status/instructions.md +++ b/src/modules/bmm/workflows/4-implementation/sprint-status/instructions.md @@ -1,7 +1,7 @@ # Sprint Status - Multi-Mode Service -The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml -You MUST have already loaded and processed: {project-root}/\_bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml +The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project-root}/_bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml Modes: interactive (default), validate, data ⚠️ ABSOLUTELY NO TIME ESTIMATES. Do NOT mention hours, days, weeks, or timelines. diff --git a/src/modules/bmm/workflows/document-project/instructions.md b/src/modules/bmm/workflows/document-project/instructions.md index ee3a09ca..f2482775 100644 --- a/src/modules/bmm/workflows/document-project/instructions.md +++ b/src/modules/bmm/workflows/document-project/instructions.md @@ -1,7 +1,7 @@ # Document Project Workflow Router -The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml -You MUST have already loaded and processed: {project-root}/\_bmad/bmm/workflows/document-project/workflow.yaml +The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project-root}/_bmad/bmm/workflows/document-project/workflow.yaml Communicate all responses in {communication_language} diff --git a/src/modules/bmm/workflows/generate-project-context/steps/step-02-generate.md b/src/modules/bmm/workflows/generate-project-context/steps/step-02-generate.md index 122bb0e8..587fb741 100644 --- a/src/modules/bmm/workflows/generate-project-context/steps/step-02-generate.md +++ b/src/modules/bmm/workflows/generate-project-context/steps/step-02-generate.md @@ -28,8 +28,8 @@ This step will generate content and present choices for each rule category: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode +- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed - User accepts/rejects protocol changes before proceeding diff --git a/src/modules/bmm/workflows/workflow-status/init/instructions.md b/src/modules/bmm/workflows/workflow-status/init/instructions.md index b925dbbe..51c1b6de 100644 --- a/src/modules/bmm/workflows/workflow-status/init/instructions.md +++ b/src/modules/bmm/workflows/workflow-status/init/instructions.md @@ -1,6 +1,6 @@ # Workflow Init - Project Setup Instructions -The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml +The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml You MUST have already loaded and processed: workflow-init/workflow.yaml Communicate in {communication_language} with {user_name} This workflow handles BOTH new projects AND legacy projects following the BMad Method diff --git a/src/modules/bmm/workflows/workflow-status/instructions.md b/src/modules/bmm/workflows/workflow-status/instructions.md index 28df92b7..9c5b7723 100644 --- a/src/modules/bmm/workflows/workflow-status/instructions.md +++ b/src/modules/bmm/workflows/workflow-status/instructions.md @@ -1,7 +1,7 @@ # Workflow Status Check - Multi-Mode Service -The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml -You MUST have already loaded and processed: {project-root}/\_bmad/bmm/workflows/workflow-status/workflow.yaml +The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project-root}/_bmad/bmm/workflows/workflow-status/workflow.yaml This workflow operates in multiple modes: interactive (default), validate, data, init-check, update Other workflows can call this as a service to avoid duplicating status logic ⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. diff --git a/src/modules/cis/workflows/design-thinking/instructions.md b/src/modules/cis/workflows/design-thinking/instructions.md index 8cc88b60..a1812f6a 100644 --- a/src/modules/cis/workflows/design-thinking/instructions.md +++ b/src/modules/cis/workflows/design-thinking/instructions.md @@ -1,7 +1,7 @@ # Design Thinking Workflow Instructions -The workflow execution engine is governed by: {project_root}/\_bmad/core/tasks/workflow.xml -You MUST have already loaded and processed: {project_root}/\_bmad/cis/workflows/design-thinking/workflow.yaml +The workflow execution engine is governed by: {project_root}/_bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project_root}/_bmad/cis/workflows/design-thinking/workflow.yaml Load and understand design methods from: {design_methods} ⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. ⚠️ CHECKPOINT PROTOCOL: After EVERY tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately β†’ SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) β†’ DISPLAY generated content β†’ PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO β†’ WAIT for user response. Never batch saves or skip checkpoints. diff --git a/src/modules/cis/workflows/innovation-strategy/instructions.md b/src/modules/cis/workflows/innovation-strategy/instructions.md index ef158a85..cf0179a8 100644 --- a/src/modules/cis/workflows/innovation-strategy/instructions.md +++ b/src/modules/cis/workflows/innovation-strategy/instructions.md @@ -1,7 +1,7 @@ # Innovation Strategy Workflow Instructions -The workflow execution engine is governed by: {project_root}/\_bmad/core/tasks/workflow.xml -You MUST have already loaded and processed: {project_root}/\_bmad/cis/workflows/innovation-strategy/workflow.yaml +The workflow execution engine is governed by: {project_root}/_bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project_root}/_bmad/cis/workflows/innovation-strategy/workflow.yaml Load and understand innovation frameworks from: {innovation_frameworks} ⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. ⚠️ CHECKPOINT PROTOCOL: After EVERY tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately β†’ SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) β†’ DISPLAY generated content β†’ PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO β†’ WAIT for user response. Never batch saves or skip checkpoints. diff --git a/src/modules/cis/workflows/problem-solving/instructions.md b/src/modules/cis/workflows/problem-solving/instructions.md index b3c3a7b3..c9ff9343 100644 --- a/src/modules/cis/workflows/problem-solving/instructions.md +++ b/src/modules/cis/workflows/problem-solving/instructions.md @@ -1,7 +1,7 @@ # Problem Solving Workflow Instructions -The workflow execution engine is governed by: {project_root}/\_bmad/core/tasks/workflow.xml -You MUST have already loaded and processed: {project_root}/\_bmad/cis/workflows/problem-solving/workflow.yaml +The workflow execution engine is governed by: {project_root}/_bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project_root}/_bmad/cis/workflows/problem-solving/workflow.yaml Load and understand solving methods from: {solving_methods} ⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. ⚠️ CHECKPOINT PROTOCOL: After EVERY tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately β†’ SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) β†’ DISPLAY generated content β†’ PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO β†’ WAIT for user response. Never batch saves or skip checkpoints.