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

package/package.json

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

package/src/bmm-skills/1-analysis/{bmad-product-brief-preview → bmad-product-brief}/SKILL.md

@@ -1,7 +1,6 @@
 ---
-name: bmad-product-brief-preview
-description: Create or update product briefs through guided or autonomous discovery. Use when the user requests to 'create a product brief', 'help me create a project brief', or 'update my product brief'.
-argument-hint: "[optional --create, --edit, --optimize, --distillate, --inputs, --headless] [brief idea]"
+name: bmad-product-brief
+description: Create or update product briefs through guided or autonomous discovery. Use when the user requests to create or update a Product Brief.
 ---
 
 # Create Product Brief

package/src/bmm-skills/1-analysis/research/bmad-domain-research/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-domain-research
-description: 'Conduct domain and industry research. Use when the user says "lets create a research report on [domain or industry]"'
+description: 'Conduct domain and industry research. Use when the user says wants to do domain research for a topic or industry'
 ---
 
 Follow the instructions in ./workflow.md.

package/src/bmm-skills/1-analysis/research/bmad-market-research/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-market-research
-description: 'Conduct market research on competition and customers. Use when the user says "create a market research report about [business idea]".'
+description: 'Conduct market research on competition and customers. Use when the user says they need market research'
 ---
 
 Follow the instructions in ./workflow.md.

package/src/bmm-skills/1-analysis/research/bmad-technical-research/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-technical-research
-description: 'Conduct technical research on technologies and architecture. Use when the user says "create a technical research report on [topic]".'
+description: 'Conduct technical research on technologies and architecture. Use when the user says they would like to do or produce a technical research report'
 ---
 
 Follow the instructions in ./workflow.md.

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

@@ -12,7 +12,7 @@ bmm,1-analysis,Brainstorm Project,BP,10,skill:bmad-brainstorming,bmad-brainstorm
 bmm,1-analysis,Market Research,MR,20,skill:bmad-market-research,bmad-bmm-market-research,false,analyst,Create Mode,"Market analysis competitive landscape customer needs and trends","planning_artifacts|project-knowledge","research documents",
 bmm,1-analysis,Domain Research,DR,21,skill:bmad-domain-research,bmad-bmm-domain-research,false,analyst,Create Mode,"Industry domain deep dive subject matter expertise and terminology","planning_artifacts|project_knowledge","research documents",
 bmm,1-analysis,Technical Research,TR,22,skill:bmad-technical-research,bmad-bmm-technical-research,false,analyst,Create Mode,"Technical feasibility architecture options and implementation approaches","planning_artifacts|project_knowledge","research documents",
-bmm,1-analysis,Create Brief,CB,30,skill:bmad-create-product-brief,bmad-bmm-create-product-brief,false,analyst,Create Mode,"A guided experience to nail down your product idea",planning_artifacts,"product brief",
+bmm,1-analysis,Create Brief,CB,30,skill:bmad-product-brief,bmad-bmm-product-brief,false,analyst,Create Mode,"A guided experience to nail down your product idea",planning_artifacts,"product brief",
 bmm,2-planning,Create PRD,CP,10,skill:bmad-create-prd,bmad-bmm-create-prd,true,pm,Create Mode,"Expert led facilitation to produce your Product Requirements Document",planning_artifacts,prd,
 bmm,2-planning,Validate PRD,VP,20,skill:bmad-validate-prd,bmad-bmm-validate-prd,false,pm,Validate Mode,"Validate PRD is comprehensive lean well organized and cohesive",planning_artifacts,"prd validation report",
 bmm,2-planning,Edit PRD,EP,25,skill:bmad-edit-prd,bmad-bmm-edit-prd,false,pm,Edit Mode,"Improve and enhance an existing PRD",planning_artifacts,"updated prd",

package/tools/cli/installers/lib/core/manifest-generator.js

@@ -50,6 +50,29 @@ class ManifestGenerator {
     return getInstallToBmadShared(manifest, filename);
   }
 
+  /**
+   * Native SKILL.md entrypoints can be packaged as either skills or agents.
+   * Both need verbatim installation for skill-format IDEs.
+   * @param {string|null} artifactType - Manifest type resolved for SKILL.md
+   * @returns {boolean} True when the directory should be installed verbatim
+   */
+  isNativeSkillDirType(artifactType) {
+    return artifactType === 'skill' || artifactType === 'agent';
+  }
+
+  /**
+   * Check whether a loaded bmad-skill-manifest.yaml declares a native
+   * SKILL.md entrypoint, either as a single-entry manifest or a multi-entry map.
+   * @param {Object|null} manifest - Loaded manifest
+   * @returns {boolean} True when the manifest contains a native skill/agent entrypoint
+   */
+  hasNativeSkillManifest(manifest) {
+    if (!manifest) return false;
+    if (manifest.__single) return this.isNativeSkillDirType(manifest.__single.type);
+
+    return Object.values(manifest).some((entry) => this.isNativeSkillDirType(entry?.type));
+  }
+
   /**
    * Clean text for CSV output by normalizing whitespace.
    * Note: Quote escaping is handled by escapeCsv() at write time.
@@ -146,9 +169,10 @@ class ManifestGenerator {
   }
 
   /**
-   * Recursively walk a module directory tree, collecting skill directories.
-   * A skill directory is one that contains both a bmad-skill-manifest.yaml with
-   * type: skill AND a SKILL.md file with name/description frontmatter.
+   * Recursively walk a module directory tree, collecting native SKILL.md entrypoints.
+   * A native entrypoint directory is one that contains both a
+   * bmad-skill-manifest.yaml with type: skill or type: agent AND a SKILL.md file
+   * with name/description frontmatter.
    * Populates this.skills[] and this.skillClaimedDirs (Set of absolute paths).
    */
   async collectSkills() {
@@ -172,11 +196,11 @@ class ManifestGenerator {
         // Check this directory for skill manifest
         const manifest = await this.loadSkillManifest(dir);
 
-        // Determine if this directory is a skill (type: skill in manifest)
+        // Determine if this directory is a native SKILL.md entrypoint
         const skillFile = 'SKILL.md';
         const artifactType = this.getArtifactType(manifest, skillFile);
 
-        if (artifactType === 'skill' || artifactType === 'agent') {
+        if (this.isNativeSkillDirType(artifactType)) {
           const skillMdPath = path.join(dir, 'SKILL.md');
           const dirName = path.basename(dir);
 
@@ -190,11 +214,12 @@ class ManifestGenerator {
               ? `${this.bmadFolderName}/${moduleName}/${relativePath}/${skillFile}`
               : `${this.bmadFolderName}/${moduleName}/${skillFile}`;
 
-            // Skills derive canonicalId from directory name — never from manifest
-            // (agent-type skills legitimately use canonicalId for agent-manifest mapping, so skip warning)
+            // Native SKILL.md entrypoints derive canonicalId from directory name.
+            // Agent entrypoints may keep canonicalId metadata for compatibility, so
+            // only warn for non-agent SKILL.md directories.
             if (manifest && manifest.__single && manifest.__single.canonicalId && artifactType !== 'agent') {
               console.warn(
-                `Warning: Skill manifest at ${dir}/bmad-skill-manifest.yaml contains canonicalId — this field is ignored for skills (directory name is the canonical ID)`,
+                `Warning: Native entrypoint manifest at ${dir}/bmad-skill-manifest.yaml contains canonicalId — this field is ignored for SKILL.md directories (directory name is the canonical ID)`,
               );
             }
             const canonicalId = dirName;
@@ -224,21 +249,21 @@ class ManifestGenerator {
           }
         }
 
-        // Warn if manifest says type:skill but directory was not claimed
+        // Warn if manifest says this is a native entrypoint but the directory was not claimed
         if (manifest && !this.skillClaimedDirs.has(dir)) {
-          let hasSkillType = false;
+          let hasNativeSkillType = false;
           if (manifest.__single) {
-            hasSkillType = manifest.__single.type === 'skill' || manifest.__single.type === 'agent';
+            hasNativeSkillType = this.isNativeSkillDirType(manifest.__single.type);
           } else {
             for (const key of Object.keys(manifest)) {
-              if (manifest[key]?.type === 'skill' || manifest[key]?.type === 'agent') {
-                hasSkillType = true;
+              if (this.isNativeSkillDirType(manifest[key]?.type)) {
+                hasNativeSkillType = true;
                 break;
               }
             }
           }
-          if (hasSkillType && debug) {
-            console.log(`[DEBUG] collectSkills: dir has type:skill manifest but failed validation: ${dir}`);
+          if (hasNativeSkillType && debug) {
+            console.log(`[DEBUG] collectSkills: dir has native SKILL.md manifest but failed validation: ${dir}`);
           }
         }
 
@@ -1359,7 +1384,8 @@ class ManifestGenerator {
         const hasTasks = await fs.pathExists(path.join(modulePath, 'tasks'));
         const hasTools = await fs.pathExists(path.join(modulePath, 'tools'));
 
-        // Check for skill-only modules: recursive scan for bmad-skill-manifest.yaml with type: skill
+        // Check for native-entrypoint-only modules: recursive scan for
+        // bmad-skill-manifest.yaml with type: skill or type: agent
         let hasSkills = false;
         if (!hasAgents && !hasWorkflows && !hasTasks && !hasTools) {
           hasSkills = await this._hasSkillManifestRecursive(modulePath);
@@ -1378,7 +1404,8 @@ class ManifestGenerator {
   }
 
   /**
-   * Recursively check if a directory tree contains a bmad-skill-manifest.yaml with type: skill.
+   * Recursively check if a directory tree contains a bmad-skill-manifest.yaml that
+   * declares a native SKILL.md entrypoint (type: skill or type: agent).
    * Skips directories starting with . or _.
    * @param {string} dir - Directory to search
    * @returns {boolean} True if a skill manifest is found
@@ -1393,10 +1420,7 @@ class ManifestGenerator {
 
     // Check for manifest in this directory
     const manifest = await this.loadSkillManifest(dir);
-    if (manifest) {
-      const type = this.getArtifactType(manifest, 'workflow.md');
-      if (type === 'skill') return true;
-    }
+    if (this.hasNativeSkillManifest(manifest)) return true;
 
     // Recurse into subdirectories
     for (const entry of entries) {

package/tools/cli/installers/lib/ide/_config-driven.js

@@ -630,7 +630,7 @@ LOAD and execute from: {project-root}/{{bmadFolderName}}/{{path}}
   }
 
   /**
-   * Install verbatim skill directories (type: skill entries from skill-manifest.csv).
+   * Install verbatim native SKILL.md directories from skill-manifest.csv.
    * Copies the entire source directory as-is into the IDE skill directory.
    * The source SKILL.md is used directly — no frontmatter transformation or file generation.
    * @param {string} projectDir - Project directory

package/src/bmm-skills/1-analysis/bmad-create-product-brief/SKILL.md

@@ -1,6 +0,0 @@
----
-name: bmad-create-product-brief
-description: 'Create product brief through collaborative discovery. Use when the user says "lets create a product brief" or "help me create a project brief"'
----
-
-Follow the instructions in ./workflow.md.

package/src/bmm-skills/1-analysis/bmad-create-product-brief/product-brief.template.md

@@ -1,10 +0,0 @@
----
-stepsCompleted: []
-inputDocuments: []
-date: {{system-date}}
-author: {{user_name}}
----
-
-# Product Brief: {{project_name}}
-
-<!-- Content will be appended sequentially through collaborative workflow steps -->

package/src/bmm-skills/1-analysis/bmad-create-product-brief/steps/step-01-init.md

@@ -1,170 +0,0 @@
----
-# File References
-outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
----
-
-# Step 1: Product Brief Initialization
-
-## STEP GOAL:
-
-Initialize the product brief workflow by detecting continuation state and setting up the document structure for collaborative product discovery.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Role Reinforcement:
-
-- ✅ You are a product-focused Business Analyst facilitator
-- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
-- ✅ We engage in collaborative dialogue, not command-response
-- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision
-- ✅ Maintain collaborative discovery tone throughout
-
-### Step-Specific Rules:
-
-- 🎯 Focus only on initialization and setup - no content generation yet
-- 🚫 FORBIDDEN to look ahead to future steps or assume knowledge from them
-- 💬 Approach: Systematic setup with clear reporting to user
-- 📋 Detect existing workflow state and handle continuation properly
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Show your analysis of current state before taking any action
-- 💾 Initialize document structure and update frontmatter appropriately
-- 📖 Set up frontmatter `stepsCompleted: [1]` before loading next step
-- 🚫 FORBIDDEN to load next step until user selects 'C' (Continue)
-
-## CONTEXT BOUNDARIES:
-
-- Available context: Variables from workflow.md are available in memory
-- Focus: Workflow initialization and document setup only
-- Limits: Don't assume knowledge from other steps or create content yet
-- Dependencies: Configuration loaded from workflow.md initialization
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Check for Existing Workflow State
-
-First, check if the output document already exists:
-
-**Workflow State Detection:**
-
-- Look for file `{outputFile}`
-- If exists, read the complete file including frontmatter
-- If not exists, this is a fresh workflow
-
-### 2. Handle Continuation (If Document Exists)
-
-If the document exists and has frontmatter with `stepsCompleted`:
-
-**Continuation Protocol:**
-
-- **STOP immediately** and load `./step-01b-continue.md`
-- Do not proceed with any initialization tasks
-- Let step-01b handle all continuation logic
-- This is an auto-proceed situation - no user choice needed
-
-### 3. Fresh Workflow Setup (If No Document)
-
-If no document exists or no `stepsCompleted` in frontmatter:
-
-#### A. Input Document Discovery
-
-load context documents using smart discovery. Documents can be in the following locations:
-- {planning_artifacts}/**
-- {output_folder}/**
-- {product_knowledge}/**
-- {project-root}/docs/**
-
-Also - when searching - documents can be a single markdown file, or a folder with an index and multiple files. For Example, if searching for `*foo*.md` and not found, also search for a folder called *foo*/index.md (which indicates sharded content)
-
-Try to discover the following:
-- Brainstorming Reports (`*brainstorming*.md`)
-- Research Documents (`*research*.md`)
-- Project Documentation (generally multiple documents might be found for this in the `{product_knowledge}` or `docs` folder.)
-- Project Context (`**/project-context.md`)
-
-<critical>Confirm what you have found with the user, along with asking if the user wants to provide anything else. Only after this confirmation will you proceed to follow the loading rules</critical>
-
-**Loading Rules:**
-
-- Load ALL discovered files completely that the user confirmed or provided (no offset/limit)
-- If there is a project context, whatever is relevant should try to be biased in the remainder of this whole workflow process
-- For sharded folders, load ALL files to get complete picture, using the index first to potentially know the potential of each document
-- index.md is a guide to what's relevant whenever available
-- Track all successfully loaded files in frontmatter `inputDocuments` array
-
-#### B. Create Initial Document
-
-**Document Setup:**
-
-- Copy the template from `../product-brief.template.md` to `{outputFile}`, and update the frontmatter fields
-
-#### C. Present Initialization Results
-
-**Setup Report to User:**
-"Welcome {{user_name}}! I've set up your product brief workspace for {{project_name}}.
-
-**Document Setup:**
-
-- Created: `{outputFile}` from template
-- Initialized frontmatter with workflow state
-
-**Input Documents Discovered:**
-
-- Research: {number of research files loaded or "None found"}
-- Brainstorming: {number of brainstorming files loaded or "None found"}
-- Project docs: {number of project files loaded or "None found"}
-- Project Context: {number of project context files loaded or "None found"}
-
-**Files loaded:** {list of specific file names or "No additional documents found"}
-
-Do you have any other documents you'd like me to include, or shall we continue to the next step?"
-
-### 4. Present MENU OPTIONS
-
-Display: "**Proceeding to product vision discovery...**"
-
-#### Menu Handling Logic:
-
-- After setup report is presented, without delay, read fully and follow: ./step-02-vision.md
-
-#### EXECUTION RULES:
-
-- This is an initialization step with auto-proceed after setup completion
-- Proceed directly to next step after document setup and reporting
-
-## CRITICAL STEP COMPLETION NOTE
-
-ONLY WHEN [setup completion is achieved and frontmatter properly updated], will you then read fully and follow: `./step-02-vision.md` to begin product vision discovery.
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Existing workflow detected and properly handed off to step-01b
-- Fresh workflow initialized with template and proper frontmatter
-- Input documents discovered and loaded using sharded-first logic
-- All discovered files tracked in frontmatter `inputDocuments`
-- Menu presented and user input handled correctly
-- Frontmatter updated with `stepsCompleted: [1]` before proceeding
-
-### ❌ SYSTEM FAILURE:
-
-- Proceeding with fresh initialization when existing workflow exists
-- Not updating frontmatter with discovered input documents
-- Creating document without proper template structure
-- Not checking sharded folders first before whole files
-- Not reporting discovered documents to user clearly
-- Proceeding without user selecting 'C' (Continue)
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/src/bmm-skills/1-analysis/bmad-create-product-brief/steps/step-01b-continue.md

@@ -1,158 +0,0 @@
----
-# File References
-outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
----
-
-# Step 1B: Product Brief Continuation
-
-## STEP GOAL:
-
-Resume the product brief workflow from where it was left off, ensuring smooth continuation with full context restoration.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Role Reinforcement:
-
-- ✅ You are a product-focused Business Analyst facilitator
-- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
-- ✅ We engage in collaborative dialogue, not command-response
-- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision
-- ✅ Maintain collaborative continuation tone throughout
-
-### Step-Specific Rules:
-
-- 🎯 Focus only on understanding where we left off and continuing appropriately
-- 🚫 FORBIDDEN to modify content completed in previous steps
-- 💬 Approach: Systematic state analysis with clear progress reporting
-- 📋 Resume workflow from exact point where it was interrupted
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Show your analysis of current state before taking any action
-- 💾 Keep existing frontmatter `stepsCompleted` values
-- 📖 Only load documents that were already tracked in `inputDocuments`
-- 🚫 FORBIDDEN to discover new input documents during continuation
-
-## CONTEXT BOUNDARIES:
-
-- Available context: Current document and frontmatter are already loaded
-- Focus: Workflow state analysis and continuation logic only
-- Limits: Don't assume knowledge beyond what's in the document
-- Dependencies: Existing workflow state from previous session
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Analyze Current State
-
-**State Assessment:**
-Review the frontmatter to understand:
-
-- `stepsCompleted`: Which steps are already done
-- `lastStep`: The most recently completed step number
-- `inputDocuments`: What context was already loaded
-- All other frontmatter variables
-
-### 2. Restore Context Documents
-
-**Context Reloading:**
-
-- For each document in `inputDocuments`, load the complete file
-- This ensures you have full context for continuation
-- Don't discover new documents - only reload what was previously processed
-- Maintain the same context as when workflow was interrupted
-
-### 3. Present Current Progress
-
-**Progress Report to User:**
-"Welcome back {{user_name}}! I'm resuming our product brief collaboration for {{project_name}}.
-
-**Current Progress:**
-
-- Steps completed: {stepsCompleted}
-- Last worked on: Step {lastStep}
-- Context documents available: {len(inputDocuments)} files
-
-**Document Status:**
-
-- Current product brief is ready with all completed sections
-- Ready to continue from where we left off
-
-Does this look right, or do you want to make any adjustments before we proceed?"
-
-### 4. Determine Continuation Path
-
-**Next Step Logic:**
-Based on `lastStep` value, determine which step to load next:
-
-- If `lastStep = 1` → Load `./step-02-vision.md`
-- If `lastStep = 2` → Load `./step-03-users.md`
-- If `lastStep = 3` → Load `./step-04-metrics.md`
-- Continue this pattern for all steps
-- If `lastStep = 6` → Workflow already complete
-
-### 5. Handle Workflow Completion
-
-**If workflow already complete (`lastStep = 6`):**
-"Great news! It looks like we've already completed the product brief workflow for {{project_name}}.
-
-The final document is ready at `{outputFile}` with all sections completed through step 6.
-
-Would you like me to:
-
-- Review the completed product brief with you
-- Suggest next workflow steps (like PRD creation)
-- Start a new product brief revision
-
-What would be most helpful?"
-
-### 6. Present MENU OPTIONS
-
-**If workflow not complete:**
-Display: "Ready to continue with Step {nextStepNumber}: {nextStepTitle}?
-
-**Select an Option:** [C] Continue to Step {nextStepNumber}"
-
-#### Menu Handling Logic:
-
-- IF C: Read fully and follow the appropriate next step file based on `lastStep`
-- IF Any other comments or queries: respond and redisplay menu
-
-#### EXECUTION RULES:
-
-- ALWAYS halt and wait for user input after presenting menu
-- ONLY proceed to next step when user selects 'C'
-- User can chat or ask questions about current progress
-
-## CRITICAL STEP COMPLETION NOTE
-
-ONLY WHEN [C continue option] is selected and [current state confirmed], will you then read fully and follow the appropriate next step file to resume the workflow.
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- All previous input documents successfully reloaded
-- Current workflow state accurately analyzed and presented
-- User confirms understanding of progress before continuation
-- Correct next step identified and prepared for loading
-- Proper continuation path determined based on `lastStep`
-
-### ❌ SYSTEM FAILURE:
-
-- Discovering new input documents instead of reloading existing ones
-- Modifying content from already completed steps
-- Loading wrong next step based on `lastStep` value
-- Proceeding without user confirmation of current state
-- Not maintaining context consistency from previous session
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.