Merge remote-tracking branch 'bmad-upstream/main' into i18n/fr_FR

chore(release): v6.8.0 [skip ci]
docs(changelog): v6.8.0 release notes (#2427 )
2026-05-26 01:15:24 +02:00 · 2026-05-25 21:47:24 +00:00 · 2026-05-25 16:46:38 -05:00 · 2026-05-25 21:44:10 +02:00 · 2026-05-25 21:42:46 +02:00 · 2026-05-25 14:15:04 -05:00
150 changed files with 2981 additions and 187 deletions
--- a/.gitignore
+++ b/.gitignore
@ -81,3 +81,6 @@ _bmad/custom/*.user.toml
 website/.astro/
 website/dist/
 build/
+
+# Web bundle release artifacts
+dist/web-bundles/
--- a/.husky/pre-commit
+++ b/.husky/pre-commit
@ -10,11 +10,13 @@ npm test
 if command -v rg >/dev/null 2>&1; then
  if git diff --cached --name-only | rg -q '^docs/'; then
    npm run docs:validate-links
+		npm run docs:validate-sidebar
 		npm run docs:build
  fi
 else
  if git diff --cached --name-only | grep -Eq '^docs/'; then
    npm run docs:validate-links
+		npm run docs:validate-sidebar
 		npm run docs:build
  fi
 fi
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@ -1,5 +1,46 @@
 # Changelog

+## v6.8.0 - 2026-05-25
+
+### ✨ Headline
+
+**New planning shapes lead this release.** **bmad-ux** replaces the old single-spine UX skill with a two-spine contract: **DESIGN.md** (visual identity, Google Labs spec) and **EXPERIENCE.md** (behavior, flow, IA). **bmad-spec** distills any messy intent (brain dump, PRD, transcript, brief) into a tight five-field SPEC.md kernel that any downstream skill can consume. Both extend the streamlined Create/Update/Validate + Fast/Coaching template that **bmad-prd** and **bmad-product-brief** set in v6.7.0. The handoff from design into engineering is now a sealed file contract, not a translation layer.
+
+**Also shipping:** **Web Bundles** for Gemini Gems and ChatGPT Custom GPTs ([bmadcode.com/web-bundles](https://bmadcode.com/web-bundles/)) bring six planning bundles to non-IDE users with full IDE schema parity. **bmad-automator** (story automation) lands on the `next` channel. **bmad-method-ui** ships a community-alpha VS Code dashboard + standalone Next.js web UI. 19 new elicitation techniques arrive. Plus a long tail of installer and activation fixes.
+
+### 💥 Breaking Changes
+
+* **`bmad-create-ux-design` replaced by `bmad-ux`.** Single `design.md` spine is gone. New skill emits **DESIGN.md** (visual tokens per the Google Labs spec) and **EXPERIENCE.md** (behavior, flow, IA, states, a11y), with EXPERIENCE.md referencing DESIGN.md tokens via `{path.to.token}` syntax. Adds named-protagonist journeys, surface-closure validation, opt-in reviewer gate, and an extensible producer-handoff registry (default: Stitch). Installer auto-removes the legacy skill. PRD and brief templates aligned (form-factor probe, named-protagonist UJs, no standalone Primary Persona) (#2413)
+* **`bmad-distillator` retired, superseded by `bmad-spec`.** Promoted to core because the kernel pattern is domain-agnostic. Installer cleans up automatically. No internal pipelines called it, but custom workflows must switch to `bmad-spec`.
+
+### 🎁 Features
+
+* **Web Bundles v6 shelf**: Six bundles purpose-built for Gemini Gems and ChatGPT Custom GPTs. Brainstorming (60 techniques, 10 categories), Product Brief (Create/Update/Validate, Fast/Coaching paths), PRFAQ (Working Backwards, 4 stages, weasel-word challenge), PRD (Vision- or Journey-led, 7-dimension validation), UX (two-spine, Don Norman framing, Stitch handoff), Market & Industry Research (Deep Research + Porter + Christensen). Full schema parity with IDE skills so Gem ↔ IDE handoffs do not break. [bmadcode.com/web-bundles](https://bmadcode.com/web-bundles/) is the single supported install path (#2421, #2423, #2425)
+* **Web Bundle release packager**: `tools/bundle-web-bundles.js` zips each bundle into `dist/web-bundles/{slug}.zip` for GitHub Release attachment. `web-bundles/bundles.json` carries persona, copy, accent color, knowledge files, and platform feature flags (web-browsing, deep-research, Stitch). Zero deps; `execFileSync` + strict slug regex (`^[a-z0-9][a-z0-9-]*$`) eliminates shell-injection surface (#2424)
+* **`bmad-spec`, new core skill**: Distills any intent (brain dump, PRD, transcript, brief) into `SPEC.md` with a five-field kernel (Problem, Capabilities, Constraints, Non-goals, Success signal). Catalogs, tables, diagrams, and editorial-voice content go to named companions; absorbed inputs land in a `sources:` list downstream skips. Eight-rule Spec Law with lean-prose discipline. Outputs to `{output_folder}/specs/spec-{slug}/`, works without bmm installed. Headless callers get JSON; interactive runs close conversationally (#2417)
+* **`bmad-ux`, spine-based UX skill**: Rewrite around DESIGN.md (visual identity, Google Labs spec) + EXPERIENCE.md (behavior, flow, IA). Six-step activation matches `bmad-prd` and `bmad-product-brief`. Fast/Coaching modes. Opt-in reviewer gate (no auto-spend on parallel reviewers for hobby work). Per-category verdicts, no misleading headline grade. Ships three DESIGN.md examples (editorial/Linen & Logic, native mobile/Quill, web SaaS/Drift), two paired EXPERIENCE.md examples, one unpaired DESIGN.md modeling the pure Stitch handoff (#2413)
+* **19 new advanced-elicitation techniques**: New `framing` category plus additions across 7 categories (all 50 existing methods preserved). Highlights: Chain-of-Thought Scaffolding, Six Thinking Hats, Delphi Method, Inversion Analysis, Steelmanning, Morphological Analysis, Abstraction Laddering, Cascading Failure Simulation, Boundary & Edge Case Sweep (#2062)
+* **Docs sidebar-order validator**: `tools/validate-sidebar-order.js` flags duplicates, gaps, missing fields, and translation drift across English and translated docs. Wired into `docs:validate-sidebar`. Locale-pattern detection prevents nested English subfolders from being silently excluded (#2409)
+
+### 🐛 Fixes
+
+* **Skill activation guardrails strengthened across 23+ skills**: LLM agents were short-circuiting activation sequences (INCLUDE → READ → RUN → CHECK → FILTER → CD) by guessing variables instead of executing in order, silently skipping append steps and `on_complete` hooks. New guardrail names prepend/append steps explicitly and requires confirmation. Applied to all BMM planning + execution skills, all persona agents (analyst, tech-writer, pm, ux-designer, architect, dev), and new skills (bmad-spec, bmad-ux) (#2398)
+* **Installer reads `config.toml` on re-run**: `loadExistingConfig` only read legacy `_bmad/<module>/config.yaml`, so user-scoped answers (`user_name`, `communication_language`) written to `_bmad/config.user.toml` were ignored and users got re-prompted. Adds `parseCentralToml`; central toml read first, legacy yaml as fallback (#2411)
+* **Stale custom-source caches refreshed on quick-update**: Quick-update now calls `cloneRepo` for every cached custom module, persists the real `next` ref, and atomically dedupes the refresh. When `git fetch` fails (network, deleted repo, revoked auth), the previous clone is preserved with a warning instead of being wiped (#2399)
+* **Shallow-clone default branch resolution**: `--depth 1` clones leave `origin/HEAD` stale, so `git reset --hard origin/HEAD` never pulled new commits. Now resolves the default branch via `git symbolic-ref` and resets against `origin/<branch>` explicitly, falling back to `main` (#2332)
+* **SSH Git URLs with nested group paths**: Custom module installer parses GitLab subgroup and Gitea nested-team SSH URLs correctly (#2379)
+* **`project_context` defined in dev-story, sprint-planning, sprint-status**: Skills referenced the variable without resolving it, producing unresolved expansions at activation in some configurations (#2422)
+* **Dev story baseline commits captured**: Baselining records the commit set the story was scoped against, so reviews compare against a stable reference (#2403)
+* **Customization JSON written as UTF-8**: Non-ASCII team names, product names, and editorial overrides survive a round trip through `_bmad/custom/` (#2414)
+* **Brainstorming idea-flow stays collaborative**: Agent was prematurely converging on its own preferred ideas instead of mirroring and expanding the user's. Collaborative posture restored (#2402)
+
+### 📚 Docs
+
+* **bmad-investigate added to agent trigger tables**: `agents.md` and `named-agents.md` now show the `IN` trigger and forensic-investigation capability on Amelia's row, closing a v6.7.0 gap (#2410)
+* **Web Bundles install framing and update/customize guidance**: Drops misleading "one-click install" and "two files" claims; adds explicit Gem/GPT setup pattern and an "Updating and customizing" section: custom changes belong in the pasted instructions block, not the knowledge files, so updates do not clobber team customizations (#2423)
+* **Web-bundles install traffic centralized at bmadcode.com/web-bundles**: README, web-bundles README, explanation, and how-to pages all point at the site as the single supported install path (#2425)
+* **Reference docs for bmad-spec**: Full entry in `docs/reference/core-tools.md` (en); table-row stubs in cs/fr/vi-vn/zh-cn pending full translation
+
 ## v6.7.1 - 2026-05-18

 ### 🐛 Fixes
--- a/README.md
+++ b/README.md
@ -77,6 +77,16 @@ BMad Method extends with official modules for specialized domains. Available dur
 | **[Game Dev Studio (BMGD)](https://github.com/bmad-code-org/bmad-module-game-dev-studio)**                        | Game development workflows (Unity, Unreal, Godot) |
 | **[Creative Intelligence Suite (CIS)](https://github.com/bmad-code-org/bmad-module-creative-intelligence-suite)** | Innovation, brainstorming, design thinking        |

+## Web Bundles
+
+V4 shipped web bundles. V6 brings them back, new and improved.
+
+Web bundles package selected BMad skills for installation as **Google Gemini Gems** and **ChatGPT Custom GPTs**. Use them to do the upfront planning work (brainstorming, product briefs, PRDs, PRFAQs, UX specs, market and industry research) in your web LLM subscription, then bring the polished artifacts into your IDE for implementation. Planning runs on a flat-rate subscription instead of metered IDE tokens, which is a meaningful cost saver on longer engagements. Choose the best model available to you in Gemini or ChatGPT.
+
+Current shelf: brainstorming, product brief, PRFAQ, PRD, UX, market & industry research.
+
+**Browse and install at [bmadcode.com/web-bundles](https://bmadcode.com/web-bundles/)**. One card per bundle, inline install steps for Gemini and ChatGPT, one-click ZIP download. See [the web bundles guide](https://docs.bmad-method.org/explanation/web-bundles/) for the concept.
+
 ## Documentation

 [BMad Method Docs Site](https://docs.bmad-method.org) — Tutorials, guides, concepts, and reference
--- a/docs/cs/explanation/advanced-elicitation.md
+++ b/docs/cs/explanation/advanced-elicitation.md
@ -2,7 +2,7 @@
 title: "Pokročilá elicitace"
 description: Přimějte LLM přehodnotit svou práci pomocí strukturovaných metod uvažování
 sidebar:
-  order: 6
+  order: 3
 ---

 Přimějte LLM přehodnotit, co právě vygeneroval. Vyberete metodu uvažování, LLM ji aplikuje na svůj vlastní výstup, a vy rozhodnete, zda si vylepšení ponecháte.
--- a/docs/cs/explanation/adversarial-review.md
+++ b/docs/cs/explanation/adversarial-review.md
@ -2,7 +2,7 @@
 title: "Adversariální revize"
 description: Technika vynuceného uvažování, která zabraňuje líným „vypadá dobře“ revizím
 sidebar:
-  order: 5
+  order: 7
 ---

 Vynuťte hlubší analýzu tím, že budete vyžadovat nalezení problémů.
--- a/docs/cs/explanation/established-projects-faq.md
+++ b/docs/cs/explanation/established-projects-faq.md
@ -2,7 +2,7 @@
 title: "FAQ pro existující projekty"
 description: Časté otázky o používání BMad Method na existujících projektech
 sidebar:
-  order: 8
+  order: 10
 ---
 Rychlé odpovědi na časté otázky o práci na existujících projektech s BMad Method (BMM).

--- a/docs/cs/explanation/party-mode.md
+++ b/docs/cs/explanation/party-mode.md
@ -2,7 +2,7 @@
 title: "Party Mode"
 description: Spolupráce více agentů — všichni vaši AI agenti v jedné konverzaci
 sidebar:
-  order: 7
+  order: 8
 ---

 Všichni vaši AI agenti v jedné konverzaci.
--- a/docs/cs/explanation/preventing-agent-conflicts.md
+++ b/docs/cs/explanation/preventing-agent-conflicts.md
@ -2,7 +2,7 @@
 title: "Předcházení konfliktům agentů"
 description: Jak architektura zabraňuje konfliktům, když více agentů implementuje systém
 sidebar:
-  order: 4
+  order: 5
 ---

 Když více AI agentů implementuje různé části systému, mohou dělat protichůdná technická rozhodnutí. Dokumentace architektury tomu zabraňuje stanovením sdílených standardů.
--- a/docs/cs/explanation/project-context.md
+++ b/docs/cs/explanation/project-context.md
@ -2,7 +2,7 @@
 title: "Kontext projektu"
 description: Jak project-context.md vede AI agenty s pravidly a preferencemi vašeho projektu
 sidebar:
-  order: 7
+  order: 9
 ---

 Soubor `project-context.md` je implementační průvodce vašeho projektu pro AI agenty. Podobně jako „ústava“ v jiných vývojových systémech zachycuje pravidla, vzory a preference, které zajišťují konzistentní generování kódu napříč všemi workflow.
--- a/docs/cs/explanation/quick-dev.md
+++ b/docs/cs/explanation/quick-dev.md
@ -2,7 +2,7 @@
 title: "Quick Dev"
 description: Snižte tření human-in-the-loop bez ztráty kontrolních bodů chránících kvalitu výstupu
 sidebar:
-  order: 2
+  order: 6
 ---

 Záměr na vstupu, změny kódu na výstupu, s co nejmenším počtem human-in-the-loop kroků — bez obětování kvality.
--- a/docs/cs/explanation/why-solutioning-matters.md
+++ b/docs/cs/explanation/why-solutioning-matters.md
@ -2,7 +2,7 @@
 title: "Proč je solutioning důležitý"
 description: Pochopení toho, proč je fáze solutioningu klíčová pro projekty s více epicy
 sidebar:
-  order: 3
+  order: 4
 ---

 Fáze 3 (Solutioning) překládá **co** budovat (z plánování) na **jak** to budovat (technický návrh). Tato fáze zabraňuje konfliktům agentů v projektech s více epicy tím, že dokumentuje architektonická rozhodnutí před zahájením implementace.
--- a/docs/cs/reference/commands.md
+++ b/docs/cs/reference/commands.md
@ -2,7 +2,7 @@
 title: Skills
 description: Reference BMad skills — co to je, jak fungují a kde je najít.
 sidebar:
-  order: 3
+  order: 4
 ---

 Skills jsou předpřipravené prompty, které načítají agenty, spouštějí workflow nebo provádějí úkoly ve vašem IDE. Instalátor BMad je generuje z vašich nainstalovaných modulů při instalaci. Pokud později přidáte, odeberete nebo změníte moduly, přeinstalujte pro synchronizaci skills (viz [Řešení problémů](#řešení-problémů)).
--- a/docs/cs/reference/core-tools.md
+++ b/docs/cs/reference/core-tools.md
@ -2,7 +2,7 @@
 title: Základní nástroje
 description: Reference všech vestavěných úkolů a workflow dostupných v každé instalaci BMad bez dalších modulů.
 sidebar:
-  order: 2
+  order: 3
 ---

 Každá instalace BMad zahrnuje sadu základních skills, které lze použít v kombinaci s čímkoli — samostatné úkoly a workflow, které fungují napříč všemi projekty, všemi moduly a všemi fázemi. Ty jsou vždy dostupné bez ohledu na to, které volitelné moduly nainstalujete.
--- a/docs/cs/reference/modules.md
+++ b/docs/cs/reference/modules.md
@ -2,7 +2,7 @@
 title: Oficiální moduly
 description: Doplňkové moduly pro tvorbu vlastních agentů, kreativní inteligenci, vývoj her a testování
 sidebar:
-  order: 4
+  order: 5
 ---

 BMad se rozšiřuje prostřednictvím oficiálních modulů, které vyberete během instalace. Tyto doplňkové moduly poskytují specializované agenty, workflow a úkoly pro specifické domény nad rámec vestavěného jádra a BMM (Agile suite).
--- a/docs/cs/reference/testing.md
+++ b/docs/cs/reference/testing.md
@ -2,7 +2,7 @@
 title: Možnosti testování
 description: Srovnání vestavěného QA agenta (Quinn) s modulem Test Architect (TEA) pro automatizaci testů.
 sidebar:
-  order: 5
+  order: 6
 ---

 BMad poskytuje dvě testovací cesty: vestavěného QA agenta pro rychlé generování testů a instalovatelný modul Test Architect pro podnikovou testovací strategii.
--- a/docs/explanation/advanced-elicitation.md
+++ b/docs/explanation/advanced-elicitation.md
@ -2,7 +2,7 @@
 title: "Advanced Elicitation"
 description: Push the LLM to rethink its work using structured reasoning methods
 sidebar:
-  order: 6
+  order: 4
 ---

 Make the LLM reconsider what it just generated. You pick a reasoning method, it applies that method to its own output, you decide whether to keep the improvements.
--- a/docs/explanation/adversarial-review.md
+++ b/docs/explanation/adversarial-review.md
@ -2,7 +2,7 @@
 title: "Adversarial Review"
 description: Forced reasoning technique that prevents lazy "looks good" reviews
 sidebar:
-  order: 5
+  order: 9
 ---

 Force deeper analysis by requiring problems to be found.
--- a/docs/explanation/analysis-phase.md
+++ b/docs/explanation/analysis-phase.md
@ -2,7 +2,7 @@
 title: "Analysis Phase: From Idea to Foundation"
 description: What brainstorming, research, product briefs, and PRFAQs are — and when to use each
 sidebar:
-  order: 1
+  order: 2
 ---

 The Analysis phase (Phase 1) helps you think clearly about your product before committing to building it. Every tool in this phase is optional, but skipping analysis entirely means your PRD is built on assumptions instead of insight.
--- a/docs/explanation/brainstorming.md
+++ b/docs/explanation/brainstorming.md
@ -2,7 +2,7 @@
 title: "Brainstorming"
 description: Interactive creative sessions using 60+ proven ideation techniques
 sidebar:
-  order: 2
+  order: 3
 ---

 Unlock your creativity through guided exploration.
--- a/docs/explanation/checkpoint-preview.md
+++ b/docs/explanation/checkpoint-preview.md
@ -2,7 +2,7 @@
 title: "Checkpoint Preview"
 description: LLM-assisted human-in-the-loop review that guides you through a change from purpose to details
 sidebar:
-  order: 3
+  order: 8
 ---

 `bmad-checkpoint-preview` is an interactive, LLM-assisted human-in-the-loop review workflow. It walks you through a code change — from purpose and context into details — so you can make an informed decision about whether to ship, rework, or dig deeper.
--- a/docs/explanation/established-projects-faq.md
+++ b/docs/explanation/established-projects-faq.md
@ -2,7 +2,7 @@
 title: "Established Projects FAQ"
 description: Common questions about using BMad Method on established projects
 sidebar:
-  order: 8
+  order: 13
 ---
 Quick answers to common questions about working on established projects with the BMad Method (BMM).

--- a/docs/explanation/forensic-investigation.md
+++ b/docs/explanation/forensic-investigation.md
@ -2,7 +2,7 @@
 title: "Forensic Investigation"
 description: How bmad-investigate treats every issue like a crime scene, grades evidence, and produces a structured case file engineers can act on
 sidebar:
-  order: 6
+  order: 10
 ---

 You hand `bmad-investigate` a crash log, a stack trace, or just a "this used to work, now it doesn't". The skill takes
--- a/docs/explanation/party-mode.md
+++ b/docs/explanation/party-mode.md
@ -2,7 +2,7 @@
 title: "Party Mode"
 description: Multi-agent collaboration - get all your AI agents in one conversation
 sidebar:
-  order: 7
+  order: 11
 ---

 Get all your AI agents in one conversation.
--- a/docs/explanation/preventing-agent-conflicts.md
+++ b/docs/explanation/preventing-agent-conflicts.md
@ -2,7 +2,7 @@
 title: "Preventing Agent Conflicts"
 description: How architecture prevents conflicts when multiple agents implement a system
 sidebar:
-  order: 4
+  order: 6
 ---

 When multiple AI agents implement different parts of a system, they can make conflicting technical decisions. Architecture documentation prevents this by establishing shared standards.
--- a/docs/explanation/project-context.md
+++ b/docs/explanation/project-context.md
@ -2,7 +2,7 @@
 title: "Project Context"
 description: How project-context.md guides AI agents with your project's rules and preferences
 sidebar:
-  order: 7
+  order: 12
 ---

 The `project-context.md` file is your project's implementation guide for AI agents. Similar to a "constitution" in other development systems, it captures the rules, patterns, and preferences that ensure consistent code generation across all workflows.
--- a/docs/explanation/quick-dev.md
+++ b/docs/explanation/quick-dev.md
@ -2,7 +2,7 @@
 title: "Quick Dev"
 description: Reduce human-in-the-loop friction without giving up the checkpoints that protect output quality
 sidebar:
-  order: 2
+  order: 7
 ---

 Intent in, code changes out, with as few human-in-the-loop turns as possible — without sacrificing quality.
--- a/docs/explanation/web-bundles.md
+++ b/docs/explanation/web-bundles.md
@ -0,0 +1,82 @@
+---
+title: 'Web Bundles'
+description: BMad skills packaged for Google Gemini Gems and ChatGPT Custom GPTs
+---
+
+Run the planning side of BMad in your web LLM subscription, then bring the artifacts into your IDE.
+
+## What is a Web Bundle?
+
+A web bundle is a BMad skill repackaged for installation as a **Google Gemini Gem** or **ChatGPT Custom GPT**. Each bundle includes a `SKILL.md` protocol you upload as a knowledge file, an `INSTRUCTIONS.md` block you paste into the Gem or GPT instructions, and any data files the skill needs (CSVs, templates, validation checklists, additionally progressively disclosed content). The persona lives in the pasted instructions; the protocol lives in the knowledge file. Swap personas without touching the protocol.
+
+Setup is not one-click, but the steps are guided. **Install from [bmadcode.com/web-bundles](https://bmadcode.com/web-bundles/)**. The site lists every bundle in a card grid, shows you the Gemini and ChatGPT install steps inline, and hands you the ZIP download. That is the supported install path; the pattern is the same across the shelf, so once you've installed one the next one is mechanical.
+
+V4 of BMad shipped web bundles. V6 brings them back, rewritten for the current Gem and Custom GPT platforms with Canvas, Deep Research, and image generation in mind.
+
+## Why use them
+
+Planning work and implementation work want different tools. Web bundles let each use the right one.
+
+| Concern | Web LLM (Gem or GPT) | IDE (Claude Code, Cursor) |
+| --- | --- | --- |
+| Cost model | Flat-rate subscription | Metered tokens |
+| Strongest at | Conversation, Canvas, Deep Research, images | Files, terminal, codebase context |
+| Best for | Brainstorming, briefs, PRDs, research | Implementation, refactoring, code review |
+
+Running a full PRD or market research conversation in an IDE burns tokens that a Gem or Custom GPT handles for the price of your existing subscription. The polished artifact then drops into your repo and Claude Code or Cursor takes it from there.
+
+:::tip[Plan in the web, build in the IDE]
+The cost saving compounds on longer engagements. A PRFAQ pass and three rounds of research in a Gem cost zero marginal dollars; the same work in an IDE is real spend.
+:::
+
+## What's in the shelf
+
+The current set of bundles covers the analysis and planning phases:
+
+| Bundle | Phase | Persona lineage |
+| --- | --- | --- |
+| Brainstorming Coach | Analysis | Osborn (default), Minto (swap) |
+| Product Brief Coach | Analysis | Mary (BMad analyst) |
+| PRFAQ Coach | Analysis | Working Backwards (Bezos) |
+| PRD Coach | Planning | Cagan |
+| UX Coach | Planning | Norman |
+| Market & Industry Research | Analysis | Porter and Christensen |
+
+Each bundle carries a default persona inherited from its owning BMad agent (where one exists) and a contrasting swap example to demonstrate the voice change pattern.
+
+## How a session works
+
+1. **Open the Gem or Custom GPT.** Persona greets in character and opens conversational discovery.
+2. **Discover scope.** The persona asks what you're trying to do, what you have on hand, what constraints apply. No form fill.
+3. **Do the work in Canvas.** The protocol opens Canvas at session start and updates it continuously. Mermaid diagrams and HTML tables go in alongside the prose.
+4. **Hand off.** When you're done, you have a Canvas document you can export, paste into your repo, or feed to a BMad skill in your IDE for the next phase.
+
+For bundles that integrate Deep Research (currently Market & Industry Research), the persona drafts a Deep Research brief mid-session for you to paste into Gemini's or ChatGPT's Deep Research mode, then ingests the returned report.
+
+## When to use a web bundle
+
+- You're doing the upfront thinking for a project and you want a focused tool with persona, Canvas, and Deep Research.
+- You want to keep IDE token spend for actual coding.
+- You're sharing the planning artifact with collaborators who don't have your IDE setup.
+
+## When to stay in the IDE
+
+- The work needs to read or modify code in your repo.
+- You're already mid-implementation and want to keep context.
+- You don't have a Gemini Advanced or ChatGPT Plus subscription.
+
+## Updating and customizing
+
+Bundles evolve. When you pull a newer version of a bundle, the typical update is to its knowledge files (the `SKILL.md` protocol and any attached templates, CSVs, or validation checklists). Re-upload those into your Gem or Custom GPT to take the update. The instructions block usually does not change.
+
+If you want to customize a bundle for your team or your voice, do it in the **instructions block** you pasted into the Gem or GPT, not in the knowledge files. The instructions block is where the persona, preferences, and any local overrides live; the knowledge files are the protocol the bundle ships with. Keeping customization in the instructions block means future updates are a swap-the-attachments operation, not a merge-your-edits-back-in operation.
+
+:::tip[Customize the instructions, attach the knowledge]
+Persona swaps, default user name, team-specific guardrails, preferred phrasing: all of that belongs in the pasted instructions block. The knowledge files stay stock so you can refresh them without losing your changes.
+:::
+
+## Building your own
+
+Web bundles are generated from BMad skills using the `bmad-os-skill-to-bundle` utility skill. Point it at any BMad skill folder and it produces the bundle files with persona inheritance from the owning agent.
+
+Install any bundle from [bmadcode.com/web-bundles](https://bmadcode.com/web-bundles/).
--- a/docs/explanation/why-solutioning-matters.md
+++ b/docs/explanation/why-solutioning-matters.md
@ -2,7 +2,7 @@
 title: "Why Solutioning Matters"
 description: Understanding why the solutioning phase is critical for multi-epic projects
 sidebar:
-  order: 3
+  order: 5
 ---


--- a/docs/fr/explanation/advanced-elicitation.md
+++ b/docs/fr/explanation/advanced-elicitation.md
@ -2,7 +2,7 @@
 title: "Élicitation Avancée"
 description: Pousser le LLM à repenser son travail en utilisant des méthodes de raisonnement structurées
 sidebar:
-  order: 9
+  order: 4
 ---

 Faites repenser au LLM ce qu’il vient de générer. Vous choisissez une méthode de raisonnement, il l’applique à sa propre sortie, et vous décidez de conserver ou non les améliorations.
--- a/docs/fr/explanation/adversarial-review.md
+++ b/docs/fr/explanation/adversarial-review.md
@ -2,7 +2,7 @@
 title: "Revue Contradictoire"
 description: Technique de raisonnement forcée qui empêche les revues paresseuses du style « ça à l’air bon »
 sidebar:
-  order: 8
+  order: 9
 ---

 Forcez une analyse plus approfondie en exigeant que des problèmes soient trouvés.
--- a/docs/fr/explanation/analysis-phase.md
+++ b/docs/fr/explanation/analysis-phase.md
@ -2,7 +2,7 @@
 title: "Phase d’analyse : de l’Idée aux Fondations"
 description: Ce que sont le brainstorming, la recherche, les product briefs et les PRFAQs — et quand les utiliser
 sidebar:
-  order: 1
+  order: 2
 ---

 La phase d’Analyse (Phase 1) vous aide à penser clairement à votre produit avant de vous engager à le construire. Chaque outil de cette phase est optionnel, mais sauter l’analyse entièrement signifie que votre PRD sera construit sur des suppositions plutôt que sur des connaissances approfondies.
--- a/docs/fr/explanation/checkpoint-preview.md
+++ b/docs/fr/explanation/checkpoint-preview.md
@ -2,7 +2,7 @@
 title: "Checkpoint Preview"
 description: Revue assistée par LLM, avec intervention humaine, qui vous guide à travers une modification, de son objectif jusqu’aux détails
 sidebar:
-  order: 5
+  order: 8
 ---

 `bmad-checkpoint-preview` est un workflow de revue interactif, assisté par LLM, avec intervention humaine. Il vous guide à travers une modification de code — de l’intention et du contexte jusqu’aux détails — afin que vous puissiez prendre une décision éclairée sur la mise en production, la refonte ou l’approfondissement.
--- a/docs/fr/explanation/named-agents.md
+++ b/docs/fr/explanation/named-agents.md
@ -2,7 +2,7 @@
 title: "Agents nommés"
 description: Pourquoi les agents BMad ont des noms, des personas et des options de personnalisation — et ce que cela permet par rapport aux alternatives basées sur des menus ou des prompts
 sidebar:
-  order: 2
+  order: 1
 ---

 Vous dites « Hey Mary, brainstormons » et Mary s’active. Elle vous salue par votre nom, dans la langue que vous avez configurée, avec son persona distinctif. Elle vous rappelle que `bmad-help` est toujours disponible. Puis elle saute le menu et se lance directement dans le brainstorming — parce que votre intention était claire.
--- a/docs/fr/explanation/preventing-agent-conflicts.md
+++ b/docs/fr/explanation/preventing-agent-conflicts.md
@ -2,7 +2,7 @@
 title: "Prévention des conflits entre agents"
 description: Comment l’architecture empêche les conflits lorsque plusieurs agents implémentent un système
 sidebar:
-  order: 7
+  order: 6
 ---

 Lorsque plusieurs agents IA implémentent différentes parties d’un système, ils peuvent prendre des décisions techniques contradictoires. La documentation d’architecture prévient cela en établissant des standards partagés.
--- a/docs/fr/explanation/quick-dev.md
+++ b/docs/fr/explanation/quick-dev.md
@ -2,7 +2,7 @@
 title: "Quick Dev"
 description: Réduire la friction de l’interaction humaine sans renoncer aux points de contrôle qui protègent la qualité des résultats
 sidebar:
-  order: 4
+  order: 7
 ---

 Intention en entrée, modifications de code en sortie, avec aussi peu d’interactions humaines dans la boucle que possible — sans sacrifier la qualité.
--- a/docs/fr/explanation/why-solutioning-matters.md
+++ b/docs/fr/explanation/why-solutioning-matters.md
@ -2,7 +2,7 @@
 title: "Pourquoi le Solutioning est Important"
 description: Comprendre pourquoi la phase de solutioning est critique pour les projets multi-epics
 sidebar:
-  order: 6
+  order: 5
 ---

 La Phase 3 (Solutioning) traduit le **quoi** construire (issu de la Planification) en **comment** le construire (conception technique). Cette phase évite les conflits entre agents dans les projets multi-epics en documentant les décisions architecturales avant le début de l’implémentation.
--- a/docs/fr/how-to/expand-bmad-for-your-org.md
+++ b/docs/fr/how-to/expand-bmad-for-your-org.md
@ -2,7 +2,7 @@
 title: 'Comment étendre BMad pour votre organisation'
 description: Six patterns de personnalisation qui remodèlent BMad sans créer de fork — règles applicables aux agents, conventions de workflow, publication externe, remplacements de templates, modifications du registre des agents et patterns d’intégration avancés
 sidebar:
-  order: 9
+  order: 11
 ---

 Le système de personnalisation de BMad permet à une organisation d’adapter les comportements sans modifier les fichiers installés ni forker les skills. Ce guide présente six recettes qui couvrent la plupart des besoins en entreprise.
--- a/docs/fr/how-to/project-context.md
+++ b/docs/fr/how-to/project-context.md
@ -2,7 +2,7 @@
 title: "Gérer le contexte du projet"
 description: Créer et maintenir project-context.md pour guider les agents IA
 sidebar:
-  order: 10
+  order: 9
 ---

 Utilisez le fichier `project-context.md` pour garantir que les agents IA respectent les préférences techniques et les règles d’implémentation de votre projet tout au long des workflows. Pour vous assurer qu’il est toujours disponible, vous pouvez également ajouter la ligne `Le contexte et les conventions importantes du projet se trouvent dans [chemin vers le contexte du projet]/project-context.md` à votre fichier de contexte ou de règles permanentes (comme `AGENTS.md`).
--- a/docs/fr/how-to/shard-large-documents.md
+++ b/docs/fr/how-to/shard-large-documents.md
@ -2,7 +2,7 @@
 title: "Guide de Division de Documents"
 description: Diviser les fichiers markdown volumineux en fichiers plus petits et organisés pour une meilleure gestion du contexte
 sidebar:
-  order: 11
+  order: 10
 ---

 Utilisez l’outil `bmad-shard-doc` si vous avez besoin de diviser des fichiers markdown volumineux en fichiers plus petits et organisés pour une meilleure gestion du contexte.
--- a/docs/fr/roadmap.mdx
+++ b/docs/fr/roadmap.mdx
@ -3,7 +3,7 @@ title: Feuille de route
 description: La suite pour BMad - Fonctionnalités, améliorations et contributions de la communauté
 ---

-# La Méthode BMad : Feuille de route publique
+# La Méthode BMad : Feuille de route publique

 La Méthode BMad, BMad Method Module (BMM) et BMad Builder (BMB) évoluent. Voici ce sur quoi nous travaillons et ce qui arrive prochainement.

@ -105,7 +105,7 @@ La Méthode BMad, BMad Method Module (BMM) et BMad Builder (BMB) évoluent. Voic
    <div class="roadmap-future-card">
      <span class="roadmap-emoji">🌴</span>
      <h4>BMad BALM !</h4>
-      <p>Gestion de vie native IA. Tâches, habitudes, objectifs : votre copilote IA pour tout.</p>
+      <p>Gestion de vie native IA. Tâches, habitudes, objectifs : votre copilote IA pour tout.</p>
    </div>
    <div class="roadmap-future-card">
      <span class="roadmap-emoji">🖥️</span>
@ -120,16 +120,16 @@ La Méthode BMad, BMad Method Module (BMM) et BMad Builder (BMB) évoluent. Voic
  </div>

  <div style="text-align: center; margin-top: 3rem; padding: 2rem; background: var(--color-bg-card); border-radius: 12px; border: 1px solid var(--color-border);">
-    <h3 style="margin: 0 0 1rem;">Envie de contribuer ?</h3>
+    <h3 style="margin: 0 0 1rem;">Envie de contribuer ?</h3>
    <p style="color: var(--slate-color-400); margin: 0;">
-      Ce n'est qu'une liste partielle de ce qui est prévu. L’équipe Open Source BMad accueille les contributeurs !{" "}<br />
+      Ce n’est qu’une liste partielle de ce qui est prévu. L’équipe Open Source BMad accueille les contributeurs !{" "}<br />
      <a href="https://github.com/bmad-code-org/BMAD-METHOD" style="color: var(--color-in-progress);">Rejoignez-nous sur GitHub</a> pour aider à façonner l’avenir du développement propulsé par l’IA.
    </p>
    <p style="color: var(--slate-color-400); margin: 1.5rem 0 0;">
-      Vous aimez ce que nous construisons ? Nous apprécions le soutien ponctuel et mensuel sur{" "}<a href="https://buymeacoffee.com/bmad" style="color: var(--color-in-progress);">Buy Me a Coffee</a>.
+      Vous aimez ce que nous construisons ? Nous apprécions le soutien ponctuel et mensuel sur{" "}<a href="https://buymeacoffee.com/bmad" style="color: var(--color-in-progress);">Buy Me a Coffee</a>.
    </p>
    <p style="color: var(--slate-color-400); margin: 1rem 0 0;">
-      Pour les parrainages d'entreprise, les demandes de partenariat, les interventions, les formations ou les demandes médias :{" "}
+      Pour les parrainages d’entreprise, les demandes de partenariat, les interventions, les formations ou les demandes médias :{" "}
      <a href="mailto:contact@bmadcode.com" style="color: var(--color-in-progress);">contact@bmadcode.com</a>
    </p>
  </div>
--- a/docs/how-to/expand-bmad-for-your-org.md
+++ b/docs/how-to/expand-bmad-for-your-org.md
@ -2,7 +2,7 @@
 title: 'How to Expand BMad for Your Organization'
 description: Six customization patterns that reshape BMad without forking — agent-wide rules, workflow conventions, external publishing, template swaps, agent roster changes, and advanced integration patterns
 sidebar:
-  order: 9
+  order: 11
 ---

 BMad's customization surface lets an organization reshape behavior without editing installed files or forking skills. This guide walks through six recipes that cover most enterprise needs.
--- a/docs/how-to/use-web-bundles.md
+++ b/docs/how-to/use-web-bundles.md
@ -0,0 +1,41 @@
+---
+title: 'Use Web Bundles'
+description: Install a BMad web bundle as a Google Gemini Gem or ChatGPT Custom GPT
+---
+
+Web bundles install from **[bmadcode.com/web-bundles](https://bmadcode.com/web-bundles/)**.
+
+## Why a single front door
+
+The site is the only supported install path for the shelf. It keeps the steps current as Gemini and ChatGPT evolve, always points at the newest tagged release, and lets one signup put you on the list for new bundles as they ship.
+
+## What you'll do on the site
+
+1. Pick a bundle from the card grid.
+2. Open the install modal. Switch between the **Gemini Gem** and **ChatGPT GPT** tabs for the platform-specific steps.
+3. Download the bundle ZIP (one click; one-time free signup for email-only members).
+4. Follow the inline steps: create the Gem or Custom GPT, upload the knowledge files, paste the instructions block, save.
+
+## Prerequisites
+
+- **For Gemini Gems**: Gemini Advanced subscription.
+- **For ChatGPT Custom GPTs**: Plus, Pro, Business, or Enterprise plan.
+- For bundles that use **Deep Research** (currently Market & Industry Research), enable it from the prompt bar (Tools → Deep Research). Deep Research has its own plan limits.
+
+## Customize the persona
+
+Each bundle's `INSTRUCTIONS.md` (inside the ZIP) includes a **Persona Swap Example** above the paste boundary. Replace the `[persona]` block in your installed instructions with the swap example to change voice without changing the protocol. You can also write your own persona from scratch; the protocol stays the same.
+
+## What you get
+
+- A reusable Gem or Custom GPT scoped to one BMad planning capability.
+- Polished artifacts (briefs, PRDs, research reports, UX specs) ready to drop into your IDE for implementation.
+- Planning conversation runs on your existing web LLM subscription instead of metered IDE tokens.
+
+:::caution[Persona drift]
+Web LLMs occasionally drop persona partway through long sessions. If the model starts speaking out of character, remind it of its persona or start a fresh session.
+:::
+
+## Building your own
+
+To turn an existing BMad skill into a web bundle, use the `bmad-os-skill-to-bundle` utility skill from [bmad-utility-skills](https://github.com/bmad-code-org/bmad-utility-skills). It produces the bundle files with persona inheritance from the owning agent and a swap-example contrast voice. Submit your bundle to the shelf by opening a PR on [BMAD-METHOD](https://github.com/bmad-code-org/BMAD-METHOD) that adds the bundle directory and an entry in `web-bundles/bundles.json`.
--- a/docs/reference/commands.md
+++ b/docs/reference/commands.md
@ -2,7 +2,7 @@
 title: Skills
 description: Reference for BMad skills — what they are, how they work, and where to find them.
 sidebar:
-  order: 3
+  order: 4
 ---

 Skills are pre-built prompts that load agents, run workflows, or execute tasks inside your IDE. The BMad installer generates them from your installed modules at install time. If you later add, remove, or change modules, re-run the installer to keep skills in sync (see [Troubleshooting](#troubleshooting)).
--- a/docs/reference/core-tools.md
+++ b/docs/reference/core-tools.md
@ -2,7 +2,7 @@
 title: Core Tools
 description: Reference for all built-in tasks and workflows available in every BMad installation without additional modules.
 sidebar:
-  order: 2
+  order: 3
 ---

 Every BMad installation includes a set of core skills that can be used in conjunction with any anything you are doing — standalone tasks and workflows that work across all projects, all modules, and all phases. These are always available regardless of which optional modules you install.
--- a/docs/reference/modules.md
+++ b/docs/reference/modules.md
@ -2,7 +2,7 @@
 title: Official Modules
 description: Add-on modules for building custom agents, creative intelligence, game development, and testing
 sidebar:
-  order: 4
+  order: 5
 ---

 BMad extends through official modules that you select during installation. These add-on modules provide specialized agents, workflows, and tasks for specific domains beyond the built-in core and BMM (Agile suite).
--- a/docs/reference/testing.md
+++ b/docs/reference/testing.md
@ -2,7 +2,7 @@
 title: Testing Options
 description: Comparing the built-in QA workflow with the Test Architect (TEA) module for test automation.
 sidebar:
-  order: 5
+  order: 6
 ---

 BMad provides two testing paths: a built-in QA workflow for fast test generation and an installable Test Architect module for enterprise-grade test strategy.
--- a/docs/vi-vn/explanation/advanced-elicitation.md
+++ b/docs/vi-vn/explanation/advanced-elicitation.md
@ -2,7 +2,7 @@
 title: "Khai thác nâng cao"
 description: Buộc LLM xem xét lại kết quả của nó bằng các phương pháp lập luận có cấu trúc
 sidebar:
-  order: 6
+  order: 4
 ---

 Buộc LLM xem xét lại những gì nó vừa tạo ra. Bạn chọn một phương pháp lập luận, nó áp dụng phương pháp đó lên chính output của mình, rồi bạn quyết định có giữ các cải tiến hay không.
--- a/docs/vi-vn/explanation/adversarial-review.md
+++ b/docs/vi-vn/explanation/adversarial-review.md
@ -2,7 +2,7 @@
 title: "Đánh giá đối kháng"
 description: Kỹ thuật lập luận ép buộc giúp tránh các bản review lười kiểu "nhìn ổn"
 sidebar:
-  order: 5
+  order: 9
 ---

 Buộc quá trình phân tích đi sâu hơn bằng cách ép phải tìm ra vấn đề.
--- a/docs/vi-vn/explanation/analysis-phase.md
+++ b/docs/vi-vn/explanation/analysis-phase.md
@ -2,7 +2,7 @@
 title: "Giai đoạn phân tích: từ ý tưởng đến nền tảng"
 description: Động não, nghiên cứu, product brief và PRFAQ là gì, và nên dùng từng công cụ khi nào
 sidebar:
-  order: 1
+  order: 2
 ---

 Giai đoạn phân tích (giai đoạn 1) giúp bạn suy nghĩ rõ ràng về sản phẩm trước khi cam kết bắt tay vào xây dựng. Mọi công cụ trong giai đoạn này đều là tùy chọn, nhưng nếu bỏ qua toàn bộ phần phân tích thì PRD của bạn sẽ được dựng trên giả định thay vì hiểu biết thực chất.
--- a/docs/vi-vn/explanation/brainstorming.md
+++ b/docs/vi-vn/explanation/brainstorming.md
@ -2,7 +2,7 @@
 title: "Động não ý tưởng"
 description: Các phiên sáng tạo tương tác sử dụng hơn 60 kỹ thuật khơi ý đã được kiểm chứng
 sidebar:
-  order: 2
+  order: 3
 ---

 Mở khóa sự sáng tạo của bạn thông qua quá trình khám phá có hướng dẫn.
--- a/docs/vi-vn/explanation/checkpoint-preview.md
+++ b/docs/vi-vn/explanation/checkpoint-preview.md
@ -2,7 +2,7 @@
 title: "Xem trước Checkpoint"
 description: Review có người trong vòng lặp với hỗ trợ của LLM, dẫn bạn đi qua thay đổi từ mục đích đến chi tiết
 sidebar:
-  order: 3
+  order: 8
 ---

 `bmad-checkpoint-preview` là một workflow review tương tác có người trong vòng lặp với hỗ trợ của LLM. Nó dẫn bạn đi qua một thay đổi mã nguồn, từ mục đích và bối cảnh đến các chi tiết quan trọng, để bạn có thể quyết định có nên phát hành, làm lại, hay đào sâu thêm.
--- a/docs/vi-vn/explanation/established-projects-faq.md
+++ b/docs/vi-vn/explanation/established-projects-faq.md
@ -2,7 +2,7 @@
 title: "FAQ cho dự án đã tồn tại"
 description: Các câu hỏi phổ biến khi dùng BMad Method trên dự án đã tồn tại
 sidebar:
-  order: 8
+  order: 12
 ---

 Các câu trả lời nhanh cho những câu hỏi thường gặp khi làm việc với dự án đã tồn tại bằng BMad Method (BMM).
--- a/docs/vi-vn/explanation/party-mode.md
+++ b/docs/vi-vn/explanation/party-mode.md
@ -2,7 +2,7 @@
 title: "Chế độ Party"
 description: Cộng tác đa agent - đưa tất cả agent AI vào cùng một cuộc trò chuyện
 sidebar:
-  order: 7
+  order: 10
 ---

 Đưa tất cả agent AI của bạn vào cùng một cuộc trò chuyện.
--- a/docs/vi-vn/explanation/preventing-agent-conflicts.md
+++ b/docs/vi-vn/explanation/preventing-agent-conflicts.md
@ -2,7 +2,7 @@
 title: "Ngăn xung đột giữa các agent"
 description: Cách kiến trúc ngăn xung đột khi nhiều agent cùng triển khai một hệ thống
 sidebar:
-     order: 4
+     order: 6
 ---

 Khi nhiều agent AI cùng triển khai các phần khác nhau của hệ thống, chúng có thể đưa ra các quyết định kỹ thuật mâu thuẫn nhau. Tài liệu kiến trúc ngăn điều đó bằng cách thiết lập các tiêu chuẩn dùng chung.
--- a/docs/vi-vn/explanation/project-context.md
+++ b/docs/vi-vn/explanation/project-context.md
@ -2,7 +2,7 @@
 title: "Bối cảnh dự án"
 description: Cách project-context.md định hướng các agent AI theo quy tắc và ưu tiên của dự án
 sidebar:
-  order: 7
+  order: 11
 ---

 Tệp `project-context.md` là kim chỉ nam cho việc triển khai của các agent AI trong dự án của bạn. Tương tự như một "bản hiến pháp" trong các hệ thống phát triển khác, nó ghi lại các quy tắc, pattern và ưu tiên giúp việc sinh mã được nhất quán trong mọi workflow.
--- a/docs/vi-vn/explanation/quick-dev.md
+++ b/docs/vi-vn/explanation/quick-dev.md
@ -2,7 +2,7 @@
 title: "Phát triển nhanh"
 description: Giảm ma sát có người trong vòng lặp mà vẫn giữ các điểm kiểm tra bảo vệ chất lượng đầu ra
 sidebar:
-  order: 2
+  order: 7
 ---

 Đưa ý định vào, nhận thay đổi mã nguồn ra, với số lần cần con người nhảy vào giữa quy trình ít nhất có thể - nhưng không đánh đổi chất lượng.
--- a/docs/vi-vn/explanation/why-solutioning-matters.md
+++ b/docs/vi-vn/explanation/why-solutioning-matters.md
@ -2,7 +2,7 @@
 title: "Vì sao solutioning quan trọng"
 description: Hiểu vì sao giai đoạn solutioning là tối quan trọng đối với dự án nhiều epic
 sidebar:
-  order: 3
+  order: 5
 ---

 Giai đoạn 3 (Solutioning) biến **xây gì** (từ giai đoạn Planning) thành **xây như thế nào** (thiết kế kỹ thuật). Giai đoạn này ngăn xung đột giữa các agent trong dự án nhiều epic bằng cách ghi lại các quyết định kiến trúc trước khi bắt đầu triển khai.
--- a/docs/vi-vn/how-to/established-projects.md
+++ b/docs/vi-vn/how-to/established-projects.md
@ -2,7 +2,7 @@
 title: "Dự án đã tồn tại"
 description: Cách sử dụng BMad Method trên các codebase hiện có
 sidebar:
-  order: 6
+  order: 7
 ---

 Sử dụng BMad Method hiệu quả khi làm việc với các dự án hiện có và codebase legacy.
--- a/docs/vi-vn/how-to/expand-bmad-for-your-org.md
+++ b/docs/vi-vn/how-to/expand-bmad-for-your-org.md
@ -2,7 +2,7 @@
 title: 'Cách mở rộng BMad cho tổ chức của bạn'
 description: Năm mẫu tùy chỉnh giúp thay đổi BMad mà không cần fork, gồm quy tắc ở cấp agent, quy ước workflow, xuất bản ra hệ thống ngoài, thay template và điều chỉnh danh sách agent
 sidebar:
-  order: 9
+  order: 11
 ---

 Bề mặt tùy chỉnh của BMad cho phép một tổ chức định hình lại hành vi mà không phải sửa file đã cài hay fork skill. Hướng dẫn này trình bày năm công thức mẫu (recipe) bao phủ phần lớn nhu cầu ở môi trường doanh nghiệp.
--- a/docs/vi-vn/how-to/get-answers-about-bmad.md
+++ b/docs/vi-vn/how-to/get-answers-about-bmad.md
@ -2,7 +2,7 @@
 title: "Cách tìm câu trả lời về BMad"
 description: Sử dụng LLM để tự nhanh chóng trả lời các câu hỏi về BMad
 sidebar:
-        order: 4
+        order: 5
 ---

 Hãy dùng trợ giúp tích hợp sẵn của BMad, tài liệu nguồn, hoặc cộng đồng để tìm câu trả lời, theo thứ tự từ nhanh nhất đến đầy đủ nhất.
--- a/docs/vi-vn/how-to/project-context.md
+++ b/docs/vi-vn/how-to/project-context.md
@ -2,7 +2,7 @@
 title: "Quản lý bối cảnh dự án"
 description: Tạo và duy trì project-context.md để định hướng cho các agent AI
 sidebar:
-  order: 8
+  order: 9
 ---

 Sử dụng tệp `project-context.md` để đảm bảo các agent AI tuân theo ưu tiên kỹ thuật và quy tắc triển khai của dự án trong suốt mọi workflow. Để đảm bảo tệp này luôn sẵn có, bạn cũng có thể thêm dòng `Important project context and conventions are located in [path to project context]/project-context.md` vào file context của công cụ hoặc file always rules của bạn (như `AGENTS.md`).
--- a/docs/vi-vn/how-to/quick-fixes.md
+++ b/docs/vi-vn/how-to/quick-fixes.md
@ -2,7 +2,7 @@
 title: "Sửa nhanh"
 description: Cách thực hiện các sửa nhanh và thay đổi ad-hoc
 sidebar:
-  order: 5
+  order: 6
 ---

 Sử dụng **Quick Dev** cho sửa lỗi, refactor, hoặc các thay đổi nhỏ có mục tiêu rõ ràng mà không cần quy trình BMad Method đầy đủ.
--- a/docs/vi-vn/how-to/shard-large-documents.md
+++ b/docs/vi-vn/how-to/shard-large-documents.md
@ -2,7 +2,7 @@
 title: "Hướng dẫn chia nhỏ tài liệu"
 description: Tách các tệp markdown lớn thành nhiều tệp nhỏ có tổ chức để quản lý context tốt hơn
 sidebar:
-       order: 9
+       order: 10
 ---

 Sử dụng công cụ `bmad-shard-doc` nếu bạn cần tách các tệp markdown lớn thành nhiều tệp nhỏ có tổ chức để quản lý context tốt hơn.
--- a/docs/vi-vn/how-to/upgrade-to-v6.md
+++ b/docs/vi-vn/how-to/upgrade-to-v6.md
@ -2,7 +2,7 @@
 title: "Cách nâng cấp lên v6"
 description: Di chuyển từ BMad v4 sang v6
 sidebar:
-  order: 3
+  order: 4
 ---

 Sử dụng trình cài đặt BMad để nâng cấp từ v4 lên v6, bao gồm khả năng tự động phát hiện bản cài đặt cũ và hỗ trợ di chuyển.
--- a/docs/vi-vn/reference/commands.md
+++ b/docs/vi-vn/reference/commands.md
@ -2,7 +2,7 @@
 title: Các skill
 description: Tài liệu tham chiếu cho skill của BMad — skill là gì, hoạt động ra sao và tìm ở đâu.
 sidebar:
-  order: 3
+  order: 4
 ---

 Skills là các prompt dựng sẵn để nạp agent, chạy workflow hoặc thực thi task bên trong IDE của bạn. Trình cài đặt BMad sinh chúng từ các module bạn đã chọn tại thời điểm cài đặt. Nếu sau này bạn thêm, xóa hoặc thay đổi module, hãy chạy lại trình cài đặt để đồng bộ skills (xem [Khắc phục sự cố](#khắc-phục-sự-cố)).
--- a/docs/vi-vn/reference/core-tools.md
+++ b/docs/vi-vn/reference/core-tools.md
@ -2,7 +2,7 @@
 title: Công cụ cốt lõi
 description: Tài liệu tham chiếu cho mọi tác vụ và quy trình tích hợp sẵn có trong mọi bản cài BMad mà không cần module bổ sung.
 sidebar:
-  order: 2
+  order: 3
 ---

 Mọi bản cài BMad đều bao gồm một tập skill cốt lõi có thể dùng cùng với bất cứ việc gì bạn đang làm, các tác vụ và quy trình độc lập hoạt động xuyên suốt mọi dự án, mọi module và mọi giai đoạn. Chúng luôn có sẵn bất kể bạn cài những module tùy chọn nào.
--- a/docs/vi-vn/reference/modules.md
+++ b/docs/vi-vn/reference/modules.md
@ -2,7 +2,7 @@
 title: Các Module Chính Thức
 description: Các module bổ sung để xây agent tùy chỉnh, tăng cường sáng tạo, phát triển game và kiểm thử
 sidebar:
-  order: 4
+  order: 5
 ---

 BMad được mở rộng thông qua các module chính thức mà bạn chọn trong quá trình cài đặt. Những module bổ sung này cung cấp agent, workflow và task chuyên biệt cho các lĩnh vực cụ thể, vượt ra ngoài phần lõi tích hợp sẵn và BMM (Agile suite).
--- a/docs/vi-vn/reference/testing.md
+++ b/docs/vi-vn/reference/testing.md
@ -2,7 +2,7 @@
 title: Các Tùy Chọn Kiểm Thử
 description: So sánh workflow QA tích hợp sẵn với module Test Architect (TEA) cho tự động hóa kiểm thử.
 sidebar:
-  order: 5
+  order: 6
 ---

 BMad cung cấp hai hướng kiểm thử: workflow QA tích hợp sẵn để tạo test nhanh và module Test Architect có thể cài thêm cho chiến lược kiểm thử c<><63>p doanh nghiệp.
--- a/docs/zh-cn/explanation/advanced-elicitation.md
+++ b/docs/zh-cn/explanation/advanced-elicitation.md
@ -2,7 +2,7 @@
 title: "高级启发"
 description: 使用结构化推理方法推动 LLM 重新思考其工作
 sidebar:
-  order: 6
+  order: 4
 ---

 高级启发（advanced elicitation）是“第二轮思考”机制：不是笼统地让模型“再来一次”，而是让它按指定推理方法重审自己的输出。
--- a/docs/zh-cn/explanation/adversarial-review.md
+++ b/docs/zh-cn/explanation/adversarial-review.md
@ -2,7 +2,7 @@
 title: "对抗性评审"
 description: 防止懒惰“看起来不错”评审的强制推理技术
 sidebar:
-  order: 5
+  order: 9
 ---

 对抗性评审（adversarial review）是一种“强制找问题”的评审方法：不允许直接“Looks good”，必须给出可验证发现，或者明确解释为什么没有发现。
--- a/docs/zh-cn/explanation/analysis-phase.md
+++ b/docs/zh-cn/explanation/analysis-phase.md
@ -2,7 +2,7 @@
 title: "分析阶段：从想法到基础"
 description: 头脑风暴、调研、产品简报和 PRFAQ 分别是什么——以及何时使用
 sidebar:
-  order: 1
+  order: 2
 ---

 分析阶段（Phase 1）帮助你在决定动手构建之前，把产品想清楚。这个阶段的每个工具都是可选的，但如果完全跳过分析，你的 PRD 就是建立在假设而非洞察之上。
--- a/docs/zh-cn/explanation/brainstorming.md
+++ b/docs/zh-cn/explanation/brainstorming.md
@ -2,7 +2,7 @@
 title: "头脑风暴"
 description: 使用 60+ 种经过验证的构思技术进行互动创意会议
 sidebar:
-  order: 2
+  order: 3
 ---

 `bmad-brainstorming` 是一个“思考引导”工作流：它不替你拍脑袋给答案，而是用结构化提问把你的想法挖出来、扩展开、再收敛成可执行方向。
--- a/docs/zh-cn/explanation/checkpoint-preview.md
+++ b/docs/zh-cn/explanation/checkpoint-preview.md
@ -2,7 +2,7 @@
 title: "检查点预览"
 description: LLM 辅助的人机协作审查，引导你从目的到细节逐步走过一个变更
 sidebar:
-  order: 3
+  order: 8
 ---

 `bmad-checkpoint-preview` 是一个交互式的、LLM 辅助的人机协作审查工作流。它带你逐步走过一个代码变更——从目的和上下文到细节——让你能做出知情决策：是发布、返工，还是深入挖掘。
--- a/docs/zh-cn/explanation/established-projects-faq.md
+++ b/docs/zh-cn/explanation/established-projects-faq.md
@ -2,7 +2,7 @@
 title: "既有项目常见问题"
 description: 关于在既有项目上使用 BMad Method 的常见问题
 sidebar:
-  order: 8
+  order: 12
 ---
 关于在 established projects（既有项目）中使用 BMad Method 的高频问题，快速说明如下。

--- a/docs/zh-cn/explanation/party-mode.md
+++ b/docs/zh-cn/explanation/party-mode.md
@ -2,7 +2,7 @@
 title: "派对模式"
 description: 多智能体协作——将所有 AI 智能体汇聚到一次对话中
 sidebar:
-  order: 7
+  order: 10
 ---

 `bmad-party-mode` 用于多角色协作讨论：把 PM、架构、开发、UX 等视角放到同一轮对话里，快速暴露分歧、对齐取舍。
--- a/docs/zh-cn/explanation/preventing-agent-conflicts.md
+++ b/docs/zh-cn/explanation/preventing-agent-conflicts.md
@ -2,7 +2,7 @@
 title: "防止智能体冲突"
 description: 架构如何在多个智能体实现系统时防止冲突
 sidebar:
-  order: 4
+  order: 6
 ---

 当多个 AI 智能体并行实现系统时，冲突并不罕见。`architecture` 的作用，就是在 `solutioning` 阶段先统一关键决策，避免到 `epic/story` 实施时才暴露分歧。
--- a/docs/zh-cn/explanation/project-context.md
+++ b/docs/zh-cn/explanation/project-context.md
@ -2,7 +2,7 @@
 title: "项目上下文"
 description: project-context.md 如何使用项目规则和偏好指导 AI 智能体
 sidebar:
-  order: 7
+  order: 11
 ---

 `project-context.md` 是面向 AI 智能体的项目级上下文文件。它的定位不是教程步骤，而是“实现约束说明”：把你的技术偏好、架构边界和工程约定沉淀成可复用规则，让不同工作流、不同智能体在多个 `story` 中做出一致决策。
--- a/docs/zh-cn/explanation/quick-dev.md
+++ b/docs/zh-cn/explanation/quick-dev.md
@ -2,7 +2,7 @@
 title: "快速开发"
 description: 在不牺牲输出质量检查点的情况下减少人机交互的摩擦
 sidebar:
-  order: 2
+  order: 7
 ---

 `bmad-quick-dev` 的目标很直接：在保证质量边界的前提下，把“意图到代码”的人机往返轮次降到最低。
--- a/docs/zh-cn/explanation/why-solutioning-matters.md
+++ b/docs/zh-cn/explanation/why-solutioning-matters.md
@ -2,7 +2,7 @@
 title: "为什么解决方案阶段很重要"
 description: 理解为什么解决方案阶段对于多史诗项目至关重要
 sidebar:
-  order: 3
+  order: 5
 ---

 Phase 3（solutioning）把“要做什么”（planning 产出）转成“如何实现”（`architecture` 设计 + 工作拆分）。它的核心价值是：在开发前先把跨 `epic` 的关键技术决策写清楚，让后续 `story` 实施保持一致。
--- a/docs/zh-cn/how-to/customize-bmad.md
+++ b/docs/zh-cn/how-to/customize-bmad.md
@ -2,7 +2,7 @@
 title: "如何自定义 BMad"
 description: 自定义智能体、工作流和模块，同时保持更新兼容性
 sidebar:
-  order: 7
+  order: 8
 ---

 使用 `.customize.yaml` 文件，自定义智能体（agent）的行为、角色（persona）和菜单，同时在后续更新中保留你的改动。
--- a/docs/zh-cn/how-to/established-projects.md
+++ b/docs/zh-cn/how-to/established-projects.md
@ -2,7 +2,7 @@
 title: "既有项目"
 description: 如何在现有代码库中使用 BMad Method
 sidebar:
-  order: 6
+  order: 7
 ---

 当你在现有项目或遗留代码库上工作时，本指南帮助你更稳妥地使用 BMad Method。
--- a/docs/zh-cn/how-to/expand-bmad-for-your-org.md
+++ b/docs/zh-cn/how-to/expand-bmad-for-your-org.md
@ -2,7 +2,7 @@
 title: "如何为组织扩展 BMad"
 description: 五个自定义方案，无需 fork 即可重塑 BMad——涵盖智能体全局规则、工作流约定、外部发布、模板替换和花名册变更
 sidebar:
-  order: 9
+  order: 11
 ---

 BMad 的自定义机制让组织无需编辑已安装文件或 fork 技能就能重塑行为。本指南介绍五个方案，覆盖大部分企业级需求。
--- a/docs/zh-cn/how-to/get-answers-about-bmad.md
+++ b/docs/zh-cn/how-to/get-answers-about-bmad.md
@ -2,7 +2,7 @@
 title: "如何获取关于 BMad 的答案"
 description: 使用 LLM 快速回答您自己的 BMad 问题
 sidebar:
-  order: 4
+  order: 5
 ---

 ## 先从 BMad-Help 开始
--- a/docs/zh-cn/how-to/project-context.md
+++ b/docs/zh-cn/how-to/project-context.md
@ -2,7 +2,7 @@
 title: "管理项目上下文"
 description: 创建并维护 project-context.md 以指导 AI 智能体
 sidebar:
-  order: 8
+  order: 9
 ---

 使用 `project-context.md`，确保 AI 智能体在各类工作流中遵循项目的技术偏好与实现规则。
--- a/docs/zh-cn/how-to/quick-fixes.md
+++ b/docs/zh-cn/how-to/quick-fixes.md
@ -2,7 +2,7 @@
 title: "快速修复"
 description: 如何进行快速修复和临时更改
 sidebar:
-  order: 5
+  order: 6
 ---

 对于 bug 修复、重构或小范围改动，使用 **Quick Dev** 即可，不必走完整的 BMad Method。
--- a/docs/zh-cn/how-to/shard-large-documents.md
+++ b/docs/zh-cn/how-to/shard-large-documents.md
@ -2,7 +2,7 @@
 title: "文档分片指南"
 description: 将大型 Markdown 文件拆分为更小的组织化文件，以更好地管理上下文
 sidebar:
-  order: 9
+  order: 10
 ---

 当单个 Markdown 文档过大、影响模型读取时，可使用 `bmad-shard-doc` 工作流把文档拆成按章节组织的小文件，降低上下文压力。
--- a/docs/zh-cn/how-to/upgrade-to-v6.md
+++ b/docs/zh-cn/how-to/upgrade-to-v6.md
@ -2,7 +2,7 @@
 title: "如何升级到 v6"
 description: 从 BMad v4 迁移到 v6
 sidebar:
-  order: 3
+  order: 4
 ---

 使用 BMad 安装程序把 v4 升级到 v6。安装程序会自动识别旧安装，并提供迁移辅助，帮助你在已有项目中平滑过渡。
--- a/docs/zh-cn/reference/commands.md
+++ b/docs/zh-cn/reference/commands.md
@ -2,7 +2,7 @@
 title: "技能（Skills）"
 description: BMad 技能参考：它们是什么、如何生成以及如何调用。
 sidebar:
-  order: 3
+  order: 4
 ---

 每次运行 `npx bmad-method install`，BMad 会基于你选择的模块生成一组 **skills**。你可以直接输入 skill 名称调用 workflow、任务、工具或智能体角色。
--- a/docs/zh-cn/reference/core-tools.md
+++ b/docs/zh-cn/reference/core-tools.md
@ -2,7 +2,7 @@
 title: "核心工具"
 description: 每个 BMad 安装默认可用的任务与 workflow 参考。
 sidebar:
-  order: 2
+  order: 3
 ---

 核心工具是跨模块可复用的一组通用能力：不依赖特定业务项目，也不要求先进入某个智能体角色。只要安装了 BMad，你就可以直接调用它们。
--- a/docs/zh-cn/reference/modules.md
+++ b/docs/zh-cn/reference/modules.md
@ -2,7 +2,7 @@
 title: "官方模块"
 description: BMad 可选模块参考：能力边界、适用场景与外部资源
 sidebar:
-  order: 4
+  order: 5
 ---

 BMad 通过可选模块扩展能力。你可以在安装时按需选择模块，为当前项目增加特定领域的 `agent`、`workflow` 与 `skill`。
--- a/docs/zh-cn/reference/testing.md
+++ b/docs/zh-cn/reference/testing.md
@ -2,7 +2,7 @@
 title: "测试选项"
 description: 内置 QA workflow 与 TEA 模块对比：何时用哪个、各自边界是什么
 sidebar:
-  order: 5
+  order: 6
 ---

 BMad 有两条测试路径：
--- a/package-lock.json
+++ b/package-lock.json
@ -1,12 +1,12 @@
 {
  "name": "bmad-method",
-  "version": "6.7.1",
+  "version": "6.8.0",
  "lockfileVersion": 3,
  "requires": true,
  "packages": {
    "": {
      "name": "bmad-method",
-      "version": "6.7.1",
+      "version": "6.8.0",
      "license": "MIT",
      "dependencies": {
        "@clack/core": "^1.3.1",
--- a/package.json
+++ b/package.json
@ -1,7 +1,7 @@
 {
  "$schema": "https://json.schemastore.org/package.json",
  "name": "bmad-method",
-  "version": "6.7.1",
+  "version": "6.8.0",
  "description": "Breakthrough Method of Agile AI-driven Development",
  "keywords": [
    "agile",
@ -31,6 +31,7 @@
    "docs:fix-links": "node tools/fix-doc-links.js",
    "docs:preview": "astro preview --root website",
    "docs:validate-links": "node tools/validate-doc-links.js",
+    "docs:validate-sidebar": "node tools/validate-sidebar-order.js",
    "format:check": "prettier --check \"**/*.{js,cjs,mjs,json,yaml}\"",
    "format:fix": "prettier --write \"**/*.{js,cjs,mjs,json,yaml}\"",
    "format:fix:staged": "prettier --write",
@ -39,7 +40,7 @@
    "lint:fix": "eslint . --ext .js,.cjs,.mjs,.yaml --fix",
    "lint:md": "markdownlint-cli2 \"**/*.md\"",
    "prepare": "command -v husky >/dev/null 2>&1 && husky || exit 0",
-    "quality": "npm run format:check && npm run lint && npm run lint:md && npm run docs:build && npm run test:install && npm run test:urls && npm run validate:refs && npm run validate:skills",
+    "quality": "npm run format:check && npm run lint && npm run lint:md && npm run docs:build && npm run test:install && npm run test:urls && npm run validate:refs && npm run validate:skills && npm run docs:validate-sidebar",
    "rebundle": "node tools/installer/bundlers/bundle-web.js rebundle",
    "test": "npm run test:refs && npm run test:install && npm run test:urls && npm run test:channels && npm run lint && npm run lint:md && npm run format:check",
    "test:channels": "node test/test-installer-channels.js",
--- a/removals.txt
+++ b/removals.txt
@ -57,3 +57,6 @@ bmad-bmm-validate-prd
 # bmad-distillator: superseded by bmad-spec (universal intent distiller with
 # preservation-validated contract for downstream skills).
 bmad-distillator
+# bmad-create-ux-design: renamed to bmad-ux (spine-based skill with separate
+# DESIGN.md and EXPERIENCE.md outputs).
+bmad-create-ux-design
--- a/src/bmm-skills/1-analysis/bmad-agent-analyst/SKILL.md
+++ b/src/bmm-skills/1-analysis/bmad-agent-analyst/SKILL.md
@ -63,6 +63,8 @@ Continue to prefix your messages with `{agent.icon}` throughout the session so t

 Execute each entry in `{agent.activation_steps_append}` in order.

+Activation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.
+
 ### Step 8: Dispatch or Present the Menu

 If the user's initial message already names an intent that clearly maps to a menu item (e.g. "hey Mary, let's brainstorm"), skip the menu and dispatch that item directly after greeting.
--- a/src/bmm-skills/1-analysis/bmad-agent-tech-writer/SKILL.md
+++ b/src/bmm-skills/1-analysis/bmad-agent-tech-writer/SKILL.md
@ -63,6 +63,8 @@ Continue to prefix your messages with `{agent.icon}` throughout the session so t

 Execute each entry in `{agent.activation_steps_append}` in order.

+Activation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.
+
 ### Step 8: Dispatch or Present the Menu

 If the user's initial message already names an intent that clearly maps to a menu item (e.g. "hey Paige, let's document this codebase"), skip the menu and dispatch that item directly after greeting.
--- a/src/bmm-skills/1-analysis/bmad-document-project/SKILL.md
+++ b/src/bmm-skills/1-analysis/bmad-document-project/SKILL.md
@ -55,7 +55,7 @@ Greet `{user_name}` (if you have not already), speaking in `{communication_langu

 Execute each entry in `{workflow.activation_steps_append}` in order.

-Activation is complete. Begin the workflow below.
+Activation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.

 ## Execution

--- a/src/bmm-skills/1-analysis/bmad-prfaq/SKILL.md
+++ b/src/bmm-skills/1-analysis/bmad-prfaq/SKILL.md
@ -65,7 +65,7 @@ Greet `{user_name}`, speaking in `{communication_language}`. Be warm but efficie

 Execute each entry in `{workflow.activation_steps_append}` in order.

-Activation is complete. Continue below.
+Activation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.

 ## Pre-workflow Setup

--- a/src/bmm-skills/1-analysis/bmad-product-brief/SKILL.md
+++ b/src/bmm-skills/1-analysis/bmad-product-brief/SKILL.md
@ -21,7 +21,10 @@ At the opening greeting, let the user know they can invoke `bmad-party-mode` for
 4. `{workflow.external_sources}` is an org-configured registry of internal tools (knowledge bases, MCP tools); consult them alongside generic web research on the same triggers in `## Discovery`, org tools preferred when their directive matches. If a named tool is unavailable at runtime, fall back to standard behavior and note the gap when relevant.
 5. Load `{project-root}/_bmad/bmm/config.yaml` (and `config.user.yaml` if present). Resolve `{user_name}`, `{communication_language}`, `{document_output_language}`, `{planning_artifacts}`, `{project_name}`, `{date}`.
 6. Greet `{user_name}` in `{communication_language}` — and stay in `{communication_language}` for every turn for the entire run, not just the greeting. Detect intent (create / update / validate). If interactive and intent is unclear, ask; for headless behavior see `## Headless Mode`.
-7. Execute each entry in `{workflow.activation_steps_append}` in order.
+
+Execute each entry in `{workflow.activation_steps_append}` in order.
+
+Activation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.

 ## Intent Operating Modes

--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
Emmanuel Atsé	dc2c13a300	Merge remote-tracking branch 'bmad-upstream/main' into i18n/fr_FR	2026-05-26 01:15:24 +02:00
github-actions[bot]	3bcd6c3cce	chore(release): v6.8.0 [skip ci]	2026-05-25 21:47:24 +00:00
Brian	62c836ee61	docs(changelog): v6.8.0 release notes (#2427 )	2026-05-25 16:46:38 -05:00
Emmanuel Atsé	7e61177690	docs(fr): fix missing french typography on roadmap.mdx	2026-05-25 21:44:10 +02:00
Emmanuel Atsé	2510a2a4ba	Merge remote-tracking branch 'bmad-upstream/main' into i18n/fr_FR	2026-05-25 21:42:46 +02:00
hanhnt2-hblab	db744d405f	fix: support nested group paths in SSH Git URLs (#2379 ) Co-authored-by: Brian <bmadcode@gmail.com>	2026-05-25 14:15:04 -05:00
Jacob du Toit	7b31b1accd	feat: expand advanced elicitation methods with 19 new techniques (#2062 ) Adds 19 new elicitation methods across 7 categories including a new 'framing' category. All existing 50 methods preserved. Entries sorted alphabetically by category then method name. New methods added: - advanced: Chain-of-Thought Scaffolding, Few-Shot Exemplar Priming - collaboration: Six Thinking Hats, Delphi Method - core: Second-Order Thinking, Inversion Analysis, Problem Decomposition, Analogy Mapping, Steelmanning - creative: Constraint Injection, Morphological Analysis - framing (new): Abstraction Laddering, Reframe the Question, Stakeholder Lens Rotation - learning: Deliberate Practice Loop - research: Source Triangulation - risk: Assumption Audit, Cascading Failure Simulation - technical: Boundary & Edge Case Sweep Closes #2061 Co-authored-by: Brian <bmadcode@gmail.com> Co-authored-by: Alex Verkhovsky <alexey.verkhovsky@gmail.com>	2026-05-25 14:09:17 -05:00
Jérôme Revillard	9c291b7ca9	fix: resolve default branch explicitly when updating shallow-cloned custom modules (#2332 ) With shallow clones (--depth 1), `origin/HEAD` becomes stale after the initial clone. The update path used `git reset --hard origin/HEAD` which never picked up new commits pushed to the default branch. Resolve the default branch name via `git symbolic-ref refs/remotes/origin/HEAD`, then fetch and reset against `origin/<branch>` explicitly. Falls back to `main` if origin/HEAD is not set. Co-authored-by: Brian <bmadcode@gmail.com>	2026-05-25 14:05:59 -05:00
robertocsko-seon	fea431fd2e	fix(installer): read config.toml on re-run so user_name (and other user-scoped answers) are preserved as defaults (#2411 ) loadExistingConfig only read from legacy _bmad/<module>/config.yaml files, but the installer writes user-scoped answers (user_name, communication_language, etc.) to _bmad/config.user.toml. On every subsequent reinstall those values were not loaded back, so the user got re-prompted instead of seeing their prior answers as defaults. Adds parseCentralToml — a lightweight line scanner matching the installer's own TOML output format — and updates loadExistingConfig to read config.toml and config.user.toml first (merging both into the same section buckets). Legacy per-module config.yaml files are kept as a fallback for pre-v6 installations. Co-authored-by: RobertOcsko <robert.ocsko@;seon.io> Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com> Co-authored-by: Brian <bmadcode@gmail.com>	2026-05-25 13:56:05 -05:00
SevenSteven	9a2fba97a3	fix: capture dev story baseline commits (#2403 ) Co-authored-by: Brian <bmadcode@gmail.com>	2026-05-25 13:50:08 -05:00
Farzad Rashidi	065003fc95	Fix stale custom-source redeploys on quick-update (#2399 ) * fix(installer): refresh custom-source cache on quick-update and persist channel marker * fix(installer): persist real next ref and atomically dedupe custom refresh * fix(installer): preserve custom-source cache when remote unreachable When git fetch fails against an existing custom-module cache, cloneRepo previously wiped the cache and attempted a fresh clone, which then also failed for the same reason (network down, repo deleted/moved, auth revoked) — leaving the user with no usable cache. With the new quick-update refresh path calling cloneRepo for every cached custom module, this turned transient remote outages into cache loss on every quick-update. - cloneRepo: on fetch failure with an existing cache, keep the previous clone and surface a warning via prompts.log.warn instead of removing the cache. The downstream metadata write uses the existing HEAD. - _refreshRepoCacheOnce: update the comment to reflect that the common "remote unreachable but cache exists" case is now handled inside cloneRepo; warn on the remaining unrecoverable failures so they aren't silent. Tests: 349 passed, 0 failed. --------- Co-authored-by: Brian Madison <bmadcode@gmail.com>	2026-05-25 13:39:04 -05:00
Brian	7729ad461d	docs: route all web-bundles install traffic to bmadcode.com/web-bundles (#2425 ) Make bmadcode.com/web-bundles/ the single supported install path. The site keeps install steps current as Gemini and ChatGPT evolve, always points at the newest tagged release, and turns one signup into the notification channel for new bundles. - README.md: drop direct-folder install reference, point to the site - web-bundles/README.md: lead with Install (site), reframe folder as source for the shelf rather than install target - docs/explanation/web-bundles.md: replace the per-bundle INSTRUCTIONS.md steer with the site, replace the dead how-to link - docs/how-to/use-web-bundles.md: rewrite as a short pointer to the site (kept the file so existing inbound links resolve), retain prerequisites, persona customization, and build-your-own sections	2026-05-25 12:17:27 -05:00
Brian	2b76d03316	feat(web-bundles): release packager + manifest for bmadcode.com/web-bundles/ (#2424 ) * feat(web-bundles): add release packager + bundle manifest Adds the infrastructure for shipping web bundles as downloadable ZIPs attached to a GitHub Release, consumed by the upcoming bmadcode.com/web-bundles/ page. - web-bundles/bundles.json — manifest with persona, tagline, description, accent color, motif key, knowledge files, and feature flags (web-browsing, deep-research, stitch integration) for each of the 6 bundles. Top-level releaseTag and downloadUrlPattern so the consuming page can construct download URLs without hardcoding. - tools/bundle-web-bundles.js — packager that zips each bundle dir into dist/web-bundles/{slug}.zip and prints the gh release create command. Zero dependencies; uses system zip. - .gitignore — exclude dist/web-bundles/ build artifacts. The web-bundles-v1.0.0 release on GitHub is currently in draft state with the 6 zips attached; it'll be published in coordination with the Ghost site page going live. * fix(web-bundles): single-source release tag, sharper bundle copy - Remove downloadUrlPattern from bundles.json — the consuming page derives the URL from releaseTag, so version bumps now touch one field instead of two. - product-brief-coach: drop "one-page" (briefs are whatever length the product earns). - brainstorming-coach: real numbers — 60 techniques across 10 categories — with concrete examples (SCAMPER, Drunk History Retelling, Nature's Solutions, Six Thinking Hats, etc.) so the card actually communicates the surprising breadth. * fix(web-bundles): harden release script per PR review - Verify the zip CLI is on PATH up front with a clear install hint, instead of crashing mid-zip with an opaque execSync error. - Wrap JSON.parse in try/catch; validate the manifest shape (bundles array non-empty, releaseTag present, slug present per entry) before trying to package, so config errors fail with a targeted message. - Catch zip failures per-bundle and surface the failing slug. - Refuse to print the gh release command when zero bundles were packaged (would otherwise mislead the user into creating an empty release). - Derive --title from manifest.releaseTag so the printed command can never drift from the actual tag (was previously hardcoded "Web Bundles v1" while the tag had moved to v1.0.0). - Remove the stale `web-bundles-v1` example from the file header. Addresses augmentcode bot review comments on PR #2424. * docs(web-bundles): rewrite copy to actually sell what each bundle does The JSON drives the bmadcode.com/web-bundles/ page; previous copy was generic and undersold the actual capabilities. Rewrote each tagline + description to lead with concrete, differentiating facts pulled directly from each bundle's SKILL.md: - Brainstorming Coach: 60 techniques across 10 categories with specific names (SCAMPER, Drunk History Retelling, Nature's Solutions, Shadow Work Mining, Superposition Collapse); calls out the 4 routes (browse, recommend, random, progressive) and the ~100-idea quantity-unlocks-quality target. - Product Brief Coach: names the three intent modes (Create / Update / Validate) and the two working paths (Fast / Coaching); surfaces the [ASSUMPTION] tag system and the Addendum. - PRFAQ Coach: details the 4 stages (Ignition / Press Release / Customer FAQ / Internal FAQ + Verdict), the 9 press release sections, the weasel-word list ("best-in-class", "seamless"), and that it adapts for commercial, internal, OSS, community. - PRD Coach: spells out the two entry points (Vision+Features vs Journey-led), named-protagonist journeys, glossary discipline, stable ID system (FR-1..N, SM-C1..N), and the 7-dimension validation rubric. - UX Coach: leads with the two-spine contract (DESIGN.md + EXPERIENCE.md), Don Norman framing, named-protagonist journeys, surface closure as the test, and Stitch integration. - Market & Industry Research: leads with Deep Research as the engine, names Porter and Christensen as anchors, lists the 6 deliverable sections, and frames the deliverable as synthesis not a research dump. * fix(web-bundles): security hardening + strict bundle validation Two issues raised by coderabbit on the latest commit: 1. Shell injection surface: execSync was building the zip command with a template literal that interpolated bundle.slug from JSON. Even with our controlled inputs, a slug with shell metacharacters would break quoting. Switched to execFileSync with an argument array (no shell) and added a strict ^[a-z0-9][a-z0-9-]*$ slug regex enforced before any FS or zip call. 2. Missing bundle directories were [SKIP]-warned but the script still printed the release command, allowing an incomplete release to ship cleanly. Now treated as fatal: any missing or invalid slug blocks the printed gh command and exits non-zero with the offending slugs listed.	2026-05-25 11:43:55 -05:00
Emmanuel Atsé	cede485217	feat(docs): Add sidebar order validator for doc frontmatter (#2409 ) * feat(docs): add sidebar order validator Adds tools/validate-sidebar-order.js to validate sidebar.order values in YAML frontmatter across English and translated docs. Checks for duplicate orders, gaps in sequence, and missing order fields. For translations, also warns on order drift from English counterparts. Wired into the quality script as docs:validate-sidebar. * fix(validate-sidebar): tighten language detection and drift guard, add docstrings * fix(validate-sidebar): replace subdirectory heuristic with locale pattern matching detectLanguageDirs() previously classified any top-level docs/ directory containing subdirectories as a translation language. This was too broad — if an English section ever gained nested subfolders it would be silently excluded from validation. Replaced with a BCP 47 locale-code regex (/^[a-z]{2}(?:-[a-zA-Z]{2})?$/) that matches known patterns (cs, fr, vi-vn, zh-cn) and won't falsely classify content sections like explanation/ or reference/. * fix(validate-sidebar): guard drift check against undefined order values extractSidebarOrder() returns { hasSidebar: false } when no sidebar block exists, leaving order as undefined rather than null. The drift check only guarded against null, allowing undefined values to emit noisy warnings like "Order drift: ... order undefined". Changed the guard to typeof === 'number' which correctly excludes both undefined and null without relying on a specific sentinel value. * chore(validate-sidebar): add JSDoc docstrings to all functions Adds @param and @returns annotations to extractSidebarOrder, detectLanguageDirs, getEnglishSections, checkDirectory, checkTranslationDrift, and relativePath. * fix(validate-sidebar): add to pre-commit hook * refactor(validate-sidebar): harden parsing and edge-case handling Refactor to main() wrapper with pure return-based APIs, single directory scan, and shared reporting. Harden frontmatter parsing (anchored delimiter, direct-child-only order extraction, flow mapping support) and validation (Infinity/zero guard, gap flood cap, multi-segment locales, graceful ENOENT). * docs: fix sidebar.order duplicates and gaps across all locales Resolves all validator errors flagged by the new tools/validate-sidebar-order.js check. English (docs/{explanation,how-to,reference}/): - Renumbered to remove duplicates; established reading order for new explanation pages added since orders were last set. Translations (cs, fr, vi-vn, zh-cn): - Mirrored English structural ordering where files exist, then compacted to 1..N within each directory to eliminate gaps caused by missing translation files. Non-blocking drift warnings remain where translation directories have fewer files than English; these are expected per the validator's design. --------- Co-authored-by: Brian Madison <bmadcode@gmail.com>	2026-05-25 10:15:37 -05:00
Jérôme Revillard	436845493f	fix(skills): strengthen activation guardrails to prevent LLM short-circuiting (#2398 ) * fix(skills): strengthen activation guardrails for all workflow skills Add explicit "Activation is complete" boundary markers that require confirming activation_steps_prepend and activation_steps_append were fully executed before beginning the main workflow. Previously, the guardrail was either missing (bmad-product-brief, bmad-prd, bmad-investigate) or too weak ("Begin the workflow below"). LLM agents would short-circuit complex activation sequences (INCLUDE → READ → RUN → CHECK → FILTER → CD) by guessing variables instead of executing steps in order, causing append steps and on_complete hooks to be silently skipped. The new guardrail explicitly names both prepend and append steps, requiring confirmation before proceeding. This prevents agents from starting the main workflow in parallel with activation. 23 skills updated: bmad-product-brief, bmad-prd, bmad-prfaq, bmad-investigate, bmad-create-story, bmad-dev-story, bmad-quick-dev, bmad-code-review, bmad-correct-course, bmad-sprint-planning, bmad-sprint-status, bmad-retrospective, bmad-qa-generate-e2e-tests, bmad-checkpoint-preview, bmad-check-implementation-readiness, bmad-create-architecture, bmad-create-epics-and-stories, bmad-generate-project-context, bmad-create-ux-design, bmad-document-project, bmad-market-research, bmad-technical-research, bmad-domain-research. * fix(skills): extend activation gate to agent + new skills, refine placement - bmad-product-brief / bmad-prd: pull activation_steps_append out of the numbered list so the sentinel reads as a paragraph break, not as the next list item. - bmad-investigate: move the sentinel above Step 7 (routing) — Step 7 is workflow routing, not activation; the gate must fire first. - bmad-agent-{analyst,tech-writer,pm,ux-designer,architect,dev}: add the same gate between Step 7 (append) and Step 8 (menu dispatch). Persona skills had the same short-circuit risk but no sentinel. - bmad-ux, bmad-spec: new skills introduced on main after this branch forked; apply the same gate so the pattern stays consistent. - removals.txt: register bmad-create-ux-design as renamed to bmad-ux. --------- Co-authored-by: Brian Madison <bmadcode@gmail.com>	2026-05-25 09:59:38 -05:00
Alex Verkhovsky	1a5df418b3	fix: keep brainstorming idea flow collaborative (#2402 ) Co-authored-by: Brian <bmadcode@gmail.com>	2026-05-25 09:34:49 -05:00
Dov Benyomin Sohacheski	bfecb6ee95	fix(bmm-skills): define project_context in dev-story, sprint-planning, sprint-status (#2422 ) Co-authored-by: Brian <bmadcode@gmail.com>	2026-05-25 09:33:05 -05:00
Brian	d659a03d53	docs(web-bundles): fix install framing and add update/customize guidance (#2423 ) - Drop "one-click install" framing in README and explanation page; setup is multi-step but consistent across the shelf. - Drop "two files (sometimes three)" claim; honestly name SKILL.md, INSTRUCTIONS.md, and any required data files (templates, CSVs, validation checklists). - Add explicit setup pattern in README (create Gem/GPT, upload knowledge, paste instructions, save). - Add "Updating and customizing" section to the explanation page covering re-upload-the-attachments updates and the rule of thumb that custom changes belong in the pasted instructions block, not the knowledge files, so future updates don't clobber team customizations.	2026-05-25 09:27:24 -05:00
Brian	3bc2ad30a3	feat(web-bundles): bring back V4 web bundles for V6 (#2421 ) * feat(web-bundles): bring back V4 web bundles for V6 Restores the V4 web bundle pattern for V6. BMad planning skills are repackaged as one-click installs for Google Gemini Gems and ChatGPT Custom GPTs, so users can run analysis and planning conversations in flat-rate web LLM subscriptions instead of metered IDE tokens. Current shelf (6 bundles): brainstorming, product brief, PRFAQ, PRD, UX, market and industry research. Each bundle ships a SKILL.md protocol, an INSTRUCTIONS.md with a default persona and a contrasting swap example, and any required data files. New in this commit: - Market & Industry Research bundle merging market and domain research with Porter and Christensen anchors, Mary persona inherited from the BMad analyst agent, Geoffrey Moore swap example, Deep Research mode integrated as the default research path - web-bundles/README.md folder index listing all 6 bundles - README.md section announcing the V6 web bundle shelf - docs/explanation/web-bundles.md concept page (what, why, when) - docs/how-to/use-web-bundles.md install steps for Gemini Gems and ChatGPT Custom GPTs * docs(web-bundles): unindent admonition closer in use-web-bundles.md The :::note[Prerequisites] closer was indented under the last bullet, which can prevent the admonition from closing and break Starlight rendering for the rest of the page. Flush left now.	2026-05-25 08:46:19 -05:00