From 1677d54f2271ebe948022d6fe5132404b254c4b2 Mon Sep 17 00:00:00 2001 From: Chris Chen Date: Sat, 28 Feb 2026 06:03:16 +1100 Subject: [PATCH 1/3] 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/3] 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/3] 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