npm - bmad-method - Versions diffs - 6.0.0-alpha.15 → 6.0.0-alpha.16 - Mend

bmad-method 6.0.0-alpha.15 → 6.0.0-alpha.16

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (392) hide show

package/src/modules/bmm/workflows/testarch/framework/instructions.md CHANGED Viewed

@@ -2,7 +2,7 @@
 # Test Framework Setup
-**Workflow ID**: `{bmad_folder}/bmm/testarch/framework`
+**Workflow ID**: `.bmad/bmm/testarch/framework`
 **Version**: 4.0 (BMad v6)
 ---
@@ -355,7 +355,7 @@ Read `{config_source}` and check `config.tea_use_playwright_utils`.
 **If `config.tea_use_playwright_utils: true` (Playwright Utils Integration):**
-Consult `{project-root}/{bmad_folder}/bmm/testarch/tea-index.csv` and load:
+Consult `{project-root}/.bmad/bmm/testarch/tea-index.csv` and load:
 - `overview.md` - Playwright utils installation and design principles
 - `fixtures-composition.md` - mergeTests composition with playwright-utils
@@ -375,7 +375,7 @@ Recommend adding burn-in and network-error-monitor to merged fixtures for enhanc
 **If `config.tea_use_playwright_utils: false` (Traditional Patterns):**
-Consult `{project-root}/{bmad_folder}/bmm/testarch/tea-index.csv` and load:
+Consult `{project-root}/.bmad/bmm/testarch/tea-index.csv` and load:
 - `fixture-architecture.md` - Pure function → fixture → `mergeTests` composition with auto-cleanup (406 lines, 5 examples)
 - `data-factories.md` - Faker-based factories with overrides, nested factories, API seeding, auto-cleanup (498 lines, 5 examples)

package/src/modules/bmm/workflows/testarch/framework/workflow.yaml CHANGED Viewed

@@ -4,7 +4,7 @@ description: "Initialize production-ready test framework architecture (Playwrigh
 author: "BMad"
 # Critical variables from config
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language"
 date: system-generated
 # Workflow components
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/testarch/framework"
+installed_path: "{project-root}/.bmad/bmm/workflows/testarch/framework"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"

package/src/modules/bmm/workflows/testarch/nfr-assess/instructions.md CHANGED Viewed

@@ -50,7 +50,7 @@ This workflow performs a comprehensive assessment of non-functional requirements
 **Actions:**
-1. Load relevant knowledge fragments from `{project-root}/{bmad_folder}/bmm/testarch/tea-index.csv`:
+1. Load relevant knowledge fragments from `{project-root}/.bmad/bmm/testarch/tea-index.csv`:
    - `nfr-criteria.md` - Non-functional requirements criteria and thresholds (security, performance, reliability, maintainability with code examples, 658 lines, 4 examples)
    - `ci-burn-in.md` - CI/CD burn-in patterns for reliability validation (10-iteration detection, sharding, selective execution, 678 lines, 4 examples)
    - `test-quality.md` - Test quality expectations for maintainability (deterministic, isolated, explicit assertions, length/time limits, 658 lines, 5 examples)

package/src/modules/bmm/workflows/testarch/nfr-assess/workflow.yaml CHANGED Viewed

@@ -4,7 +4,7 @@ description: "Assess non-functional requirements (performance, security, reliabi
 author: "BMad"
 # Critical variables from config
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language"
 date: system-generated
 # Workflow components
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/testarch/nfr-assess"
+installed_path: "{project-root}/.bmad/bmm/workflows/testarch/nfr-assess"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 template: "{installed_path}/nfr-report-template.md"

package/src/modules/bmm/workflows/testarch/test-design/instructions.md CHANGED Viewed

@@ -2,7 +2,7 @@
 # Test Design and Risk Assessment
-**Workflow ID**: `{bmad_folder}/bmm/testarch/test-design`
+**Workflow ID**: `.bmad/bmm/testarch/test-design`
 **Version**: 4.0 (BMad v6)
 ---
@@ -74,7 +74,7 @@ The workflow auto-detects which mode to use based on project phase.
 3. **Load Knowledge Base Fragments (System-Level)**
-   **Critical:** Consult `{project-root}/{bmad_folder}/bmm/testarch/tea-index.csv` to load:
+   **Critical:** Consult `{project-root}/.bmad/bmm/testarch/tea-index.csv` to load:
    - `nfr-criteria.md` - NFR validation approach (security, performance, reliability, maintainability)
    - `test-levels-framework.md` - Test levels strategy guidance
    - `risk-governance.md` - Testability risk identification
@@ -108,7 +108,7 @@ The workflow auto-detects which mode to use based on project phase.
 4. **Load Knowledge Base Fragments (Epic-Level)**
-   **Critical:** Consult `{project-root}/{bmad_folder}/bmm/testarch/tea-index.csv` to load:
+   **Critical:** Consult `{project-root}/.bmad/bmm/testarch/tea-index.csv` to load:
    - `risk-governance.md` - Risk classification framework (6 categories: TECH, SEC, PERF, DATA, BUS, OPS), automated scoring, gate decision engine, owner tracking (625 lines, 4 examples)
    - `probability-impact.md` - Risk scoring methodology (probability × impact matrix, automated classification, dynamic re-assessment, gate integration, 604 lines, 4 examples)
    - `test-levels-framework.md` - Test level selection guidance (E2E vs API vs Component vs Unit with decision matrix, characteristics, when to use each, 467 lines, 4 examples)

package/src/modules/bmm/workflows/testarch/test-design/test-design-template.md CHANGED Viewed

@@ -281,5 +281,5 @@
 ---
 **Generated by**: BMad TEA Agent - Test Architect Module
-**Workflow**: `{bmad_folder}/bmm/testarch/test-design`
+**Workflow**: `.bmad/bmm/testarch/test-design`
 **Version**: 4.0 (BMad v6)

package/src/modules/bmm/workflows/testarch/test-design/workflow.yaml CHANGED Viewed

@@ -4,7 +4,7 @@ description: "Dual-mode workflow: (1) System-level testability review in Solutio
 author: "BMad"
 # Critical variables from config
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language"
 date: system-generated
 # Workflow components
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/testarch/test-design"
+installed_path: "{project-root}/.bmad/bmm/workflows/testarch/test-design"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 template: "{installed_path}/test-design-template.md"

package/src/modules/bmm/workflows/testarch/test-review/instructions.md CHANGED Viewed

@@ -52,7 +52,7 @@ This workflow performs comprehensive test quality reviews using TEA's knowledge
 1. Check playwright-utils flag:
    - Read `{config_source}` and check `config.tea_use_playwright_utils`
-2. Load relevant knowledge fragments from `{project-root}/{bmad_folder}/bmm/testarch/tea-index.csv`:
+2. Load relevant knowledge fragments from `{project-root}/.bmad/bmm/testarch/tea-index.csv`:
    **Core Patterns (Always load):**
    - `test-quality.md` - Definition of Done (deterministic tests, isolated with cleanup, explicit assertions, <300 lines, <1.5 min, 658 lines, 5 examples)

package/src/modules/bmm/workflows/testarch/test-review/workflow.yaml CHANGED Viewed

@@ -4,7 +4,7 @@ description: "Review test quality using comprehensive knowledge base and best pr
 author: "BMad"
 # Critical variables from config
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language"
 date: system-generated
 # Workflow components
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/testarch/test-review"
+installed_path: "{project-root}/.bmad/bmm/workflows/testarch/test-review"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 template: "{installed_path}/test-review-template.md"

package/src/modules/bmm/workflows/testarch/trace/instructions.md CHANGED Viewed

@@ -64,7 +64,7 @@ This phase focuses on mapping requirements to tests, analyzing coverage, and ide
 **Actions:**
-1. Load relevant knowledge fragments from `{project-root}/{bmad_folder}/bmm/testarch/tea-index.csv`:
+1. Load relevant knowledge fragments from `{project-root}/.bmad/bmm/testarch/tea-index.csv`:
    - `test-priorities-matrix.md` - P0/P1/P2/P3 risk framework with automated priority calculation, risk-based mapping, tagging strategy (389 lines, 2 examples)
    - `risk-governance.md` - Risk-based testing approach: 6 categories (TECH, SEC, PERF, DATA, BUS, OPS), automated scoring, gate decision engine, coverage traceability (625 lines, 4 examples)
    - `probability-impact.md` - Risk scoring methodology: probability × impact matrix, automated classification, dynamic re-assessment, gate integration (604 lines, 4 examples)
@@ -476,10 +476,10 @@ This phase uses traceability results to make a quality gate decision (PASS/CONCE
 ## References
-- Traceability Matrix: `{bmad_folder}/output/traceability-matrix.md`
-- Test Design: `{bmad_folder}/output/test-design-epic-2.md`
+- Traceability Matrix: `.bmad/output/traceability-matrix.md`
+- Test Design: `.bmad/output/test-design-epic-2.md`
 - Test Results: `ci-artifacts/test-report-2025-01-15.xml`
-- NFR Assessment: `{bmad_folder}/output/nfr-assessment-release-1.2.md`
+- NFR Assessment: `.bmad/output/nfr-assessment-release-1.2.md`
 ```
 3. **Include evidence links** (if `require_evidence: true`):
@@ -515,7 +515,7 @@ This phase uses traceability results to make a quality gate decision (PASS/CONCE
      - **Decision**: CONCERNS
      - **Reason**: P1 coverage 88% (below 90%)
-     - **Document**: [gate-decision-story-1.3.md]({bmad_folder}/output/gate-decision-story-1.3.md)
+     - **Document**: [gate-decision-story-1.3.md](.bmad/output/gate-decision-story-1.3.md)
      - **Action**: Deploy with follow-up story for AC-5
      ```
@@ -536,7 +536,7 @@ This phase uses traceability results to make a quality gate decision (PASS/CONCE
    - Create follow-up story for AC-5 E2E test
    - Deploy to staging for validation
-   Full Report: {bmad_folder}/output/gate-decision-story-1.3.md
+   Full Report: .bmad/output/gate-decision-story-1.3.md
    ```
 3. **Request sign-off** (if `require_sign_off: true`):

package/src/modules/bmm/workflows/testarch/trace/workflow.yaml CHANGED Viewed

@@ -4,7 +4,7 @@ description: "Generate requirements-to-tests traceability matrix, analyze covera
 author: "BMad"
 # Critical variables from config
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language"
 date: system-generated
 # Workflow components
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/testarch/trace"
+installed_path: "{project-root}/.bmad/bmm/workflows/testarch/trace"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 template: "{installed_path}/trace-template.md"

package/src/modules/bmm/workflows/workflow-status/init/instructions.md CHANGED Viewed

@@ -1,6 +1,6 @@
 # Workflow Init - Project Setup Instructions
-<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
+<critical>The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: workflow-init/workflow.yaml</critical>
 <critical>Communicate in {communication_language} with {user_name}</critical>
 <critical>This workflow handles BOTH new projects AND legacy projects following the BMad Method</critical>

package/src/modules/bmm/workflows/workflow-status/init/workflow.yaml CHANGED Viewed

@@ -4,7 +4,7 @@ description: "Initialize a new BMM project by determining level, type, and creat
 author: "BMad"
 # Critical variables from config
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 sprint_artifacts: "{config_source}:sprint_artifacts"
 user_name: "{config_source}:user_name"
@@ -15,12 +15,12 @@ user_skill_level: "{config_source}:user_skill_level"
 date: system-generated
 # Workflow components
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/init"
+installed_path: "{project-root}/.bmad/bmm/workflows/workflow-status/init"
 instructions: "{installed_path}/instructions.md"
-template: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow-status-template.yaml"
+template: "{project-root}/.bmad/bmm/workflows/workflow-status/workflow-status-template.yaml"
 # Path data files
-path_files: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/paths/"
+path_files: "{project-root}/.bmad/bmm/workflows/workflow-status/paths/"
 # Output configuration
 default_output_file: "{output_folder}/bmm-workflow-status.yaml"

package/src/modules/bmm/workflows/workflow-status/instructions.md CHANGED Viewed

@@ -1,7 +1,7 @@
 # Workflow Status Check - Multi-Mode Service
-<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow.yaml</critical>
+<critical>The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {project-root}/.bmad/bmm/workflows/workflow-status/workflow.yaml</critical>
 <critical>This workflow operates in multiple modes: interactive (default), validate, data, init-check, update</critical>
 <critical>Other workflows can call this as a service to avoid duplicating status logic</critical>
 <critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical>
@@ -42,7 +42,7 @@
   <check if="response == y OR response == yes">
     <action>Launching workflow-init to set up your project tracking...</action>
-    <invoke-workflow path="{project-root}/{bmad_folder}/bmm/workflows/workflow-status/init/workflow.yaml"></invoke-workflow>
+    <invoke-workflow path="{project-root}/.bmad/bmm/workflows/workflow-status/init/workflow.yaml"></invoke-workflow>
     <action>Exit workflow and let workflow-init take over</action>
   </check>

package/src/modules/bmm/workflows/workflow-status/project-levels.yaml CHANGED Viewed

@@ -1,5 +1,5 @@
 # BMM Project Scale Levels - Source of Truth
-# Reference: /{bmad_folder}/bmm/README.md lines 77-85
+# Reference: /.bmad/bmm/README.md lines 77-85
 levels:
   0:

package/src/modules/bmm/workflows/workflow-status/workflow.yaml CHANGED Viewed

@@ -4,7 +4,7 @@ description: 'Lightweight status checker - answers "what should I do now?" for a
 author: "BMad"
 # Critical variables from config
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+config_source: "{project-root}/.bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -13,7 +13,7 @@ user_skill_level: "{config_source}:user_skill_level"
 date: system-generated
 # Workflow components
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status"
+installed_path: "{project-root}/.bmad/bmm/workflows/workflow-status"
 instructions: "{installed_path}/instructions.md"
 # Template for status file creation (used by workflow-init)

package/src/modules/cis/README.md CHANGED Viewed

@@ -103,7 +103,7 @@ agent cis/brainstorming-coach
 ## Configuration
-Edit `/{bmad_folder}/cis/config.yaml`:
+Edit `/.bmad/cis/config.yaml`:
 ```yaml
 output_folder: ./creative-outputs

package/src/modules/cis/agents/README.md CHANGED Viewed

@@ -96,7 +96,7 @@ Every CIS agent includes:
 ## Configuration
-All agents load configuration from `/{bmad_folder}/cis/config.yaml`:
+All agents load configuration from `/.bmad/cis/config.yaml`:
 - `project_name` - Project identification
 - `output_folder` - Where workflow results are saved

package/src/modules/cis/agents/brainstorming-coach.agent.yaml CHANGED Viewed

@@ -2,7 +2,7 @@
 agent:
   metadata:
-    id: "{bmad_folder}/cis/agents/brainstorming-coach.md"
+    id: ".bmad/cis/agents/brainstorming-coach.md"
     name: Carson
     title: Elite Brainstorming Specialist
     icon: 🧠
@@ -16,14 +16,14 @@ agent:
   menu:
     - trigger: brainstorm
-      workflow: "{project-root}/{bmad_folder}/core/workflows/brainstorming/workflow.yaml"
+      workflow: "{project-root}/.bmad/core/workflows/brainstorming/workflow.yaml"
       description: Guide me through Brainstorming any topic
     - trigger: party-mode
-      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
+      exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md"
       description: Consult with other expert agents from the party
     - trigger: advanced-elicitation
-      exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml"
+      exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml"
       description: Advanced elicitation techniques to challenge the LLM to get better results
       web-only: true

package/src/modules/cis/agents/creative-problem-solver.agent.yaml CHANGED Viewed

@@ -2,7 +2,7 @@
 agent:
   metadata:
-    id: "{bmad_folder}/cis/agents/creative-problem-solver.md"
+    id: ".bmad/cis/agents/creative-problem-solver.md"
     name: Dr. Quinn
     title: Master Problem Solver
     icon: 🔬
@@ -16,14 +16,14 @@ agent:
   menu:
     - trigger: solve
-      workflow: "{project-root}/{bmad_folder}/cis/workflows/problem-solving/workflow.yaml"
+      workflow: "{project-root}/.bmad/cis/workflows/problem-solving/workflow.yaml"
       description: Apply systematic problem-solving methodologies
     - trigger: party-mode
-      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
+      exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md"
       description: Consult with other expert agents from the party
     - trigger: advanced-elicitation
-      exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml"
+      exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml"
       description: Advanced elicitation techniques to challenge the LLM to get better results
       web-only: true

package/src/modules/cis/agents/design-thinking-coach.agent.yaml CHANGED Viewed

@@ -2,7 +2,7 @@
 agent:
   metadata:
-    id: "{bmad_folder}/cis/agents/design-thinking-coach.md"
+    id: ".bmad/cis/agents/design-thinking-coach.md"
     name: Maya
     title: Design Thinking Maestro
     icon: 🎨
@@ -16,14 +16,14 @@ agent:
   menu:
     - trigger: design
-      workflow: "{project-root}/{bmad_folder}/cis/workflows/design-thinking/workflow.yaml"
+      workflow: "{project-root}/.bmad/cis/workflows/design-thinking/workflow.yaml"
       description: Guide human-centered design process
     - trigger: party-mode
-      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
+      exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md"
       description: Consult with other expert agents from the party
     - trigger: advanced-elicitation
-      exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml"
+      exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml"
       description: Advanced elicitation techniques to challenge the LLM to get better results
       web-only: true

package/src/modules/cis/agents/innovation-strategist.agent.yaml CHANGED Viewed

@@ -2,7 +2,7 @@
 agent:
   metadata:
-    id: "{bmad_folder}/cis/agents/innovation-strategist.md"
+    id: ".bmad/cis/agents/innovation-strategist.md"
     name: Victor
     title: Disruptive Innovation Oracle
     icon: ⚡
@@ -16,14 +16,14 @@ agent:
   menu:
     - trigger: innovate
-      workflow: "{project-root}/{bmad_folder}/cis/workflows/innovation-strategy/workflow.yaml"
+      workflow: "{project-root}/.bmad/cis/workflows/innovation-strategy/workflow.yaml"
       description: Identify disruption opportunities and business model innovation
     - trigger: party-mode
-      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
+      exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md"
       description: Consult with other expert agents from the party
     - trigger: advanced-elicitation
-      exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml"
+      exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml"
       description: Advanced elicitation techniques to challenge the LLM to get better results
       web-only: true

package/src/modules/cis/agents/presentation-master.agent.yaml CHANGED Viewed

@@ -2,7 +2,7 @@
 agent:
   metadata:
-    id: "{bmad_folder}/cis/agents/presentation-master.md"
+    id: ".bmad/cis/agents/presentation-master.md"
     name: Caravaggio
     title: Visual Communication + Presentation Expert
     icon: 🎨
@@ -52,10 +52,10 @@ agent:
       description: Generate single expressive image that explains ideas creatively and memorably
     - trigger: party-mode
-      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
+      exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md"
       description: Consult with other expert agents from the party
     - trigger: advanced-elicitation
-      exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml"
+      exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml"
       description: Advanced elicitation techniques to challenge the LLM to get better results
       web-only: true

package/src/modules/cis/agents/storyteller.agent.yaml CHANGED Viewed

@@ -2,7 +2,7 @@
 agent:
   metadata:
-    id: "{bmad_folder}/cis/agents/storyteller.md"
+    id: ".bmad/cis/agents/storyteller.md"
     name: Sophia
     title: Master Storyteller
     icon: 📖
@@ -16,14 +16,14 @@ agent:
   menu:
     - trigger: story
-      exec: "{project-root}/{bmad_folder}/cis/workflows/storytelling/workflow.yaml"
+      exec: "{project-root}/.bmad/cis/workflows/storytelling/workflow.yaml"
       description: Craft compelling narrative using proven frameworks
     - trigger: party-mode
-      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
+      exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md"
       description: Consult with other expert agents from the party
     - trigger: advanced-elicitation
-      exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml"
+      exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml"
       description: Advanced elicitation techniques to challenge the LLM to get better results
       web-only: true

package/src/modules/cis/module.yaml CHANGED Viewed

@@ -10,7 +10,6 @@ subheader: "No Configuration needed - uses Core Config only."
 ## user_name
 ## communication_language
 ## output_folder
-## bmad_folder
 ## install_user_docs
 ## kb_install

package/src/modules/cis/workflows/README.md CHANGED Viewed

@@ -98,7 +98,7 @@ agent cis/brainstorming-coach
 ## Configuration
-Edit `/{bmad_folder}/cis/config.yaml`:
+Edit `/.bmad/cis/config.yaml`:
 | Setting                | Purpose                 | Default            |
 | ---------------------- | ----------------------- | ------------------ |

package/src/modules/cis/workflows/design-thinking/instructions.md CHANGED Viewed

@@ -1,7 +1,7 @@
 # Design Thinking Workflow Instructions
-<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {project_root}/{bmad_folder}/cis/workflows/design-thinking/workflow.yaml</critical>
+<critical>The workflow execution engine is governed by: {project_root}/.bmad/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {project_root}/.bmad/cis/workflows/design-thinking/workflow.yaml</critical>
 <critical>Load and understand design methods from: {design_methods}</critical>
 <critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical>
 <critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical>

package/src/modules/cis/workflows/design-thinking/workflow.yaml CHANGED Viewed

@@ -4,7 +4,7 @@ description: "Guide human-centered design processes using empathy-driven methodo
 author: "BMad"
 # Critical variables load from config_source
-config_source: "{project-root}/{bmad_folder}/cis/config.yaml"
+config_source: "{project-root}/.bmad/cis/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -14,7 +14,7 @@ date: system-generated
 # Example: data="{path}/product-context.md" provides project context
 # Module path and component files
-installed_path: "{project-root}/{bmad_folder}/cis/workflows/design-thinking"
+installed_path: "{project-root}/.bmad/cis/workflows/design-thinking"
 template: "{installed_path}/template.md"
 instructions: "{installed_path}/instructions.md"
@@ -30,9 +30,9 @@ web_bundle:
   name: "design-thinking"
   description: "Guide human-centered design processes using empathy-driven methodologies. This workflow walks through the design thinking phases - Empathize, Define, Ideate, Prototype, and Test - to create solutions deeply rooted in user needs."
   author: "BMad"
-  instructions: "{bmad_folder}/cis/workflows/design-thinking/instructions.md"
-  template: "{bmad_folder}/cis/workflows/design-thinking/template.md"
+  instructions: ".bmad/cis/workflows/design-thinking/instructions.md"
+  template: ".bmad/cis/workflows/design-thinking/template.md"
   web_bundle_files:
-    - "{bmad_folder}/cis/workflows/design-thinking/instructions.md"
-    - "{bmad_folder}/cis/workflows/design-thinking/template.md"
-    - "{bmad_folder}/cis/workflows/design-thinking/design-methods.csv"
+    - ".bmad/cis/workflows/design-thinking/instructions.md"
+    - ".bmad/cis/workflows/design-thinking/template.md"
+    - ".bmad/cis/workflows/design-thinking/design-methods.csv"

package/src/modules/cis/workflows/innovation-strategy/instructions.md CHANGED Viewed

@@ -1,7 +1,7 @@
 # Innovation Strategy Workflow Instructions
-<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {project_root}/{bmad_folder}/cis/workflows/innovation-strategy/workflow.yaml</critical>
+<critical>The workflow execution engine is governed by: {project_root}/.bmad/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {project_root}/.bmad/cis/workflows/innovation-strategy/workflow.yaml</critical>
 <critical>Load and understand innovation frameworks from: {innovation_frameworks}</critical>
 <critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical>
 <critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical>

package/src/modules/cis/workflows/innovation-strategy/workflow.yaml CHANGED Viewed

@@ -4,7 +4,7 @@ description: "Identify disruption opportunities and architect business model inn
 author: "BMad"
 # Critical variables load from config_source
-config_source: "{project-root}/{bmad_folder}/cis/config.yaml"
+config_source: "{project-root}/.bmad/cis/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -14,7 +14,7 @@ date: system-generated
 # Example: data="{path}/industry-analysis.md" provides market context
 # Module path and component files
-installed_path: "{project-root}/{bmad_folder}/cis/workflows/innovation-strategy"
+installed_path: "{project-root}/.bmad/cis/workflows/innovation-strategy"
 template: "{installed_path}/template.md"
 instructions: "{installed_path}/instructions.md"
@@ -30,9 +30,9 @@ web_bundle:
   name: "innovation-strategy"
   description: "Identify disruption opportunities and architect business model innovation. This workflow guides strategic analysis of markets, competitive dynamics, and business model innovation to uncover sustainable competitive advantages and breakthrough opportunities."
   author: "BMad"
-  instructions: "{bmad_folder}/cis/workflows/innovation-strategy/instructions.md"
-  template: "{bmad_folder}/cis/workflows/innovation-strategy/template.md"
+  instructions: ".bmad/cis/workflows/innovation-strategy/instructions.md"
+  template: ".bmad/cis/workflows/innovation-strategy/template.md"
   web_bundle_files:
-    - "{bmad_folder}/cis/workflows/innovation-strategy/instructions.md"
-    - "{bmad_folder}/cis/workflows/innovation-strategy/template.md"
-    - "{bmad_folder}/cis/workflows/innovation-strategy/innovation-frameworks.csv"
+    - ".bmad/cis/workflows/innovation-strategy/instructions.md"
+    - ".bmad/cis/workflows/innovation-strategy/template.md"
+    - ".bmad/cis/workflows/innovation-strategy/innovation-frameworks.csv"

package/src/modules/cis/workflows/problem-solving/instructions.md CHANGED Viewed

@@ -1,7 +1,7 @@
 # Problem Solving Workflow Instructions
-<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {project_root}/{bmad_folder}/cis/workflows/problem-solving/workflow.yaml</critical>
+<critical>The workflow execution engine is governed by: {project_root}/.bmad/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {project_root}/.bmad/cis/workflows/problem-solving/workflow.yaml</critical>
 <critical>Load and understand solving methods from: {solving_methods}</critical>
 <critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical>
 <critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical>