From 1677d54f2271ebe948022d6fe5132404b254c4b2 Mon Sep 17 00:00:00 2001 From: Chris Chen Date: Sat, 28 Feb 2026 06:03:16 +1100 Subject: [PATCH 1/7] fix: correct docs domain to docs.bmad-method.org (#1777) * fix: correct docs domain to docs.bmad-method.org Fixes BMAD-METHOD#1712 * fix: update all docs.bmad-method.org links to HTTPS - Changed http:// to https:// across README.md and issue templates - Addresses review comments on PR #1776 --------- Co-authored-by: OpenClaw Assistant --- .github/ISSUE_TEMPLATE/config.yaml | 2 +- .github/ISSUE_TEMPLATE/documentation.yaml | 2 +- README.md | 12 ++++++------ tools/cli/installers/install-messages.yaml | 2 +- 4 files changed, 9 insertions(+), 9 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/config.yaml b/.github/ISSUE_TEMPLATE/config.yaml index b4c92ee6c..7e980f119 100644 --- a/.github/ISSUE_TEMPLATE/config.yaml +++ b/.github/ISSUE_TEMPLATE/config.yaml @@ -1,7 +1,7 @@ blank_issues_enabled: false contact_links: - name: 📚 Documentation - url: http://docs.bmad-method.org + url: https://docs.bmad-method.org about: Check the docs first — tutorials, guides, and reference - name: 💬 Discord Community url: https://discord.gg/gk8jAdXWmj diff --git a/.github/ISSUE_TEMPLATE/documentation.yaml b/.github/ISSUE_TEMPLATE/documentation.yaml index 00729a363..6b132c48e 100644 --- a/.github/ISSUE_TEMPLATE/documentation.yaml +++ b/.github/ISSUE_TEMPLATE/documentation.yaml @@ -28,7 +28,7 @@ body: attributes: label: Documentation location description: Where is the documentation that needs improvement? - placeholder: e.g., http://docs.bmad-method.org/tutorials/getting-started/ or "In the README" + placeholder: e.g., https://docs.bmad-method.org/tutorials/getting-started/ or "In the README" validations: required: true diff --git a/README.md b/README.md index 4958c65a1..d4827e378 100644 --- a/README.md +++ b/README.md @@ -20,7 +20,7 @@ Traditional AI tools do the thinking for you, producing average results. BMad ag - **Party Mode** — Bring multiple agent personas into one session to collaborate and discuss - **Complete Lifecycle** — From brainstorming to deployment -[Learn more at **docs.bmad-method.org**](http://docs.bmad-method.org) +[Learn more at **docs.bmad-method.org**](https://docs.bmad-method.org) --- @@ -28,7 +28,7 @@ Traditional AI tools do the thinking for you, producing average results. BMad ag **V6 is here and we're just getting started!** The BMad Method is evolving rapidly with optimizations including Cross Platform Agent Team and Sub Agent inclusion, Skills Architecture, BMad Builder v1, Dev Loop Automation, and so much more in the works. -**[📍 Check out the complete Roadmap →](http://docs.bmad-method.org/roadmap/)** +**[📍 Check out the complete Roadmap →](https://docs.bmad-method.org/roadmap/)** --- @@ -50,7 +50,7 @@ Follow the installer prompts, then open your AI IDE (Claude Code, Cursor, etc.) npx bmad-method install --directory /path/to/project --modules bmm --tools claude-code --yes ``` -[See all installation options](http://docs.bmad-method.org/how-to/non-interactive-installation/) +[See all installation options](https://docs.bmad-method.org/how-to/non-interactive-installation/) > **Not sure what to do?** Run `/bmad-help` — it tells you exactly what's next and what's optional. You can also ask questions like `/bmad-help I just finished the architecture, what do I do next?` @@ -68,11 +68,11 @@ BMad Method extends with official modules for specialized domains. Available dur ## Documentation -[BMad Method Docs Site](http://docs.bmad-method.org) — Tutorials, guides, concepts, and reference +[BMad Method Docs Site](https://docs.bmad-method.org) — Tutorials, guides, concepts, and reference **Quick links:** -- [Getting Started Tutorial](http://docs.bmad-method.org/tutorials/getting-started/) -- [Upgrading from Previous Versions](http://docs.bmad-method.org/how-to/upgrade-to-v6/) +- [Getting Started Tutorial](https://docs.bmad-method.org/tutorials/getting-started/) +- [Upgrading from Previous Versions](https://docs.bmad-method.org/how-to/upgrade-to-v6/) - [Test Architect Documentation](https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise/) diff --git a/tools/cli/installers/install-messages.yaml b/tools/cli/installers/install-messages.yaml index b14265165..0fc32cc82 100644 --- a/tools/cli/installers/install-messages.yaml +++ b/tools/cli/installers/install-messages.yaml @@ -12,7 +12,7 @@ startMessage: | - Select and install modules during setup - customize your experience - New BMad Method for Agile AI-Driven Development (the evolution of V4) - Exciting new modules available during installation, with community modules coming soon - - Documentation: docs.bmad-method.com + - Documentation: https://docs.bmad-method.org 🌟 BMad is 100% free and open source. - No gated Discord. No paywalls. No gated content. From 43cfc01f2c5d24cf2ff604b081278b4e5b69e350 Mon Sep 17 00:00:00 2001 From: Alex Verkhovsky Date: Fri, 27 Feb 2026 22:08:30 -0700 Subject: [PATCH 2/7] feat(core): add edge case hunter review task (#1790) Method-driven review that exhaustively walks branching paths and boundary conditions, reporting only unhandled gaps. Orthogonal to the attitude-driven adversarial review for complementary coverage. --- src/core/module-help.csv | 1 + src/core/tasks/review-edge-case-hunter.xml | 64 ++++++++++++++++++++++ 2 files changed, 65 insertions(+) create mode 100644 src/core/tasks/review-edge-case-hunter.xml diff --git a/src/core/module-help.csv b/src/core/module-help.csv index 1fdf064c4..2e4419599 100644 --- a/src/core/module-help.csv +++ b/src/core/module-help.csv @@ -7,3 +7,4 @@ core,anytime,Shard Document,SD,,_bmad/core/tasks/shard-doc.xml,bmad-shard-doc,fa core,anytime,Editorial Review - Prose,EP,,_bmad/core/tasks/editorial-review-prose.xml,bmad-editorial-review-prose,false,,,"Review prose for clarity, tone, and communication issues. Use after drafting to polish written content.",report located with target document,"three-column markdown table with suggested fixes", core,anytime,Editorial Review - Structure,ES,,_bmad/core/tasks/editorial-review-structure.xml,bmad-editorial-review-structure,false,,,"Propose cuts, reorganization, and simplification while preserving comprehension. Use when doc produced from multiple subprocesses or needs structural improvement.",report located with target document, core,anytime,Adversarial Review (General),AR,,_bmad/core/tasks/review-adversarial-general.xml,bmad-review-adversarial-general,false,,,"Review content critically to find issues and weaknesses. Use for quality assurance or before finalizing deliverables. Code Review in other modules run this automatically, but its useful also for document reviews",, +core,anytime,Edge Case Hunter Review,ECH,,_bmad/core/tasks/review-edge-case-hunter.xml,bmad-review-edge-case-hunter,false,,,"Walk every branching path and boundary condition in code, report only unhandled edge cases. Use alongside adversarial review for orthogonal coverage - method-driven not attitude-driven.",, diff --git a/src/core/tasks/review-edge-case-hunter.xml b/src/core/tasks/review-edge-case-hunter.xml new file mode 100644 index 000000000..6e4e7d285 --- /dev/null +++ b/src/core/tasks/review-edge-case-hunter.xml @@ -0,0 +1,64 @@ + + + + You are a pure path tracer. Never comment on whether code is good or bad; only list missing handling. +When a diff is provided, scan only the diff hunks and list boundaries that are directly reachable from the changed lines and lack an explicit guard in the diff. +When no diff is provided (full file or function), treat the entire provided content as the scope. +Ignore the rest of the codebase unless the provided content explicitly references external functions. + + + + + + + Return ONLY a valid JSON array of objects. Each object must contain exactly these four fields and nothing else: +{ + "location": "file:line", + "trigger_condition": "one-line description (max 15 words)", + "guard_snippet": "minimal code sketch that closes the gap", + "potential_consequence": "what could actually go wrong (max 15 words)" +} +No extra text, no explanations, no markdown wrapping. + + + MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER + DO NOT skip steps or change the sequence + HALT immediately when halt-conditions are met + Each action xml tag within step xml tag is a REQUIRED action to complete that step + + Your method is exhaustive path enumeration — mechanically walk every branch, not hunt by intuition + Trace each branching path: conditionals, switches, early returns, guard clauses, loops, error handlers + Trace each boundary condition: null, undefined, empty, zero, negative, overflow, max-length, type coercion, concurrency, timing + Report ONLY paths and conditions that lack handling — discard handled ones silently + Do NOT editorialize or add filler — findings only + + + + + Load the content to review from provided input or context + If content to review is empty, ask for clarification and abort task + Identify content type (diff, full file, or function) to determine scope rules + + + + Walk every branching path and boundary condition within scope - report only unhandled ones + If also_consider input was provided, incorporate those areas into the analysis + Enumerate all branching paths and boundary conditions within scope: conditionals, switches, early returns, guard clauses, loops, error handlers, null/empty states, overflow, type edges, concurrency, timing + For each path: determine whether the content handles it + Collect only the unhandled paths as findings - discard handled ones silently + + + + Output findings as a JSON array following the output-format specification exactly + + + + + HALT if zero findings - this is suspicious, re-analyze or ask for guidance + HALT if content is empty or unreadable + + + From bc7c7f07570292299f55bce3cdece60f07bfc2e1 Mon Sep 17 00:00:00 2001 From: Alex Verkhovsky Date: Sat, 28 Feb 2026 17:37:13 -0700 Subject: [PATCH 3/7] fix(core): remove zero-findings halt condition from edge case hunter (#1797) The "HALT if zero findings" condition pressures the LLM to hallucinate findings when reviewing trivial diffs with no branching logic. Since this task runs non-interactively as a subagent, it cannot ask for guidance either. Zero findings is a valid outcome for clean code. --- src/core/tasks/review-edge-case-hunter.xml | 1 - 1 file changed, 1 deletion(-) diff --git a/src/core/tasks/review-edge-case-hunter.xml b/src/core/tasks/review-edge-case-hunter.xml index 6e4e7d285..f312e1b2e 100644 --- a/src/core/tasks/review-edge-case-hunter.xml +++ b/src/core/tasks/review-edge-case-hunter.xml @@ -57,7 +57,6 @@ No extra text, no explanations, no markdown wrapping. - HALT if zero findings - this is suspicious, re-analyze or ask for guidance HALT if content is empty or unreadable From d036d34892cbcf87bf46b5d244ce3562957893f4 Mon Sep 17 00:00:00 2001 From: Dicky Moore Date: Sun, 1 Mar 2026 00:49:31 +0000 Subject: [PATCH 4/7] fix(templates): replace @ path prefixes with {project-root} (#1769) Co-authored-by: Brian --- .../installers/lib/ide/templates/agent-command-template.md | 2 +- .../lib/ide/templates/combined/default-workflow-yaml.md | 6 +++--- .../lib/ide/templates/combined/default-workflow.md | 2 +- .../lib/ide/templates/workflow-command-template.md | 4 ++-- .../cli/installers/lib/ide/templates/workflow-commander.md | 2 +- 5 files changed, 8 insertions(+), 8 deletions(-) diff --git a/tools/cli/installers/lib/ide/templates/agent-command-template.md b/tools/cli/installers/lib/ide/templates/agent-command-template.md index 897136317..0f0c2e20d 100644 --- a/tools/cli/installers/lib/ide/templates/agent-command-template.md +++ b/tools/cli/installers/lib/ide/templates/agent-command-template.md @@ -6,7 +6,7 @@ description: '{{description}}' You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command. -1. LOAD the FULL agent file from @_bmad/{{module}}/agents/{{path}} +1. LOAD the FULL agent file from {project-root}/_bmad/{{module}}/agents/{{path}} 2. READ its entire contents - this contains the complete agent persona, menu, and instructions 3. Execute ALL activation steps exactly as written in the agent file 4. Follow the agent's persona and menu system precisely diff --git a/tools/cli/installers/lib/ide/templates/combined/default-workflow-yaml.md b/tools/cli/installers/lib/ide/templates/combined/default-workflow-yaml.md index eca904370..4a8da26e7 100644 --- a/tools/cli/installers/lib/ide/templates/combined/default-workflow-yaml.md +++ b/tools/cli/installers/lib/ide/templates/combined/default-workflow-yaml.md @@ -6,9 +6,9 @@ description: '{{description}}' IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded: -1. Always LOAD the FULL @{project-root}/{{bmadFolderName}}/core/tasks/workflow.xml -2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/{{bmadFolderName}}/{{path}} -3. Pass the yaml path @{project-root}/{{bmadFolderName}}/{{path}} as 'workflow-config' parameter to the workflow.xml instructions +1. Always LOAD the FULL {project-root}/{{bmadFolderName}}/core/tasks/workflow.xml +2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config {project-root}/{{bmadFolderName}}/{{path}} +3. Pass the yaml path {project-root}/{{bmadFolderName}}/{{path}} as 'workflow-config' parameter to the workflow.xml instructions 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions 5. Save outputs after EACH section when generating any documents from templates diff --git a/tools/cli/installers/lib/ide/templates/combined/default-workflow.md b/tools/cli/installers/lib/ide/templates/combined/default-workflow.md index afb0dea58..c8ad40459 100644 --- a/tools/cli/installers/lib/ide/templates/combined/default-workflow.md +++ b/tools/cli/installers/lib/ide/templates/combined/default-workflow.md @@ -3,4 +3,4 @@ name: '{{name}}' description: '{{description}}' --- -IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/{{bmadFolderName}}/{{path}}, READ its entire contents and follow its directions exactly! +IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL {project-root}/{{bmadFolderName}}/{{path}}, READ its entire contents and follow its directions exactly! diff --git a/tools/cli/installers/lib/ide/templates/workflow-command-template.md b/tools/cli/installers/lib/ide/templates/workflow-command-template.md index 5c9e436c7..328983c9e 100644 --- a/tools/cli/installers/lib/ide/templates/workflow-command-template.md +++ b/tools/cli/installers/lib/ide/templates/workflow-command-template.md @@ -5,8 +5,8 @@ description: '{{description}}' IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded: -1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml -2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{{workflow_path}} +1. Always LOAD the FULL {project-root}/_bmad/core/tasks/workflow.xml +2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config {project-root}/{{workflow_path}} 3. Pass the yaml path {{workflow_path}} as 'workflow-config' parameter to the workflow.xml instructions 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions 5. Save outputs after EACH section when generating any documents from templates diff --git a/tools/cli/installers/lib/ide/templates/workflow-commander.md b/tools/cli/installers/lib/ide/templates/workflow-commander.md index 3645c1a2f..66eee15d1 100644 --- a/tools/cli/installers/lib/ide/templates/workflow-commander.md +++ b/tools/cli/installers/lib/ide/templates/workflow-commander.md @@ -2,4 +2,4 @@ description: '{{description}}' --- -IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{{workflow_path}}, READ its entire contents and follow its directions exactly! +IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL {project-root}/{{workflow_path}}, READ its entire contents and follow its directions exactly! From 17fe43845269d63de8833ebf5887f6fe8bd4ee60 Mon Sep 17 00:00:00 2001 From: Brian Madison Date: Sat, 28 Feb 2026 19:16:44 -0600 Subject: [PATCH 5/7] fix brainstorming so that it will not overwrite previous brainstormings, and it will also ask if you want to continue a previous one or start a new one when older brainstormings are found. --- .../steps/step-01-session-setup.md | 49 ++++++++++++------- .../brainstorming/steps/step-01b-continue.md | 2 +- .../steps/step-03-technique-execution.md | 4 +- .../steps/step-04-idea-organization.md | 4 +- src/core/workflows/brainstorming/workflow.md | 4 +- 5 files changed, 39 insertions(+), 24 deletions(-) diff --git a/src/core/workflows/brainstorming/steps/step-01-session-setup.md b/src/core/workflows/brainstorming/steps/step-01-session-setup.md index 7e1cb2cdb..cf970e3f7 100644 --- a/src/core/workflows/brainstorming/steps/step-01-session-setup.md +++ b/src/core/workflows/brainstorming/steps/step-01-session-setup.md @@ -29,23 +29,30 @@ Initialize the brainstorming workflow by detecting continuation state and settin ## INITIALIZATION SEQUENCE: -### 1. Check for Existing Workflow +### 1. Check for Existing Sessions -First, check if the output document already exists: +First, check the brainstorming sessions folder for existing sessions: -- Look for file at `{output_folder}/brainstorming/brainstorming-session-{{date}}.md` -- If exists, read the complete file including frontmatter -- If not exists, this is a fresh workflow +- List all files in `{output_folder}/brainstorming/` +- **DO NOT read any file contents** - only list filenames +- If files exist, identify the most recent by date/time in the filename +- If no files exist, this is a fresh workflow -### 2. Handle Continuation (If Document Exists) +### 2. Handle Existing Sessions (If Files Found) -If the document exists and has frontmatter with `stepsCompleted`: +If existing session files are found: -- **STOP here** and load `./step-01b-continue.md` immediately -- Do not proceed with any initialization tasks -- Let step-01b handle the continuation logic +- Display the most recent session filename (do NOT read its content) +- Ask the user: "Found existing session: `[filename]`. Would you like to: + **[1]** Continue this session + **[2]** Start a new session + **[3]** See all existing sessions" -### 3. Fresh Workflow Setup (If No Document) +- If user selects **[1]** (continue): Set `{brainstorming_session_output_file}` to that file path and load `./step-01b-continue.md` +- If user selects **[2]** (new): Generate new filename with current date/time and proceed to step 3 +- If user selects **[3]** (see all): List all session filenames and ask which to continue or if new + +### 3. Fresh Workflow Setup (If No Files or User Chooses New) If no document exists or no `stepsCompleted` in frontmatter: @@ -55,10 +62,10 @@ Create the brainstorming session document: ```bash # Create directory if needed -mkdir -p "$(dirname "{output_folder}/brainstorming/brainstorming-session-{{date}}.md")" +mkdir -p "$(dirname "{brainstorming_session_output_file}")" # Initialize from template -cp "{template_path}" "{output_folder}/brainstorming/brainstorming-session-{{date}}.md" +cp "{template_path}" "{brainstorming_session_output_file}" ``` #### B. Context File Check and Loading @@ -134,7 +141,7 @@ _[Content based on conversation about session parameters and facilitator approac ## APPEND TO DOCUMENT: -When user selects approach, append the session overview content directly to `{output_folder}/brainstorming/brainstorming-session-{{date}}.md` using the structure from above. +When user selects approach, append the session overview content directly to `{brainstorming_session_output_file}` using the structure from above. ### E. Continue to Technique Selection @@ -152,7 +159,7 @@ Which approach appeals to you most? (Enter 1-4)" #### When user selects approach number: -- **Append initial session overview to `{output_folder}/brainstorming/brainstorming-session-{{date}}.md`** +- **Append initial session overview to `{brainstorming_session_output_file}`** - **Update frontmatter:** `stepsCompleted: [1]`, `selected_approach: '[selected approach]'` - **Load the appropriate step-02 file** based on selection @@ -167,7 +174,9 @@ After user selects approach number: ## SUCCESS METRICS: -✅ Existing workflow detected and continuation handled properly +✅ Existing sessions detected without reading file contents +✅ User prompted to continue existing session or start new +✅ Correct session file selected for continuation ✅ Fresh workflow initialized with correct document structure ✅ Session context gathered and understood clearly ✅ User's approach selection captured and routed correctly @@ -176,7 +185,9 @@ After user selects approach number: ## FAILURE MODES: -❌ Not checking for existing document before creating new one +❌ Reading file contents during session detection (wastes context) +❌ Not asking user before continuing existing session +❌ Not properly routing user's continue/new session selection ❌ Missing continuation detection leading to duplicate work ❌ Insufficient session context gathering ❌ Not properly routing user's approach selection @@ -184,7 +195,9 @@ After user selects approach number: ## SESSION SETUP PROTOCOLS: -- Always verify document existence before initialization +- Always list sessions folder WITHOUT reading file contents +- Ask user before continuing any existing session +- Only load continue step after user confirms - Load brain techniques CSV only when needed for technique presentation - Use collaborative facilitation language throughout - Maintain psychological safety for creative exploration diff --git a/src/core/workflows/brainstorming/steps/step-01b-continue.md b/src/core/workflows/brainstorming/steps/step-01b-continue.md index 23205c0d4..9b7e5968c 100644 --- a/src/core/workflows/brainstorming/steps/step-01b-continue.md +++ b/src/core/workflows/brainstorming/steps/step-01b-continue.md @@ -35,7 +35,7 @@ Load existing document and analyze current state: **Document Analysis:** -- Read existing `{output_folder}/brainstorming/brainstorming-session-{{date}}.md` +- Read existing `{brainstorming_session_output_file}` - Examine frontmatter for `stepsCompleted`, `session_topic`, `session_goals` - Review content to understand session progress and outcomes - Identify current stage and next logical steps diff --git a/src/core/workflows/brainstorming/steps/step-03-technique-execution.md b/src/core/workflows/brainstorming/steps/step-03-technique-execution.md index 362bead3b..59388e1aa 100644 --- a/src/core/workflows/brainstorming/steps/step-03-technique-execution.md +++ b/src/core/workflows/brainstorming/steps/step-03-technique-execution.md @@ -296,7 +296,7 @@ After final technique element: #### If 'C' (Move to organization): -- **Append the technique execution content to `{output_folder}/brainstorming/brainstorming-session-{{date}}.md`** +- **Append the technique execution content to `{brainstorming_session_output_file}`** - **Update frontmatter:** `stepsCompleted: [1, 2, 3]` - **Load:** `./step-04-idea-organization.md` @@ -356,7 +356,7 @@ _[Short narrative describing the user and AI collaboration journey - what made t ## APPEND TO DOCUMENT: -When user selects 'C', append the content directly to `{output_folder}/brainstorming/brainstorming-session-{{date}}.md` using the structure from above. +When user selects 'C', append the content directly to `{brainstorming_session_output_file}` using the structure from above. ## SUCCESS METRICS: diff --git a/src/core/workflows/brainstorming/steps/step-04-idea-organization.md b/src/core/workflows/brainstorming/steps/step-04-idea-organization.md index afe56ff77..74e7faeb8 100644 --- a/src/core/workflows/brainstorming/steps/step-04-idea-organization.md +++ b/src/core/workflows/brainstorming/steps/step-04-idea-organization.md @@ -253,14 +253,14 @@ Provide final session wrap-up and forward guidance: #### If [C] Complete: -- **Append the final session content to `{output_folder}/brainstorming/brainstorming-session-{{date}}.md`** +- **Append the final session content to `{brainstorming_session_output_file}`** - Update frontmatter: `stepsCompleted: [1, 2, 3, 4]` - Set `session_active: false` and `workflow_completed: true` - Complete workflow with positive closure message ## APPEND TO DOCUMENT: -When user selects 'C', append the content directly to `{output_folder}/brainstorming/brainstorming-session-{{date}}.md` using the structure from step 7. +When user selects 'C', append the content directly to `{brainstorming_session_output_file}` using the structure from step 7. ## SUCCESS METRICS: diff --git a/src/core/workflows/brainstorming/workflow.md b/src/core/workflows/brainstorming/workflow.md index c8baf457e..81bc1b2a1 100644 --- a/src/core/workflows/brainstorming/workflow.md +++ b/src/core/workflows/brainstorming/workflow.md @@ -45,7 +45,9 @@ Load config from `{project-root}/_bmad/core/config.yaml` and resolve: - `installed_path` = `{project-root}/_bmad/core/workflows/brainstorming` - `template_path` = `{installed_path}/template.md` - `brain_techniques_path` = `{installed_path}/brain-methods.csv` -- `default_output_file` = `{output_folder}/brainstorming/brainstorming-session-{{date}}.md` +- `brainstorming_session_output_file` = `{output_folder}/brainstorming/brainstorming-session-{{date}}-{{time}}.md` (evaluated once at workflow start) + +All steps MUST reference `{brainstorming_session_output_file}` instead of the full path pattern. - `context_file` = Optional context file path from workflow invocation for project-specific guidance - `advancedElicitationTask` = `{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml` From deedf18fc56ceb658d6c1929b700ae1ef139ca1f Mon Sep 17 00:00:00 2001 From: Brian Madison Date: Sat, 28 Feb 2026 19:20:28 -0600 Subject: [PATCH 6/7] changelog: prepare v6.0.4 release --- CHANGELOG.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 65812c0a4..03e191434 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,20 @@ # Changelog +## [6.0.4] + +### 🎁 Features + +* Add edge case hunter review task - new reusable review task that exhaustively traces branching paths and boundary conditions in code, reporting only unhandled gaps. Method-driven analysis complementary to adversarial review (#1790) + +### 🐛 Bug Fixes + +* Fix brainstorming to not overwrite previous sessions; now prompts to continue existing brainstorming or start a new one when older brainstorming sessions are found +* Fix installer templates - replace legacy `@` path prefixes with explicit `{project-root}` syntax for consistency (#1769) +* Fix edge case hunter - remove zero-findings halt condition that was pressuring the LLM to hallucinate findings when none legitimately exist (#1797) +* Fix broken docs domain references in README and GitHub issue templates (#1777) + +--- + ## [6.0.3] ### 🎁 Features From 44972d62b907459e4a4d8c526db2e899dd628511 Mon Sep 17 00:00:00 2001 From: Brian Madison Date: Sat, 28 Feb 2026 19:20:45 -0600 Subject: [PATCH 7/7] chore(release): bump to v6.0.4 --- package-lock.json | 4 ++-- package.json | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/package-lock.json b/package-lock.json index 2ffca11a6..450469c4d 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "bmad-method", - "version": "6.0.3", + "version": "6.0.4", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "bmad-method", - "version": "6.0.3", + "version": "6.0.4", "license": "MIT", "dependencies": { "@clack/core": "^1.0.0", diff --git a/package.json b/package.json index 773c5704f..f3207f5fa 100644 --- a/package.json +++ b/package.json @@ -1,7 +1,7 @@ { "$schema": "https://json.schemastore.org/package.json", "name": "bmad-method", - "version": "6.0.3", + "version": "6.0.4", "description": "Breakthrough Method of Agile AI-driven Development", "keywords": [ "agile",