bmad-method 6.10.1-next.16 → 6.10.1-next.18

package/.claude-plugin/marketplace.json

@@ -7,41 +7,62 @@
   "license": "MIT",
   "homepage": "https://github.com/bmad-code-org/BMAD-METHOD",
   "repository": "https://github.com/bmad-code-org/BMAD-METHOD",
-  "keywords": ["bmad", "agile", "ai", "orchestrator", "development", "methodology", "agents"],
+  "keywords": ["bmad", "agile", "ai", "orchestrator", "development", "methodology", "agents", "brainstorming", "thinking"],
   "plugins": [
     {
-      "name": "bmad-pro-skills",
+      "name": "bmad-brainstorming",
       "source": "./",
-      "description": "Next level skills for power users — advanced prompting techniques, agent management, and more.",
-      "version": "6.8.0",
+      "description": "Facilitated brainstorming with a curated technique library — diverge, converge, and capture ideas with a visual technique picker.",
+      "version": "6.10.0",
       "author": {
         "name": "Brian (BMad) Madison"
       },
-      "skills": [
-        "./src/core-skills/bmad-help",
-        "./src/core-skills/bmad-brainstorming",
-        "./src/core-skills/bmad-customize",
-        "./src/core-skills/bmad-spec",
-        "./src/core-skills/bmad-party-mode",
-        "./src/core-skills/bmad-shard-doc",
-        "./src/core-skills/bmad-advanced-elicitation",
-        "./src/core-skills/bmad-editorial-review-prose",
-        "./src/core-skills/bmad-editorial-review-structure",
-        "./src/core-skills/bmad-index-docs",
-        "./src/core-skills/bmad-review-adversarial-general",
-        "./src/core-skills/bmad-review-edge-case-hunter",
-        "./src/core-skills/bmad-review-verification-gap"
-      ]
+      "skills": ["./src/core-skills/bmad-brainstorming"]
+    },
+    {
+      "name": "bmad-party-mode",
+      "source": "./",
+      "description": "Multi-perspective roundtable discussions — collide viewpoints between agents or custom personas to stress-test any topic.",
+      "version": "6.10.0",
+      "author": {
+        "name": "Brian (BMad) Madison"
+      },
+      "skills": ["./src/core-skills/bmad-party-mode"]
+    },
+    {
+      "name": "bmad-forge-idea",
+      "source": "./",
+      "description": "Pressure-test an idea with persona-driven interrogation until it hardens, proves out, or dies cheaply.",
+      "version": "6.10.0",
+      "author": {
+        "name": "Brian (BMad) Madison"
+      },
+      "skills": ["./src/core-skills/bmad-forge-idea"]
+    },
+    {
+      "name": "bmad-analysis",
+      "source": "./",
+      "description": "The BMad thinking pack — structured brainstorming, idea pressure-testing, and multi-perspective agent roundtables in one install.",
+      "version": "6.10.0",
+      "author": {
+        "name": "Brian (BMad) Madison"
+      },
+      "skills": ["./src/core-skills/bmad-brainstorming", "./src/core-skills/bmad-party-mode", "./src/core-skills/bmad-forge-idea"]
     },
     {
       "name": "bmad-method-lifecycle",
       "source": "./",
       "description": "Full-lifecycle AI development framework — agents and workflows for product analysis, planning, architecture, and implementation.",
-      "version": "6.8.0",
+      "version": "6.10.0",
       "author": {
         "name": "Brian (BMad) Madison"
       },
       "skills": [
+        "./src/core-skills/bmad-help",
+        "./src/core-skills/bmad-customize",
+        "./src/core-skills/bmad-advanced-elicitation",
+        "./src/core-skills/bmad-review",
+        "./src/core-skills/bmad-editorial-review",
         "./src/bmm-skills/1-analysis/bmad-product-brief",
         "./src/bmm-skills/1-analysis/bmad-prfaq",
         "./src/bmm-skills/1-analysis/bmad-agent-analyst",
@@ -53,13 +74,10 @@
         "./src/bmm-skills/2-plan-workflows/bmad-agent-pm",
         "./src/bmm-skills/2-plan-workflows/bmad-agent-ux-designer",
         "./src/bmm-skills/2-plan-workflows/bmad-prd",
-        "./src/bmm-skills/2-plan-workflows/bmad-create-prd",
-        "./src/bmm-skills/2-plan-workflows/bmad-edit-prd",
-        "./src/bmm-skills/2-plan-workflows/bmad-validate-prd",
+        "./src/bmm-skills/2-plan-workflows/bmad-spec",
         "./src/bmm-skills/2-plan-workflows/bmad-ux",
         "./src/bmm-skills/3-solutioning/bmad-agent-architect",
         "./src/bmm-skills/3-solutioning/bmad-architecture",
-        "./src/bmm-skills/3-solutioning/bmad-create-architecture",
         "./src/bmm-skills/3-solutioning/bmad-check-implementation-readiness",
         "./src/bmm-skills/3-solutioning/bmad-create-epics-and-stories",
         "./src/bmm-skills/3-solutioning/bmad-generate-project-context",

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method",
-  "version": "6.10.1-next.16",
+  "version": "6.10.1-next.18",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "keywords": [
     "agile",

package/removals.txt

@@ -68,3 +68,8 @@ bmad-investigate
 # bmad-auto-setup: renamed to bmad-loop-setup as part of the bmad-auto ->
 # bmad-loop module rename (BMad Automator's replacement).
 bmad-auto-setup
+
+# Removed skills (core streamline, post-v6.10.0)
+# bmad-index-docs, bmad-shard-doc: retired outright.
+bmad-index-docs
+bmad-shard-doc

package/src/bmm-skills/1-analysis/bmad-product-brief/customize.toml

@@ -53,7 +53,7 @@ run_folder_pattern = "brief-{project_name}-{date}"
 # findings before the user sees the draft. Encodes standards, not options.
 #
 # Examples:
-#   "skill:bmad-editorial-review-prose"
+#   "skill:bmad-editorial-review"
 #   "file:{project-root}/_bmad/style-guides/company-voice.md"
 #   "Convert all dates to ISO 8601 format."
 #
@@ -64,9 +64,9 @@ run_folder_pattern = "brief-{project_name}-{date}"
 #
 # Override the array in team/user TOML to add additional standards. Append-only:
 # base entries cannot be removed or replaced (resolver has no removal mechanism).
+# The default entry runs both editorial passes in order: structure, then prose.
 doc_standards = [
-  "skill:bmad-editorial-review-structure",
-  "skill:bmad-editorial-review-prose",
+  "skill:bmad-editorial-review",
 ]
 
 # External-source registry. Natural-language directives describing knowledge

package/src/bmm-skills/2-plan-workflows/bmad-create-prd/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-create-prd
-description: 'DEPRECATED — consolidated into bmad-prd create intent - this skill will be removed in v7 in favor of `bmad-prd`.'
+description: 'Deprecated — forwards to bmad-prd (create intent).'
 ---
 
 # DEPRECATED — forwards to bmad-prd (create intent)
@@ -15,12 +15,12 @@ This skill was consolidated into `bmad-prd`. It is retained as a thin compatibil
 
 3. Emit a deprecation notice to the user in `{communication_language}`:
 
-   > Notice: `bmad-create-prd` is deprecated and will be removed in a future release. It now forwards to `bmad-prd` with create intent. To silence this notice and access the full new customization surface (`prd_template`, `validation_checklist`, `doc_standards`, `external_sources`, `external_handoffs`, `output_dir`, `output_folder_name`), migrate `_bmad/custom/bmad-create-prd.toml` to `_bmad/custom/bmad-prd.toml` and invoke `bmad-prd` directly next time. Customization fields that were in this version still remain in the new version and will be respected if present in `_bmad/custom/bmad-prd.toml`, but the new version also supports additional fields that you can take advantage of by migrating.
+   > Notice: `bmad-create-prd` is deprecated and will be removed in a future release. It now forwards to `bmad-prd` with create intent. To silence this notice and access the full new customization surface (`prd_template`, `validation_checklist_template`, `validation_report_template`, `doc_standards`, `finalize_reviewers`, `external_sources`, `external_handoffs`, `prd_output_path`, `run_folder_pattern`), migrate `_bmad/custom/bmad-create-prd.toml` to `_bmad/custom/bmad-prd.toml` and invoke `bmad-prd` directly next time. Customization fields that were in this version still remain in the new version and will be respected if present in `_bmad/custom/bmad-prd.toml`, but the new version also supports additional fields that you can take advantage of by migrating.
 
 4. Invoke `bmad-prd` with the following context. Pass these as the activating context so `bmad-prd` honors them instead of resolving its own customization from scratch:
 
    - **Intent:** `create` — skip `bmad-prd`'s usual intent detection step.
-   - **Pre-resolved legacy customization** — use these in place of resolving from `bmad-prd`'s own `customize.toml` for the four legacy fields. For everything else (`prd_template`, `validation_checklist`, `validation_report_template`, `doc_standards`, `output_dir`, `output_folder_name`, `external_sources`, `external_handoffs`), use `bmad-prd`'s own defaults and overrides as normal:
+   - **Pre-resolved legacy customization** — use these in place of resolving from `bmad-prd`'s own `customize.toml` for the four legacy fields. For everything else (`prd_template`, `validation_checklist_template`, `validation_report_template`, `doc_standards`, `finalize_reviewers`, `prd_output_path`, `run_folder_pattern`, `external_sources`, `external_handoffs`), use `bmad-prd`'s own defaults and overrides as normal:
      - `activation_steps_prepend` = the resolved value from step 1
      - `activation_steps_append` = the resolved value from step 1
      - `persistent_facts` = the resolved value from step 1

package/src/bmm-skills/2-plan-workflows/bmad-edit-prd/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-edit-prd
-description: 'DEPRECATED — consolidated into bmad-prd update intent - this skill will be removed in v7 in favor of `bmad-prd`.'
+description: 'Deprecated — forwards to bmad-prd (update intent).'
 ---
 
 # DEPRECATED — forwards to bmad-prd (update intent)
@@ -15,12 +15,12 @@ This skill was consolidated into `bmad-prd`. It is retained as a thin compatibil
 
 3. Emit a deprecation notice to the user in `{communication_language}`:
 
-   > Notice: `bmad-edit-prd` is deprecated and will be removed in a future release. It now forwards to `bmad-prd` with update intent. To silence this notice and access the full new customization surface (`prd_template`, `validation_checklist`, `doc_standards`, `external_sources`, `external_handoffs`, `output_dir`, `output_folder_name`), migrate `_bmad/custom/bmad-edit-prd.toml` to `_bmad/custom/bmad-prd.toml` and invoke `bmad-prd` directly next time. Customization fields that were in this version still remain in the new version and will be respected if present in `_bmad/custom/bmad-prd.toml`, but the new version also supports additional fields that you can take advantage of by migrating.
+   > Notice: `bmad-edit-prd` is deprecated and will be removed in a future release. It now forwards to `bmad-prd` with update intent. To silence this notice and access the full new customization surface (`prd_template`, `validation_checklist_template`, `validation_report_template`, `doc_standards`, `finalize_reviewers`, `external_sources`, `external_handoffs`, `prd_output_path`, `run_folder_pattern`), migrate `_bmad/custom/bmad-edit-prd.toml` to `_bmad/custom/bmad-prd.toml` and invoke `bmad-prd` directly next time. Customization fields that were in this version still remain in the new version and will be respected if present in `_bmad/custom/bmad-prd.toml`, but the new version also supports additional fields that you can take advantage of by migrating.
 
 4. Invoke `bmad-prd` with the following context. Pass these as the activating context so `bmad-prd` honors them instead of resolving its own customization from scratch:
 
    - **Intent:** `update` — skip `bmad-prd`'s usual intent detection step.
-   - **Pre-resolved legacy customization** — use these in place of resolving from `bmad-prd`'s own `customize.toml` for the four legacy fields. For everything else (`prd_template`, `validation_checklist`, `validation_report_template`, `doc_standards`, `output_dir`, `output_folder_name`, `external_sources`, `external_handoffs`), use `bmad-prd`'s own defaults and overrides as normal:
+   - **Pre-resolved legacy customization** — use these in place of resolving from `bmad-prd`'s own `customize.toml` for the four legacy fields. For everything else (`prd_template`, `validation_checklist_template`, `validation_report_template`, `doc_standards`, `finalize_reviewers`, `prd_output_path`, `run_folder_pattern`, `external_sources`, `external_handoffs`), use `bmad-prd`'s own defaults and overrides as normal:
      - `activation_steps_prepend` = the resolved value from step 1
      - `activation_steps_append` = the resolved value from step 1
      - `persistent_facts` = the resolved value from step 1

package/src/bmm-skills/2-plan-workflows/bmad-prd/SKILL.md

@@ -15,6 +15,8 @@ You are a master facilitator and coach helping the user create, edit, or validat
 
 ## On Activation
 
+**Forwarded activation:** if a caller invoked you with a stated intent and pre-resolved customization fields (e.g. the `bmad-create-prd` / `bmad-edit-prd` / `bmad-validate-prd` shims), honor them verbatim — skip your own intent inference, use the supplied values for those named fields, and resolve only the remaining fields from your own `customize.toml`.
+
 1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`. On failure, read `{skill-root}/customize.toml` directly and use defaults.
 2. Run `{workflow.activation_steps_prepend}`. Treat `{workflow.persistent_facts}` as foundational context (entries prefixed `file:` are loaded). `{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, org tools preferred when their directive matches. Research itself fires during Discovery — see **Research subagents**.
 3. Load `{project-root}/_bmad/bmm/config.yaml` (+ `config.user.yaml` if present). Resolve `{user_name}`, `{communication_language}`, `{document_output_language}`, `{planning_artifacts}`, `{project_name}`, `{date}`. Missing keys → neutral defaults; never block.

package/src/bmm-skills/2-plan-workflows/bmad-prd/customize.toml

@@ -71,7 +71,7 @@ run_folder_pattern = "prd-{project_name}-{date}"
 # findings before the user sees the draft. Encodes standards, not options.
 #
 # Examples:
-#   "skill:bmad-editorial-review-prose"
+#   "skill:bmad-editorial-review"
 #   "file:{project-root}/_bmad/style-guides/company-voice.md"
 #   "Convert all dates to ISO 8601 format."
 #
@@ -82,9 +82,9 @@ run_folder_pattern = "prd-{project_name}-{date}"
 #
 # Override the array in team/user TOML to add additional standards. Append-only:
 # base entries cannot be removed or replaced (resolver has no removal mechanism).
+# The default entry runs both editorial passes in order: structure, then prose.
 doc_standards = [
-  "skill:bmad-editorial-review-structure",
-  "skill:bmad-editorial-review-prose",
+  "skill:bmad-editorial-review",
 ]
 
 # External-source registry. Natural-language directives describing knowledge

package/src/{core-skills → bmm-skills/2-plan-workflows}/bmad-spec/SKILL.md

@@ -20,7 +20,7 @@ Multiple skills may call to update the same spec over time.
 
 1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`. On failure, read `{skill-root}/customize.toml` directly.
 2. Run `{workflow.activation_steps_prepend}`. Treat `{workflow.persistent_facts}` as foundational context (`file:` entries are loaded).
-3. Load `{project-root}/_bmad/core/config.yaml` (and `config.user.yaml` if present), root level and `bmm` section. Resolve `{user_name}`, `{communication_language}`, `{document_output_language}`, `{planning_artifacts}`, `{project_name}`, `{date}`.
+3. Resolve config: `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}` (merges `_bmad/config.toml`, `_bmad/config.user.toml`, and the `_bmad/custom/` overrides). From the merged JSON resolve `{user_name}`, `{communication_language}`, `{document_output_language}`, `{project_name}`, `{output_folder}` (under `core`), and `{date}`.
 4. Detect mode. **Headless** when any of: no TTY, programmatic caller (another skill or non-interactive runner), or the first message pre-supplies all inputs and asks for an artifact path back. **Interactive** otherwise. In interactive mode, greet by `{user_name}` in `{communication_language}`, stay in that language, and mention that `bmad-party-mode` and `bmad-advanced-elicitation` are available for deeper exploration on any field.
 
 Run `{workflow.activation_steps_append}`.

package/src/{core-skills → bmm-skills/2-plan-workflows}/bmad-spec/assets/spec-template.md

@@ -4,7 +4,7 @@ companions: []     # files downstream MUST read alongside SPEC.md. Paths may poi
 sources: []        # files fully absorbed into the SPEC (audit only; downstream does NOT read these). Never the memlog.
 ---
 
-> **Canonical contract.** This SPEC and the files in `companions:` are the complete, preservation-validated contract for what to build, test, and validate. Source documents listed in frontmatter are for traceability only — consult them only if you need narrative rationale or prose color this contract intentionally omits.
+> **Canonical contract.** This SPEC and the files in `companions:` are the complete, preservation-validated contract for what to build, test, and validate. Source documents listed in frontmatter are for traceability — consult them only if you need narrative rationale or prose color this contract intentionally omits.
 
 # {Spec Title}
 

package/src/{core-skills → bmm-skills/2-plan-workflows}/bmad-spec/customize.toml

@@ -38,10 +38,9 @@ spec_template = "assets/spec-template.md"
 # Uppercase by convention to signal "the central source of truth."
 spec_filename = "SPEC.md"
 
-# Output path for spec folders. Lands directly under {output_folder}
-# so bmad-spec works in core-only installs and matches the
-# long-term BMad direction of grouping artifacts as siblings under
-# {output_folder}/<type>/ rather than nested inside planning vs
+# Output path for spec folders. Lands directly under {output_folder},
+# matching the long-term BMad direction of grouping artifacts as siblings
+# under {output_folder}/<type>/ rather than nested inside planning vs
 # implementation folders.
 spec_output_path = "{output_folder}/specs"
 

package/src/bmm-skills/2-plan-workflows/bmad-ux/customize.toml

@@ -78,9 +78,9 @@ creative_tools = [
 # Polish passes applied to DESIGN.md and EXPERIENCE.md at finalize.
 # Entries: `skill:NAME`, `file:PATH`, or plain text directive.
 # Suggested order: structural → content/voice → prose mechanics.
+# The default entry runs both editorial passes in order: structure, then prose.
 doc_standards = [
-  "skill:bmad-editorial-review-structure",
-  "skill:bmad-editorial-review-prose",
+  "skill:bmad-editorial-review",
 ]
 
 # Information retrieval registry. Consulted on demand when the conversation

package/src/bmm-skills/2-plan-workflows/bmad-validate-prd/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-validate-prd
-description: 'DEPRECATED — consolidated into bmad-prd validate intent - this skill will be removed in v7 in favor of `bmad-prd`.'
+description: 'Deprecated — forwards to bmad-prd (validate intent).'
 ---
 
 # DEPRECATED — forwards to bmad-prd (validate intent)
@@ -15,12 +15,12 @@ This skill was consolidated into `bmad-prd`. It is retained as a thin compatibil
 
 3. Emit a deprecation notice to the user in `{communication_language}`:
 
-   > Notice: `bmad-validate-prd` is deprecated and will be removed in a future release. It now forwards to `bmad-prd` with validate intent. To silence this notice and access the full new customization surface (`prd_template`, `validation_checklist`, `doc_standards`, `external_sources`, `external_handoffs`, `output_dir`, `output_folder_name`), migrate `_bmad/custom/bmad-validate-prd.toml` to `_bmad/custom/bmad-prd.toml` and invoke `bmad-prd` directly next time. Customization fields that were in this version still remain in the new version and will be respected if present in `_bmad/custom/bmad-prd.toml`, but the new version also supports additional fields that you can take advantage of by migrating.
+   > Notice: `bmad-validate-prd` is deprecated and will be removed in a future release. It now forwards to `bmad-prd` with validate intent. To silence this notice and access the full new customization surface (`prd_template`, `validation_checklist_template`, `validation_report_template`, `doc_standards`, `finalize_reviewers`, `external_sources`, `external_handoffs`, `prd_output_path`, `run_folder_pattern`), migrate `_bmad/custom/bmad-validate-prd.toml` to `_bmad/custom/bmad-prd.toml` and invoke `bmad-prd` directly next time. Customization fields that were in this version still remain in the new version and will be respected if present in `_bmad/custom/bmad-prd.toml`, but the new version also supports additional fields that you can take advantage of by migrating.
 
 4. Invoke `bmad-prd` with the following context. Pass these as the activating context so `bmad-prd` honors them instead of resolving its own customization from scratch:
 
    - **Intent:** `validate` — skip `bmad-prd`'s usual intent detection step.
-   - **Pre-resolved legacy customization** — use these in place of resolving from `bmad-prd`'s own `customize.toml` for the four legacy fields. For everything else (`prd_template`, `validation_checklist`, `validation_report_template`, `doc_standards`, `output_dir`, `output_folder_name`, `external_sources`, `external_handoffs`), use `bmad-prd`'s own defaults and overrides as normal:
+   - **Pre-resolved legacy customization** — use these in place of resolving from `bmad-prd`'s own `customize.toml` for the four legacy fields. For everything else (`prd_template`, `validation_checklist_template`, `validation_report_template`, `doc_standards`, `finalize_reviewers`, `prd_output_path`, `run_folder_pattern`, `external_sources`, `external_handoffs`), use `bmad-prd`'s own defaults and overrides as normal:
      - `activation_steps_prepend` = the resolved value from step 1
      - `activation_steps_append` = the resolved value from step 1
      - `persistent_facts` = the resolved value from step 1

package/src/bmm-skills/3-solutioning/bmad-architecture/SKILL.md

@@ -48,10 +48,10 @@ Writes go through the shared script (don't read the file back except on resume):
 
 ## On Activation
 
-**Forwarded activation:** if a caller (e.g. the `bmad-create-architecture` shim) invoked you with a stated intent and pre-resolved customization fields, honor them verbatim — skip your own intent inference, use the supplied values for those named fields, and resolve only the remaining fields from your own `customize.toml`.
+**Forwarded activation:** if a caller invoked you with a stated intent and pre-resolved customization fields, honor them verbatim — skip your own intent inference, use the supplied values for those named fields, and resolve only the remaining fields from your own `customize.toml`.
 
 1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow` (on failure read `{skill-root}/customize.toml`, use defaults). Run `{workflow.activation_steps_prepend}`, then `{workflow.activation_steps_append}`. Hold `{workflow.persistent_facts}` as standing context — the default loads `project-context.md`, load-bearing for brownfield — and consult `{workflow.external_sources}` on demand.
-2. Load `{project-root}/_bmad/bmm/config.yaml` (+ `config.user.yaml`) for `{user_name}`, `{communication_language}`, `{document_output_language}`, `{planning_artifacts}`, `{project_name}`, `{date}`; missing keys take neutral defaults, never block.
+2. Resolve config: `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}` (merges `_bmad/config.toml`, `_bmad/config.user.toml`, and the `_bmad/custom/` overrides). From the merged JSON resolve `{user_name}`, `{communication_language}`, `{document_output_language}`, `{project_name}` (under `core`), `{planning_artifacts}` (under `modules.bmm`), and `{date}`; missing keys take neutral defaults, never block.
 3. Headless (no interactive user) → follow `references/headless.md` for the whole run. Otherwise greet `{user_name}` in `{communication_language}`. Detect the intent from the conversation and input — **create** (the default), **update** an existing spine, or **validate** one (see those sections). If the real ask is requirements / UX / a capability contract / epic breakdown / an agent, invoke the `bmad-prd`, `bmad-ux`, `bmad-spec`, `bmad-create-epics-and-stories`, or `bmad-workflow-builder` (if the BMad Builder module is installed) skill instead.
 4. If a run folder for this target already exists under `{workflow.spine_output_path}`, offer to resume from its memlog rather than restart.
 5. Interactive create: offer the working mode in `{communication_language}` — **Coaching path** (default) or **Fast path** (see *How you work*) — before any drafting; default to Coaching unless the user asks for speed.

package/src/bmm-skills/3-solutioning/bmad-architecture/customize.toml

@@ -59,9 +59,9 @@ run_folder_pattern = "architecture-{project_name}-{date}"
 # short, structured outputs, which are terse and carry decisions in AD-n blocks and diagrams by
 # design. Each entry is a `skill:`, `file:`, or plain-text directive applied before the user sees
 # the polished draft. Suggested order: structural passes first, prose mechanics last. Append-only.
+# The default entry runs both editorial passes in order: structure, then prose.
 doc_standards = [
-  "skill:bmad-editorial-review-structure",
-  "skill:bmad-editorial-review-prose",
+  "skill:bmad-editorial-review",
 ]
 
 # External-source registry. Natural-language directives describing knowledge bases, MCP tools, or

package/src/bmm-skills/3-solutioning/bmad-create-architecture/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-create-architecture
-description: 'DEPRECATED — consolidated into bmad-architecture create intent - this skill will be removed in v7 in favor of `bmad-architecture`.'
+description: 'Deprecated — forwards to bmad-architecture (create intent).'
 ---
 
 # DEPRECATED — forwards to bmad-architecture (create intent)

package/src/bmm-skills/4-implementation/bmad-agent-dev/customize.toml

@@ -48,6 +48,9 @@ principles = [
   "No task complete without passing tests.",
   "Red, green, refactor — in that order.",
   "Tasks executed in the sequence written.",
+  "Never add epic or story references as inline code comments (e.g. # Epic: X, # Story: PROJ-42).",
+  "Code comments explain why, not what — no AI workflow metadata, planning refs, or story tracking in source code.",
+  "Generated code must be production-ready: clean, minimal, and free of AI-generated noise.",
 ]
 
 # Capabilities menu. Overrides merge by `code`: matching codes replace the item

package/src/bmm-skills/4-implementation/bmad-code-review/customize.toml

@@ -52,7 +52,7 @@ name = "Blind Hunter"
 instruction = """
 Launch a subagent with no prior conversation context, with this prompt:
 
-> Invoke the `bmad-review-adversarial-general` skill on this diff:
+> Invoke the `bmad-review` skill with only the `adversarial` lens on this diff:
 >
 > {diff_output}
 """
@@ -63,7 +63,7 @@ name = "Edge Case Hunter"
 instruction = """
 Launch a subagent with no prior conversation context, with this prompt:
 
-> Invoke the `bmad-review-edge-case-hunter` skill on this diff:
+> Invoke the `bmad-review` skill with only the `edge-case-hunter` lens on this diff:
 >
 > {diff_output}
 """
@@ -74,7 +74,7 @@ name = "Verification Gap Reviewer"
 instruction = """
 Launch a subagent with no prior conversation context, with this prompt:
 
-> Invoke the `bmad-review-verification-gap` skill on this diff:
+> Invoke the `bmad-review` skill with only the `verification-gap` lens on this diff:
 >
 > {diff_output}
 """

package/src/bmm-skills/4-implementation/bmad-dev-auto/customize.toml

@@ -63,7 +63,7 @@ name = "Blind Hunter"
 instruction = """
 Launch a subagent with no prior conversation context, with this prompt:
 
-> Invoke the `bmad-review-adversarial-general` skill on this diff:
+> Invoke the `bmad-review` skill with only the `adversarial` lens on this diff:
 >
 > {diff_output}
 """
@@ -74,7 +74,7 @@ name = "Edge Case Hunter"
 instruction = """
 Launch a subagent with no prior conversation context, with this prompt:
 
-> Invoke the `bmad-review-edge-case-hunter` skill on this diff:
+> Invoke the `bmad-review` skill with only the `edge-case-hunter` lens on this diff:
 >
 > {diff_output}
 """
@@ -85,7 +85,7 @@ name = "Verification Gap Reviewer"
 instruction = """
 Launch a subagent with no prior conversation context, with this prompt:
 
-> Invoke the `bmad-review-verification-gap` skill on this diff:
+> Invoke the `bmad-review` skill with only the `verification-gap` lens on this diff:
 >
 > {diff_output}
 """

package/src/bmm-skills/4-implementation/bmad-dev-story/customize.toml

@@ -32,6 +32,9 @@ activation_steps_append = []
 
 persistent_facts = [
   "file:{project-root}/**/project-context.md",
+  "Never add epic or story references as inline code comments (e.g. # Epic: X, # Story: PROJ-42).",
+  "Code comments explain why, not what — no AI workflow metadata, planning refs, or story tracking in source code.",
+  "Generated code must be production-ready: clean, minimal, and free of AI-generated noise.",
 ]
 
 # Scalar: executed when the workflow reaches its final step,

package/src/bmm-skills/4-implementation/bmad-quick-dev/customize.toml

@@ -44,7 +44,7 @@ name = "Blind Hunter"
 instruction = """
 Launch a subagent with no prior conversation context, with this prompt:
 
-> Invoke the `bmad-review-adversarial-general` skill on this diff:
+> Invoke the `bmad-review` skill with only the `adversarial` lens on this diff:
 >
 > {diff_output}
 """
@@ -55,7 +55,7 @@ name = "Edge Case Hunter"
 instruction = """
 Launch a subagent with no prior conversation context, with this prompt:
 
-> Invoke the `bmad-review-edge-case-hunter` skill on this diff:
+> Invoke the `bmad-review` skill with only the `edge-case-hunter` lens on this diff:
 >
 > {diff_output}
 """
@@ -66,7 +66,7 @@ name = "Verification Gap Reviewer"
 instruction = """
 Launch a subagent with no prior conversation context, with this prompt:
 
-> Invoke the `bmad-review-verification-gap` skill on this diff:
+> Invoke the `bmad-review` skill with only the `verification-gap` lens on this diff:
 >
 > {diff_output}
 """
@@ -79,5 +79,5 @@ name = "Blind Hunter"
 instruction = """
 Launch a subagent with no prior conversation context, with this prompt:
 
-> Invoke the `bmad-review-adversarial-general` skill on the changed files.
+> Invoke the `bmad-review` skill with only the `adversarial` lens on the changed files.
 """

package/src/bmm-skills/module-help.csv

@@ -3,13 +3,14 @@ BMad Method,_meta,,,,,,,,,false,https://docs.bmad-method.org/llms.txt,
 BMad Method,bmad-document-project,Document Project,DP,Analyze an existing project to produce useful documentation.,,,anytime,,,false,project-knowledge,*
 BMad Method,bmad-generate-project-context,Generate Project Context,GPC,Scan existing codebase to generate a lean LLM-optimized project-context.md. Essential for brownfield projects.,,,anytime,,,false,output_folder,project context
 BMad Method,bmad-quick-dev,Quick Dev,QQ,Unified intent-in code-out workflow: clarify plan implement review and present.,,,anytime,,,false,implementation_artifacts,spec and project implementation
+BMad Method,bmad-spec,Spec,SPC,"Use to distill any intent input (brief, PRD, transcript, brain dump, design folder, mixed multi-source) into a succinct, no-fluff SPEC.md contract + companions that downstream work derives from. Locks the WHAT before the HOW. Works for software, game design, research, editorial, policy, business, anything intent-bearing. Validation mode also available.",,[path],anytime,,,false,{output_folder}/specs/spec-{slug},SPEC.md + companion files
 BMad Method,bmad-correct-course,Correct Course,CC,Navigate significant changes. May recommend start over update PRD redo architecture sprint planning or correct epics and stories.,,,anytime,,,false,planning_artifacts,change proposal
 BMad Method,bmad-agent-tech-writer,Write Document,WD,"Describe in detail what you want, and the agent will follow documentation best practices. Multi-turn conversation with subprocess for research/review.",write,,anytime,,,false,project-knowledge,document
 BMad Method,bmad-agent-tech-writer,Update Standards,US,Update agent memory documentation-standards.md with your specific preferences if you discover missing document conventions.,update-standards,,anytime,,,false,_bmad/_memory/tech-writer-sidecar,standards
 BMad Method,bmad-agent-tech-writer,Mermaid Generate,MG,Create a Mermaid diagram based on user description. Will suggest diagram types if not specified.,mermaid,,anytime,,,false,planning_artifacts,mermaid diagram
 BMad Method,bmad-agent-tech-writer,Validate Document,VD,Review the specified document against documentation standards and best practices. Returns specific actionable improvement suggestions organized by priority.,validate,[path],anytime,,,false,planning_artifacts,validation report
 BMad Method,bmad-agent-tech-writer,Explain Concept,EC,Create clear technical explanations with examples and diagrams for complex concepts.,explain,[topic],anytime,,,false,project_knowledge,explanation
-BMad Method,bmad-brainstorming,Brainstorm Project,BP,Expert guided facilitation through a single or multiple techniques.,,,1-analysis,,,false,planning_artifacts,brainstorming session
+BMad Method,bmad-brainstorming,Brainstorm Project,BP,Expert guided facilitation through a single or multiple techniques.,,,1-analysis,,,false,{output_folder}/brainstorming,brainstorming session
 BMad Method,bmad-market-research,Market Research,MR,Market analysis competitive landscape customer needs and trends.,,,1-analysis,,,false,planning_artifacts|project-knowledge,research documents
 BMad Method,bmad-domain-research,Domain Research,DR,Industry domain deep dive subject matter expertise and terminology.,,,1-analysis,,,false,planning_artifacts|project_knowledge,research documents
 BMad Method,bmad-technical-research,Technical Research,TR,Technical feasibility architecture options and implementation approaches.,,,1-analysis,,,false,planning_artifacts|project_knowledge,research documents

package/src/bmm-skills/module.yaml

@@ -40,11 +40,8 @@ project_knowledge: # Artifacts from research, document-project output, other lon
   default: "docs"
   result: "{project-root}/{value}"
 
-# Directories to create during installation (declarative, no code execution)
-directories:
-  - "{planning_artifacts}"
-  - "{implementation_artifacts}"
-  - "{project_knowledge}"
+# No pre-created directories: planning_artifacts, implementation_artifacts, and
+# project_knowledge are created lazily by whichever skill first writes to them.
 
 # Agent roster — essence only. External skills (party-mode, retrospective,
 # advanced-elicitation, help catalog) read these descriptors to route, display,