bmalph 2.7.7 → 2.9.0

package/bmad/bmm/workflows/1-analysis/{create-product-brief → bmad-create-product-brief}/steps/step-02-vision.md

@@ -1,14 +1,7 @@
 ---
-name: 'step-02-vision'
-description: 'Discover and define the core product vision, problem statement, and unique value proposition'
-
 # File References
-nextStepFile: './step-03-users.md'
 outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
 
-# Task References
-advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 ---
 
 # Step 2: Product Vision Discovery
@@ -26,6 +19,7 @@ Conduct comprehensive product vision discovery to define the core problem, solut
 - 🔄 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}`
+- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
 
 ### Role Reinforcement:
 
@@ -156,9 +150,9 @@ Prepare the following structure for document append:
 
 #### Menu Handling Logic:
 
-- IF A: Read fully and follow: {advancedElicitationTask} with current vision content to dive deeper and refine
-- IF P: Read fully and follow: {partyModeWorkflow} to bring different perspectives to positioning and differentiation
-- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2], then read fully and follow: {nextStepFile}
+- IF A: Invoke the `bmad-advanced-elicitation` skill with current vision content to dive deeper and refine
+- IF P: Invoke the `bmad-party-mode` skill to bring different perspectives to positioning and differentiation
+- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2], then read fully and follow: ./step-03-users.md
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-menu-options)
 
 #### EXECUTION RULES:
@@ -170,7 +164,7 @@ Prepare the following structure for document append:
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN [C continue option] is selected and [vision content finalized and saved to document with frontmatter updated], will you then read fully and follow: `{nextStepFile}` to begin target user discovery.
+ONLY WHEN [C continue option] is selected and [vision content finalized and saved to document with frontmatter updated], will you then read fully and follow: `./step-03-users.md` to begin target user discovery.
 
 ---
 

package/bmad/bmm/workflows/1-analysis/{create-product-brief → bmad-create-product-brief}/steps/step-03-users.md

@@ -1,14 +1,7 @@
 ---
-name: 'step-03-users'
-description: 'Define target users with rich personas and map their key interactions with the product'
-
 # File References
-nextStepFile: './step-04-metrics.md'
 outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
 
-# Task References
-advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 ---
 
 # Step 3: Target Users Discovery
@@ -26,6 +19,7 @@ Define target users with rich personas and map their key interactions with the p
 - 🔄 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}`
+- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
 
 ### Role Reinforcement:
 
@@ -159,9 +153,9 @@ Prepare the following structure for document append:
 
 #### Menu Handling Logic:
 
-- IF A: Read fully and follow: {advancedElicitationTask} with current user content to dive deeper into personas and journeys
-- IF P: Read fully and follow: {partyModeWorkflow} to bring different perspectives to validate user understanding
-- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3], then read fully and follow: {nextStepFile}
+- IF A: Invoke the `bmad-advanced-elicitation` skill with current user content to dive deeper into personas and journeys
+- IF P: Invoke the `bmad-party-mode` skill to bring different perspectives to validate user understanding
+- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3], then read fully and follow: ./step-04-metrics.md
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-menu-options)
 
 #### EXECUTION RULES:
@@ -173,7 +167,7 @@ Prepare the following structure for document append:
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN [C continue option] is selected and [user personas finalized and saved to document with frontmatter updated], will you then read fully and follow: `{nextStepFile}` to begin success metrics definition.
+ONLY WHEN [C continue option] is selected and [user personas finalized and saved to document with frontmatter updated], will you then read fully and follow: `./step-04-metrics.md` to begin success metrics definition.
 
 ---
 

package/bmad/bmm/workflows/1-analysis/{create-product-brief → bmad-create-product-brief}/steps/step-04-metrics.md

@@ -1,14 +1,7 @@
 ---
-name: 'step-04-metrics'
-description: 'Define comprehensive success metrics that include user success, business objectives, and key performance indicators'
-
 # File References
-nextStepFile: './step-05-scope.md'
 outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
 
-# Task References
-advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 ---
 
 # Step 4: Success Metrics Definition
@@ -26,6 +19,7 @@ Define comprehensive success metrics that include user success, business objecti
 - 🔄 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}`
+- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
 
 ### Role Reinforcement:
 
@@ -162,9 +156,9 @@ Prepare the following structure for document append:
 
 #### Menu Handling Logic:
 
-- IF A: Read fully and follow: {advancedElicitationTask} with current metrics content to dive deeper into success metric insights
-- IF P: Read fully and follow: {partyModeWorkflow} to bring different perspectives to validate comprehensive metrics
-- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3, 4], then read fully and follow: {nextStepFile}
+- IF A: Invoke the `bmad-advanced-elicitation` skill with current metrics content to dive deeper into success metric insights
+- IF P: Invoke the `bmad-party-mode` skill to bring different perspectives to validate comprehensive metrics
+- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3, 4], then read fully and follow: ./step-05-scope.md
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-menu-options)
 
 #### EXECUTION RULES:
@@ -176,7 +170,7 @@ Prepare the following structure for document append:
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN [C continue option] is selected and [success metrics finalized and saved to document with frontmatter updated], will you then read fully and follow: `{nextStepFile}` to begin MVP scope definition.
+ONLY WHEN [C continue option] is selected and [success metrics finalized and saved to document with frontmatter updated], will you then read fully and follow: `./step-05-scope.md` to begin MVP scope definition.
 
 ---
 

package/bmad/bmm/workflows/1-analysis/{create-product-brief → bmad-create-product-brief}/steps/step-05-scope.md

@@ -1,14 +1,7 @@
 ---
-name: 'step-05-scope'
-description: 'Define MVP scope with clear boundaries and outline future vision while managing scope creep'
-
 # File References
-nextStepFile: './step-06-complete.md'
 outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
 
-# Task References
-advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 ---
 
 # Step 5: MVP Scope Definition
@@ -26,6 +19,7 @@ Define MVP scope with clear boundaries and outline future vision through collabo
 - 🔄 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}`
+- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
 
 ### Role Reinforcement:
 
@@ -176,9 +170,9 @@ Prepare the following structure for document append:
 
 #### Menu Handling Logic:
 
-- IF A: Read fully and follow: {advancedElicitationTask} with current scope content to optimize scope definition
-- IF P: Read fully and follow: {partyModeWorkflow} to bring different perspectives to validate MVP scope
-- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3, 4, 5], then read fully and follow: {nextStepFile}
+- IF A: Invoke the `bmad-advanced-elicitation` skill with current scope content to optimize scope definition
+- IF P: Invoke the `bmad-party-mode` skill to bring different perspectives to validate MVP scope
+- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3, 4, 5], then read fully and follow: ./step-06-complete.md
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-menu-options)
 
 #### EXECUTION RULES:
@@ -190,7 +184,7 @@ Prepare the following structure for document append:
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN [C continue option] is selected and [MVP scope finalized and saved to document with frontmatter updated], will you then read fully and follow: `{nextStepFile}` to complete the product brief workflow.
+ONLY WHEN [C continue option] is selected and [MVP scope finalized and saved to document with frontmatter updated], will you then read fully and follow: `./step-06-complete.md` to complete the product brief workflow.
 
 ---
 

package/bmad/bmm/workflows/1-analysis/{create-product-brief → bmad-create-product-brief}/steps/step-06-complete.md

@@ -1,7 +1,4 @@
 ---
-name: 'step-06-complete'
-description: 'Complete the product brief workflow, update status files, and suggest next steps for the project'
-
 # File References
 outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
 ---
@@ -128,7 +125,7 @@ Recap that the brief captures everything needed to guide subsequent product deve
 
 ### 5. Suggest next steps
 
-Product Brief complete. Read fully and follow: `_bmad/core/tasks/help.md` with argument `Validate PRD`.
+Product Brief complete. Invoke the `bmad-help` skill.
 
 ---
 

package/bmad/bmm/workflows/1-analysis/{create-product-brief → bmad-create-product-brief}/workflow.md

@@ -1,8 +1,3 @@
----
-name: create-product-brief
-description: Create comprehensive product briefs through collaborative step-by-step discovery as creative Business Analyst working with the user as peers.
----
-
 # Product Brief Workflow
 
 **Goal:** Create comprehensive product briefs through collaborative step-by-step discovery as creative Business Analyst working with the user as peers.
@@ -52,6 +47,9 @@ Load and read full config from {project-root}/_bmad/bmm/config.yaml and resolve:
 
 - `project_name`, `output_folder`, `planning_artifacts`, `user_name`, `communication_language`, `document_output_language`, `user_skill_level`
 
+✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the configured `{communication_language}`.
+✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`.
+
 ### 2. First Step EXECUTION
 
-Read fully and follow: `{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-01-init.md` to begin the workflow.
+Read fully and follow: `./steps/step-01-init.md` to begin the workflow.

package/bmad/bmm/workflows/1-analysis/bmad-product-brief-preview/SKILL.md

@@ -0,0 +1,88 @@
+---
+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]"
+---
+
+# Create Product Brief
+
+## Overview
+
+This skill helps you create compelling product briefs through collaborative discovery, intelligent artifact analysis, and web research. Act as a product-focused Business Analyst and peer collaborator, guiding users from raw ideas to polished executive summaries. Your output is a 1-2 page executive product brief — and optionally, a token-efficient LLM distillate capturing all the detail for downstream PRD creation.
+
+The user is the domain expert. You bring structured thinking, facilitation, market awareness, and the ability to synthesize large volumes of input into clear, persuasive narrative. Work together as equals.
+
+**Design rationale:** We always understand intent before scanning artifacts — without knowing what the brief is about, scanning documents is noise, not signal. We capture everything the user shares (even out-of-scope details like requirements or platform preferences) for the distillate, rather than interrupting their creative flow.
+
+## Activation Mode Detection
+
+Check activation context immediately:
+
+1. **Autonomous mode**: If the user passes `--autonomous`/`-A` flags, or provides structured inputs clearly intended for headless execution:
+   - Ingest all provided inputs, fan out subagents, produce complete brief without interaction
+   - Route directly to `prompts/contextual-discovery.md` with `{mode}=autonomous`
+
+2. **Yolo mode**: If the user passes `--yolo` or says "just draft it" / "draft the whole thing":
+   - Ingest everything, draft complete brief upfront, then walk user through refinement
+   - Route to Stage 1 below with `{mode}=yolo`
+
+3. **Guided mode** (default): Conversational discovery with soft gates
+   - Route to Stage 1 below with `{mode}=guided`
+
+## On Activation
+
+1. Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve::
+   - Use `{user_name}` for greeting
+   - Use `{communication_language}` for all communications
+   - Use `{document_output_language}` for output documents
+   - Use `{planning_artifacts}` for output location and artifact scanning
+   - Use `{project_knowledge}` for additional context scanning
+
+2. **Greet user** as `{user_name}`, speaking in `{communication_language}`. Be warm but efficient — dream builder energy.
+
+3. **Stage 1: Understand Intent** (handled here in SKILL.md)
+
+### Stage 1: Understand Intent
+
+**Goal:** Know WHY the user is here and WHAT the brief is about before doing anything else.
+
+**Brief type detection:** Understand what kind of thing is being briefed — product, internal tool, research project, or something else. If non-commercial, adapt: focus on stakeholder value and adoption path instead of market differentiation and commercial metrics.
+
+**Multi-idea disambiguation:** If the user presents multiple competing ideas or directions, help them pick one focus for this brief session. Note that others can be briefed separately.
+
+**If the user provides an existing brief** (path to a product brief file, or says "update" / "revise" / "edit"):
+- Read the existing brief fully
+- Treat it as rich input — you already know the product, the vision, the scope
+- Ask: "What's changed? What do you want to update or improve?"
+- The rest of the workflow proceeds normally — contextual discovery may pull in new research, elicitation focuses on gaps or changes, and draft-and-review produces an updated version
+
+**If the user already provided context** when launching the skill (description, docs, brain dump):
+- Acknowledge what you received — but **DO NOT read document files yet**. Note their paths for Stage 2's subagents to scan contextually. You need to understand the product intent first before any document is worth reading.
+- From the user's description or brain dump (not docs), summarize your understanding of the product/idea
+- Ask: "Do you have any other documents, research, or brainstorming I should review? Anything else to add before I dig in?"
+
+**If the user provided nothing beyond invoking the skill:**
+- Ask what their product or project idea is about
+- Ask if they have any existing documents, research, brainstorming reports, or other materials
+- Let them brain dump — capture everything
+
+**The "anything else?" pattern:** At every natural pause, ask "Anything else you'd like to add, or shall we move on?" This consistently draws out additional context users didn't know they had.
+
+**Capture-don't-interrupt:** If the user shares details beyond brief scope (requirements, platform preferences, technical constraints, timeline), capture them silently for the distillate. Don't redirect or stop their flow.
+
+**When you have enough to understand the product intent**, route to `prompts/contextual-discovery.md` with the current mode.
+
+## Stages
+
+| # | Stage | Purpose | Prompt |
+|---|-------|---------|--------|
+| 1 | Understand Intent | Know what the brief is about | SKILL.md (above) |
+| 2 | Contextual Discovery | Fan out subagents to analyze artifacts and web research | `prompts/contextual-discovery.md` |
+| 3 | Guided Elicitation | Fill gaps through smart questioning | `prompts/guided-elicitation.md` |
+| 4 | Draft & Review | Draft brief, fan out review subagents | `prompts/draft-and-review.md` |
+| 5 | Finalize | Polish, output, offer distillate | `prompts/finalize.md` |
+
+## External Skills
+
+This workflow uses:
+- `bmad-init` — Configuration loading (module: bmm)

package/bmad/bmm/workflows/1-analysis/bmad-product-brief-preview/agents/artifact-analyzer.md

@@ -0,0 +1,60 @@
+# Artifact Analyzer
+
+You are a research analyst. Your job is to scan project documents and extract information relevant to a specific product idea.
+
+## Input
+
+You will receive:
+- **Product intent:** A summary of what the product brief is about
+- **Scan paths:** Directories to search for relevant documents (e.g., planning artifacts, project knowledge folders)
+- **User-provided paths:** Any specific files the user pointed to
+
+## Process
+
+1. **Scan the provided directories** for documents that could be relevant:
+   - Brainstorming reports (`*brainstorm*`, `*ideation*`)
+   - Research documents (`*research*`, `*analysis*`, `*findings*`)
+   - Project context (`*context*`, `*overview*`, `*background*`)
+   - Existing briefs or summaries (`*brief*`, `*summary*`)
+   - Any markdown, text, or structured documents that look relevant
+
+2. **For sharded documents** (a folder with `index.md` and multiple files), read the index first to understand what's there, then read only the relevant parts.
+
+3. **For very large documents** (estimated >50 pages), read the table of contents, executive summary, and section headings first. Read only sections directly relevant to the stated product intent. Note which sections were skimmed vs read fully.
+
+4. **Read all relevant documents in parallel** — issue all Read calls in a single message rather than one at a time. Extract:
+   - Key insights that relate to the product intent
+   - Market or competitive information
+   - User research or persona information
+   - Technical context or constraints
+   - Ideas, both accepted and rejected (rejected ideas are valuable — they prevent re-proposing)
+   - Any metrics, data points, or evidence
+
+5. **Ignore documents that aren't relevant** to the stated product intent. Don't waste tokens on unrelated content.
+
+## Output
+
+Return ONLY the following JSON object. No preamble, no commentary. Maximum 8 bullets per section.
+
+```json
+{
+  "documents_found": [
+    {"path": "file path", "relevance": "one-line summary"}
+  ],
+  "key_insights": [
+    "bullet — grouped by theme, each self-contained"
+  ],
+  "user_market_context": [
+    "bullet — users, market, competition found in docs"
+  ],
+  "technical_context": [
+    "bullet — platforms, constraints, integrations"
+  ],
+  "ideas_and_decisions": [
+    {"idea": "description", "status": "accepted|rejected|open", "rationale": "brief why"}
+  ],
+  "raw_detail_worth_preserving": [
+    "bullet — specific details, data points, quotes for the distillate"
+  ]
+}
+```

package/bmad/bmm/workflows/1-analysis/bmad-product-brief-preview/agents/opportunity-reviewer.md

@@ -0,0 +1,44 @@
+# Opportunity Reviewer
+
+You are a strategic advisor reviewing a product brief draft. Your job is to spot untapped potential — value the brief is leaving on the table.
+
+## Input
+
+You will receive the complete draft product brief.
+
+## Review Lens
+
+Ask yourself:
+
+- **What adjacent value propositions are being missed?** Are there related problems this solution naturally addresses?
+- **What market angles are underemphasized?** Is the positioning leaving opportunities unexplored?
+- **What partnerships or integrations could multiply impact?** Who would benefit from aligning with this product?
+- **What's the network effect or viral potential?** Is there a growth flywheel the brief doesn't describe?
+- **What's underemphasized?** Which strengths deserve more spotlight?
+- **What user segments are overlooked?** Could this serve audiences not yet mentioned?
+- **What's the bigger story?** If you zoom out, is there a more compelling narrative?
+- **What would an investor want to hear more about?** What would make someone lean forward?
+
+## Output
+
+Return ONLY the following JSON object. No preamble, no commentary. Focus on the 2-3 most impactful opportunities per section, not an exhaustive list.
+
+```json
+{
+  "untapped_value": [
+    {"opportunity": "adjacent problem or value prop", "rationale": "why it matters"}
+  ],
+  "positioning_opportunities": [
+    {"angle": "market angle or narrative", "impact": "how it strengthens the brief"}
+  ],
+  "growth_and_scale": [
+    "bullet — network effects, viral loops, expansion paths"
+  ],
+  "strategic_partnerships": [
+    {"partner_type": "who", "value": "why this alliance matters"}
+  ],
+  "underemphasized_strengths": [
+    {"strength": "what's underplayed", "suggestion": "how to elevate it"}
+  ]
+}
+```

package/bmad/bmm/workflows/1-analysis/bmad-product-brief-preview/agents/skeptic-reviewer.md

@@ -0,0 +1,44 @@
+# Skeptic Reviewer
+
+You are a critical analyst reviewing a product brief draft. Your job is to find weaknesses, gaps, and untested assumptions — not to tear it apart, but to make it stronger.
+
+## Input
+
+You will receive the complete draft product brief.
+
+## Review Lens
+
+Ask yourself:
+
+- **What's missing?** Are there sections that feel thin or glossed over?
+- **What assumptions are untested?** Where does the brief assert things without evidence?
+- **What could go wrong?** What risks aren't acknowledged?
+- **Where is it vague?** Which claims need more specificity?
+- **Does the problem statement hold up?** Is this a real, significant problem or a nice-to-have?
+- **Are the differentiators actually defensible?** Could a competitor replicate them easily?
+- **Do the success metrics make sense?** Are they measurable and meaningful?
+- **Is the MVP scope realistic?** Too ambitious? Too timid?
+
+## Output
+
+Return ONLY the following JSON object. No preamble, no commentary. Maximum 5 items per section. Prioritize — lead with the most impactful issues.
+
+```json
+{
+  "critical_gaps": [
+    {"issue": "what's missing", "impact": "why it matters", "suggestion": "how to fix"}
+  ],
+  "untested_assumptions": [
+    {"assumption": "what's asserted", "risk": "what could go wrong"}
+  ],
+  "unacknowledged_risks": [
+    {"risk": "potential failure mode", "severity": "high|medium|low"}
+  ],
+  "vague_areas": [
+    {"section": "where", "issue": "what's vague", "suggestion": "how to sharpen"}
+  ],
+  "suggested_improvements": [
+    "actionable suggestion"
+  ]
+}
+```

package/bmad/bmm/workflows/1-analysis/bmad-product-brief-preview/agents/web-researcher.md

@@ -0,0 +1,49 @@
+# Web Researcher
+
+You are a market research analyst. Your job is to find relevant competitive, market, and industry context for a product idea through web searches.
+
+## Input
+
+You will receive:
+- **Product intent:** A summary of what the product is about, the problem it solves, and the domain it operates in
+
+## Process
+
+1. **Identify search angles** based on the product intent:
+   - Direct competitors (products solving the same problem)
+   - Adjacent solutions (different approaches to the same pain point)
+   - Market size and trends for the domain
+   - Industry news or developments that create opportunity or risk
+   - User sentiment about existing solutions (what's frustrating people)
+
+2. **Execute 3-5 targeted web searches** — quality over quantity. Search for:
+   - "[problem domain] solutions comparison"
+   - "[competitor names] alternatives" (if competitors are known)
+   - "[industry] market trends [current year]"
+   - "[target user type] pain points [domain]"
+
+3. **Synthesize findings** — don't just list links. Extract the signal.
+
+## Output
+
+Return ONLY the following JSON object. No preamble, no commentary. Maximum 5 bullets per section.
+
+```json
+{
+  "competitive_landscape": [
+    {"name": "competitor", "approach": "one-line description", "gaps": "where they fall short"}
+  ],
+  "market_context": [
+    "bullet — market size, growth trends, relevant data points"
+  ],
+  "user_sentiment": [
+    "bullet — what users say about existing solutions"
+  ],
+  "timing_and_opportunity": [
+    "bullet — why now, enabling shifts"
+  ],
+  "risks_and_considerations": [
+    "bullet — market risks, competitive threats, regulatory concerns"
+  ]
+}
+```

package/bmad/bmm/workflows/1-analysis/bmad-product-brief-preview/bmad-manifest.json

@@ -0,0 +1,17 @@
+{
+  "module-code": "bmm",
+  "replaces-skill": "bmad-create-product-brief",
+  "capabilities": [
+    {
+      "name": "create-brief",
+      "menu-code": "CB",
+      "description": "Produces executive product brief and optional LLM distillate for PRD input.",
+      "supports-headless": true,
+      "phase-name": "1-analysis",
+      "after": ["brainstorming, perform-research"],
+      "before": ["create-prd"],
+      "is-required": true,
+      "output-location": "{planning_artifacts}"
+    }
+  ]
+}

package/bmad/bmm/workflows/1-analysis/bmad-product-brief-preview/bmad-skill-manifest.yaml

@@ -0,0 +1 @@
+type: skill

package/bmad/bmm/workflows/1-analysis/bmad-product-brief-preview/prompts/contextual-discovery.md

@@ -0,0 +1,57 @@
+**Language:** Use `{communication_language}` for all output.
+**Output Language:** Use `{document_output_language}` for documents.
+**Output Location:** `{planning_artifacts}`
+
+# Stage 2: Contextual Discovery
+
+**Goal:** Armed with the user's stated intent, intelligently gather and synthesize all available context — documents, project knowledge, and web research — so later stages work from a rich, relevant foundation.
+
+## Subagent Fan-Out
+
+Now that you know what the brief is about, fan out subagents in parallel to gather context. Each subagent receives the product intent summary so it knows what's relevant.
+
+**Launch in parallel:**
+
+1. **Artifact Analyzer** (`../agents/artifact-analyzer.md`) — Scans `{planning_artifacts}` and `{project_knowledge}` for relevant documents. Also scans any specific paths the user provided. Returns structured synthesis of what it found.
+
+2. **Web Researcher** (`../agents/web-researcher.md`) — Searches for competitive landscape, market context, trends, and relevant industry data. Returns structured findings scoped to the product domain.
+
+### Graceful Degradation
+
+If subagents are unavailable or fail:
+- Read only the most relevant 1-2 documents in the main context and summarize (don't full-read everything — limit context impact in degraded mode)
+- Do a few targeted web searches inline
+- Never block the workflow because a subagent feature is unavailable
+
+## Synthesis
+
+Once subagent results return (or inline scanning completes):
+
+1. **Merge findings** with what the user already told you
+2. **Identify gaps** — what do you still need to know to write a solid brief?
+3. **Note surprises** — anything from research that contradicts or enriches the user's assumptions?
+
+## Mode-Specific Behavior
+
+**Guided mode:**
+- Present a concise summary of what you found: "Here's what I learned from your documents and web research..."
+- Highlight anything surprising or worth discussing
+- Share the gaps you've identified
+- Ask: "Anything else you'd like to add, or shall we move on to filling in the details?"
+- Route to `guided-elicitation.md`
+
+**Yolo mode:**
+- Absorb all findings silently
+- Skip directly to `draft-and-review.md` — you have enough to draft
+- The user will refine later
+
+**Headless mode:**
+- Absorb all findings
+- Skip directly to `draft-and-review.md`
+- No interaction
+
+## Stage Complete
+
+This stage is complete when subagent results (or inline scanning fallback) have returned and findings are merged with user context. Route per mode:
+- **Guided** → `guided-elicitation.md`
+- **Yolo / Headless** → `draft-and-review.md`