bmad-method 6.7.1-next.7 → 6.7.1-next.9

package/README.md

@@ -79,11 +79,13 @@ BMad Method extends with official modules for specialized domains. Available dur
 
 ## Web Bundles
 
-V4 shipped web bundles. V6 brings them back, new and improved. Find them in [`web-bundles/`](./web-bundles/).
+V4 shipped web bundles. V6 brings them back, new and improved.
 
-Web bundles package selected BMad skills for installation as **Google Gemini Gems** and **ChatGPT Custom GPTs**. Use them to do the upfront planning work (brainstorming, product briefs, PRDs, PRFAQs, UX specs, market and industry research) in your web LLM subscription, then bring the polished artifacts into your IDE for implementation. Planning runs on a flat-rate subscription instead of metered IDE tokens, which is a meaningful cost saver on longer engagements. Ensure that when using you choose the best model available to you in Gemini or ChatGPT.
+Web bundles package selected BMad skills for installation as **Google Gemini Gems** and **ChatGPT Custom GPTs**. Use them to do the upfront planning work (brainstorming, product briefs, PRDs, PRFAQs, UX specs, market and industry research) in your web LLM subscription, then bring the polished artifacts into your IDE for implementation. Planning runs on a flat-rate subscription instead of metered IDE tokens, which is a meaningful cost saver on longer engagements. Choose the best model available to you in Gemini or ChatGPT.
 
-Current shelf: brainstorming, product brief, PRFAQ, PRD, UX, market & industry research. Each bundle has its own `INSTRUCTIONS.md` to follow; the setup pattern is the same across the shelf (create a Gem or GPT, attach knowledge file(s) (bundle customized SKILL.md and additional content), paste the instructions block, save). See [the web bundles guide](https://docs.bmad-method.org/explanation/web-bundles/) for the concept and [the how-to](https://docs.bmad-method.org/how-to/use-web-bundles/) for setup details.
+Current shelf: brainstorming, product brief, PRFAQ, PRD, UX, market & industry research.
+
+**Browse and install at [bmadcode.com/web-bundles](https://bmadcode.com/web-bundles/)**. One card per bundle, inline install steps for Gemini and ChatGPT, one-click ZIP download. See [the web bundles guide](https://docs.bmad-method.org/explanation/web-bundles/) for the concept.
 
 ## Documentation
 

package/package.json

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

package/src/bmm-skills/4-implementation/bmad-dev-story/SKILL.md

@@ -10,7 +10,7 @@ description: 'Execute story implementation following a context filled story spec
 **Your Role:** Developer implementing the story.
 - Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}
 - Generate all documents in {document_output_language}
-- Only modify the story file in these areas: Tasks/Subtasks checkboxes, Dev Agent Record (Debug Log, Completion Notes), File List, Change Log, and Status
+- Only modify the story file in these areas: YAML frontmatter `baseline_commit`, Tasks/Subtasks checkboxes, Dev Agent Record (Debug Log, Completion Notes), File List, Change Log, and Status
 - Execute ALL steps in exact order; do NOT skip steps
 - Absolutely DO NOT stop because of "milestones", "significant progress", or "session boundaries". Continue in a single execution until the story is COMPLETE (all ACs satisfied and all tasks/subtasks checked) UNLESS a HALT condition is triggered or the USER gives other instruction.
 - Do NOT schedule a "next session" or request review pauses unless a HALT condition applies. Only Step 9 decides completion.
@@ -76,7 +76,7 @@ Activation is complete. If `activation_steps_prepend` or `activation_steps_appen
 <workflow>
   <critical>Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}</critical>
   <critical>Generate all documents in {document_output_language}</critical>
-  <critical>Only modify the story file in these areas: Tasks/Subtasks checkboxes, Dev Agent Record (Debug Log, Completion Notes), File List,
+  <critical>Only modify the story file in these areas: YAML frontmatter `baseline_commit`, Tasks/Subtasks checkboxes, Dev Agent Record (Debug Log, Completion Notes), File List,
     Change Log, and Status</critical>
   <critical>Execute ALL steps in exact order; do NOT skip steps</critical>
   <critical>Absolutely DO NOT stop because of "milestones", "significant progress", or "session boundaries". Continue in a single execution
@@ -261,26 +261,40 @@ Activation is complete. If `activation_steps_prepend` or `activation_steps_appen
   </step>
 
   <step n="4" goal="Mark story in-progress" tag="sprint-status">
+    <action>If story file YAML frontmatter already contains `baseline_commit`, preserve the existing value and do not overwrite it</action>
+
     <check if="{{sprint_status}} file exists">
       <action>Load the FULL file: {{sprint_status}}</action>
       <action>Read all development_status entries to find {{story_key}}</action>
-      <action>Get current status value for development_status[{{story_key}}]</action>
+      <action>Set {{current_status}} to development_status[{{story_key}}]</action>
+    </check>
+
+    <check if="{{sprint_status}} file does NOT exist">
+      <action>Set {{current_status}} to the story file Status section value</action>
+    </check>
+
+    <check if="{{current_status}} == 'ready-for-dev' AND story file YAML frontmatter does NOT contain baseline_commit">
+      <action>Run `git rev-parse HEAD` to capture current commit into {{baseline_commit}}; if git/version control is unavailable, set {{baseline_commit}} = `NO_VCS`</action>
+      <action>If story file YAML frontmatter exists, add `baseline_commit: {{baseline_commit}}` to the frontmatter</action>
+      <action>If story file has no YAML frontmatter, create frontmatter at the top containing only `baseline_commit: {{baseline_commit}}`</action>
+    </check>
 
-      <check if="current status == 'ready-for-dev' OR review_continuation == true">
+    <check if="{{sprint_status}} file exists">
+      <check if="{{current_status}} == 'ready-for-dev' OR (review_continuation == true AND {{current_status}} != 'in-progress')">
         <action>Update the story in the sprint status report to = "in-progress"</action>
         <action>Update last_updated field to current date</action>
         <output>🚀 Starting work on story {{story_key}}
-          Status updated: ready-for-dev → in-progress
+          Status updated: {{current_status}} → in-progress
         </output>
       </check>
 
-      <check if="current status == 'in-progress'">
+      <check if="{{current_status}} == 'in-progress'">
         <output>⏯️ Resuming work on story {{story_key}}
           Story is already marked in-progress
         </output>
       </check>
 
-      <check if="current status is neither ready-for-dev nor in-progress">
+      <check if="{{current_status}} is neither ready-for-dev nor in-progress">
         <output>⚠️ Unexpected story status: {{current_status}}
           Expected ready-for-dev or in-progress. Continuing anyway...
         </output>

package/tools/bundle-web-bundles.js

@@ -0,0 +1,117 @@
+/**
+ * Web Bundle Release Packager
+ *
+ * Zips each bundle under web-bundles/ into dist/web-bundles/{slug}.zip
+ * for attachment to a GitHub Release.
+ *
+ * Usage:
+ *   node tools/bundle-web-bundles.js
+ *
+ * After running, the script prints the exact `gh release create` command
+ * (with the correct tag from bundles.json) for you to copy.
+ */
+
+const fs = require('node:fs');
+const path = require('node:path');
+const { execSync, execFileSync } = require('node:child_process');
+
+const REPO_ROOT = path.resolve(__dirname, '..');
+const BUNDLES_DIR = path.join(REPO_ROOT, 'web-bundles');
+const DIST_DIR = path.join(REPO_ROOT, 'dist', 'web-bundles');
+const MANIFEST = path.join(BUNDLES_DIR, 'bundles.json');
+const SLUG_RE = /^[a-z0-9][a-z0-9-]*$/;
+
+function fail(msg) {
+  console.error(`[ERROR] ${msg}`);
+  process.exit(1);
+}
+
+function requireZipCli() {
+  try {
+    execSync('zip -v', { stdio: 'ignore' });
+  } catch {
+    fail("'zip' CLI not found on PATH. Install zip (macOS: preinstalled; Debian/Ubuntu: apt install zip; Alpine: apk add zip) and re-run.");
+  }
+}
+
+function loadManifest() {
+  if (!fs.existsSync(MANIFEST)) {
+    fail(`bundles.json not found at ${MANIFEST}`);
+  }
+  let manifest;
+  try {
+    manifest = JSON.parse(fs.readFileSync(MANIFEST, 'utf-8'));
+  } catch (error) {
+    fail(`bundles.json is not valid JSON: ${error.message}`);
+  }
+  if (!Array.isArray(manifest.bundles) || manifest.bundles.length === 0) {
+    fail('bundles.json is missing a non-empty "bundles" array.');
+  }
+  if (typeof manifest.releaseTag !== 'string' || !manifest.releaseTag) {
+    fail('bundles.json is missing "releaseTag".');
+  }
+  return manifest;
+}
+
+function main() {
+  requireZipCli();
+  const manifest = loadManifest();
+  const releaseTag = manifest.releaseTag;
+
+  fs.mkdirSync(DIST_DIR, { recursive: true });
+
+  console.log(`Packaging ${manifest.bundles.length} bundles for release ${releaseTag}\n`);
+
+  const zipped = [];
+  const missing = [];
+  const invalid = [];
+  for (const bundle of manifest.bundles) {
+    if (!bundle.slug || !SLUG_RE.test(bundle.slug)) {
+      invalid.push(bundle.slug || '(no slug)');
+      console.error(`  [INVALID] slug must match ${SLUG_RE} — got: ${bundle.slug}`);
+      continue;
+    }
+    const src = path.join(BUNDLES_DIR, bundle.slug);
+    if (!fs.existsSync(src)) {
+      missing.push(bundle.slug);
+      console.error(`  [MISSING] ${bundle.slug} — directory not found`);
+      continue;
+    }
+
+    const out = path.join(DIST_DIR, `${bundle.slug}.zip`);
+    if (fs.existsSync(out)) fs.unlinkSync(out);
+
+    try {
+      execFileSync('zip', ['-r', '-X', '-q', out, bundle.slug, '-x', '*.DS_Store'], {
+        cwd: BUNDLES_DIR,
+        stdio: 'inherit',
+      });
+    } catch (error) {
+      fail(`zip failed for ${bundle.slug}: ${error.message}`);
+    }
+
+    const size = (fs.statSync(out).size / 1024).toFixed(1);
+    console.log(`  [OK] ${bundle.slug}.zip (${size} KB)`);
+    zipped.push(bundle.slug);
+  }
+
+  if (invalid.length > 0) {
+    fail(`Refusing to publish: ${invalid.length} bundle(s) have invalid slugs: ${invalid.join(', ')}`);
+  }
+  if (missing.length > 0) {
+    fail(`Refusing to publish an incomplete release: missing directories for ${missing.join(', ')}`);
+  }
+  if (zipped.length === 0) {
+    fail('No bundles were packaged. Check bundles.json against web-bundles/ subdirectories.');
+  }
+
+  console.log(`\nWrote ${zipped.length} bundles to ${path.relative(REPO_ROOT, DIST_DIR)}/`);
+  console.log('\nNext step — create or update the GitHub Release:\n');
+  console.log(`  gh release create ${releaseTag} dist/web-bundles/*.zip \\`);
+  console.log(`    --title "${releaseTag}" \\`);
+  console.log(`    --notes "BMad web bundles for Gemini Gems and ChatGPT Custom GPTs. See https://bmadcode.com/web-bundles/"\n`);
+  console.log('Or, to refresh an existing release:\n');
+  console.log(`  gh release upload ${releaseTag} dist/web-bundles/*.zip --clobber\n`);
+}
+
+main();

package/tools/installer/modules/custom-module-manager.js

@@ -19,6 +19,10 @@ function quoteCustomRef(ref) {
 class CustomModuleManager {
   /** @type {Map<string, Object>} Shared across all instances: module code -> ResolvedModule */
   static _resolutionCache = new Map();
+  /** @type {Set<string>} Repo roots refreshed in the current process (dedupe quick-update fetches). */
+  static _refreshedRepoPaths = new Set();
+  /** @type {Map<string, Promise<void>>} In-flight refresh operations keyed by repo path. */
+  static _refreshInFlight = new Map();
 
   // ─── Source Parsing ───────────────────────────────────────────────────────
 
@@ -431,8 +435,12 @@ class CustomModuleManager {
         }
         fetchSpinner.stop(`Updated ${displayName}`);
       } catch {
-        fetchSpinner.error(`Update failed, re-downloading ${displayName}`);
-        await fs.remove(repoCacheDir);
+        // Fetch failed against an existing cache — most often the remote is
+        // unreachable (network down, repo deleted/moved, auth revoked).
+        // Preserve the previous clone so re-deploy still works from cached
+        // content; surface a warning so the user knows the cache is stale.
+        fetchSpinner.error(`Could not refresh ${displayName} — keeping cached copy`);
+        await prompts.log.warn(`Custom module ${displayName} was not refreshed (remote unreachable). Using cached copy.`);
       }
     }
 
@@ -466,6 +474,32 @@ class CustomModuleManager {
     } catch {
       // swallow — a non-git repo (local path) wouldn't reach here anyway
     }
+    // Best-effort: capture the remote default branch name so channel marker
+    // metadata for "next" reflects the actual tracked ref (not always "main").
+    let defaultRef = 'main';
+    if (!effectiveVersion) {
+      try {
+        const symbolic = execSync('git symbolic-ref --short refs/remotes/origin/HEAD', {
+          cwd: repoCacheDir,
+          stdio: 'pipe',
+        })
+          .toString()
+          .trim();
+        if (symbolic.startsWith('origin/')) {
+          defaultRef = symbolic.slice('origin/'.length) || defaultRef;
+        }
+      } catch {
+        // Fallback to previous marker value when symbolic ref is unavailable.
+        try {
+          const existingMarker = await fs.readJson(path.join(repoCacheDir, '.bmad-channel.json'));
+          if (existingMarker?.channel === 'next' && typeof existingMarker.version === 'string' && existingMarker.version.trim()) {
+            defaultRef = existingMarker.version.trim();
+          }
+        } catch {
+          // Keep default fallback.
+        }
+      }
+    }
 
     // Write source metadata for later URL reconstruction
     const metadataPath = path.join(repoCacheDir, '.bmad-source.json');
@@ -478,6 +512,15 @@ class CustomModuleManager {
       sha: resolvedSha,
       clonedAt: new Date().toISOString(),
     });
+    // Keep a channel marker in custom cache too so update paths that rely on
+    // channel metadata (same as official-module cache) can treat this clone as
+    // refreshable. URL + no explicit ref => next, explicit ref => pinned.
+    await fs.writeJson(path.join(repoCacheDir, '.bmad-channel.json'), {
+      channel: effectiveVersion ? 'pinned' : 'next',
+      version: effectiveVersion || defaultRef,
+      sha: resolvedSha,
+      writtenAt: new Date().toISOString(),
+    });
 
     // Install dependencies if package.json exists (skip during browsing/analysis)
     const packageJsonPath = path.join(repoCacheDir, 'package.json');
@@ -642,6 +685,13 @@ class CustomModuleManager {
       const repoRoots = await this._findCacheRepoRoots(cacheDir);
 
       for (const { repoPath, metadata } of repoRoots) {
+        // Quick-update path: refresh URL-backed cached repos before reading
+        // files from them so re-deploy uses latest commits for `next` and
+        // the pinned ref for `pinned`.
+        if (options.bmadDir && metadata?.rawInput) {
+          await this._refreshRepoCacheOnce(repoPath, metadata);
+        }
+
         // Check marketplace.json for matching module code
         const marketplacePath = path.join(repoPath, '.claude-plugin', 'marketplace.json');
         if (!(await fs.pathExists(marketplacePath))) continue;
@@ -692,6 +742,45 @@ class CustomModuleManager {
     return this._findLocalSourceFromManifest(moduleCode, options);
   }
 
+  /**
+   * Refresh one cached repo at most once per process with in-flight dedupe.
+   * Prevents concurrent quick-update callers from racing the same cache path.
+   * @param {string} repoPath - Absolute cache repo path
+   * @param {Object} metadata - Parsed .bmad-source.json metadata
+   */
+  async _refreshRepoCacheOnce(repoPath, metadata) {
+    if (CustomModuleManager._refreshedRepoPaths.has(repoPath)) return;
+
+    const existing = CustomModuleManager._refreshInFlight.get(repoPath);
+    if (existing) {
+      await existing;
+      return;
+    }
+
+    const refreshPromise = (async () => {
+      try {
+        await this.cloneRepo(metadata.rawInput, {
+          silent: true,
+          pinOverride: metadata.version || undefined,
+        });
+        CustomModuleManager._refreshedRepoPaths.add(repoPath);
+      } catch (error_) {
+        // cloneRepo only throws here for unrecoverable cases (no cache present
+        // and a fresh clone failed, or an unexpected internal error). The
+        // common "remote unreachable but cache exists" case is handled inside
+        // cloneRepo, which preserves the clone and returns normally. Reaching
+        // this catch means we have no usable cache — surface a warning so the
+        // failure isn't silent.
+        await prompts.log.warn(`Refresh of cached custom module at ${path.basename(repoPath)} failed: ${error_?.message || error_}`);
+      } finally {
+        CustomModuleManager._refreshInFlight.delete(repoPath);
+      }
+    })();
+
+    CustomModuleManager._refreshInFlight.set(repoPath, refreshPromise);
+    await refreshPromise;
+  }
+
   /**
    * Check the installation manifest for a localPath entry for this module.
    * Used as fallback when the module was installed from a local source (no cache entry).

package/web-bundles/README.md

@@ -2,39 +2,45 @@
 
 V4 shipped web bundles. V6 brings them back, new and improved. Each bundle packages a BMad skill as a self-contained install for **Google Gemini Gems** and **ChatGPT Custom GPTs**, so you can run the planning work in your web LLM subscription before opening your IDE.
 
-## Why use these
+## Install
+
+**Go to [bmadcode.com/web-bundles](https://bmadcode.com/web-bundles/).**
+
+The site lists every bundle in a card grid, walks you through the Gemini and ChatGPT setup inline, and hands you the ZIP download in one click. That is the only supported install path.
+
+Why a single front door:
+
+- One place to keep install steps current as Gemini and ChatGPT evolve.
+- Versioned releases. Every shelf update ships as a tagged GitHub Release; the site always points at the newest tag.
+- One signup gets you on the list for new bundles as they ship.
+
+## Why use them
 
 - **Cost.** Web LLM subscriptions are flat-rate. Run brainstorming, briefs, PRDs, and research there instead of burning IDE tokens.
 - **Right tool for the job.** Planning conversations want Canvas, image generation, and Deep Research. Implementation wants the codebase and a terminal. Use each where it's strongest.
-- **Persona swapping.** Every bundle's `INSTRUCTIONS.md` carries a default persona and a contrasting swap example. Change voices without touching the protocol.
+- **Persona swapping.** Every bundle ships a default persona and a contrasting swap example. Change voices without touching the protocol.
 
 ## The shelf
 
 | Bundle | Purpose |
 | --- | --- |
-| [`brainstorming-coach/`](./brainstorming-coach/) | Facilitated ideation across 60 techniques. Defaults to **Carson** (Osborn lineage); swap to **Mary** for analyst rigor. |
-| [`product-brief-coach/`](./product-brief-coach/) | Build a one-page product brief through guided discovery. |
-| [`prfaq-coach/`](./prfaq-coach/) | Working Backwards PRFAQ challenge (Bezos lineage) to forge and stress-test product concepts. |
-| [`prd-coach/`](./prd-coach/) | Product Requirements Document with built-in validation (Cagan lineage). |
-| [`ux-coach/`](./ux-coach/) | UX patterns, flows, and design specifications. |
-| [`market-and-industry-research/`](./market-and-industry-research/) | Market research, customer JTBD, competitive landscape, regulatory and technical lenses. Deep Research mode integrated. |
+| Brainstorming Coach | Facilitated ideation across 60 techniques. Defaults to **Carson** (Osborn lineage); swap to **Mary** for analyst rigor. |
+| Product Brief Coach | Build a product brief through guided discovery. Create, Update, or Validate modes. |
+| PRFAQ Coach | Working Backwards PRFAQ challenge (Bezos lineage) to forge and stress-test product concepts. |
+| PRD Coach | Product Requirements Document with built-in validation (Cagan lineage). |
+| UX Coach | UX patterns, flows, and design specifications. Pairs with Google Stitch. |
+| Market & Industry Research | Market research, customer JTBD, competitive landscape, regulatory and technical lenses. Deep Research mode integrated. |
 
-## Install
-
-Each bundle has its own `INSTRUCTIONS.md` with platform-specific setup steps. Pattern is the same:
-
-1. Create a Gem (Gemini) or Custom GPT (ChatGPT).
-2. Upload the bundle's `SKILL.md` (and any data files) as knowledge.
-3. Paste the block below the **PASTE BOUNDARY** into the instructions box.
-4. Enable Web Browsing / Deep Research if the bundle's install steps call for it.
-
-Gemini Gems require Gemini Advanced. ChatGPT Custom GPTs require Plus, Pro, Business, or Enterprise; Deep Research has its own plan limits.
+Requires Gemini Advanced (for Gems) or ChatGPT Plus / Pro / Business / Enterprise (for Custom GPTs). Deep Research has its own plan limits.
 
 ## Build your own
 
 Web bundles are generated from BMad skills using the [`bmad-os-skill-to-bundle`](https://github.com/bmad-code-org/bmad-utility-skills) utility skill. Point it at any BMad skill folder and it produces a `SKILL.md`, an `INSTRUCTIONS.md`, and any required data files, with persona inheritance from the owning agent.
 
-## Docs
+## What's in this folder
+
+This folder is the **source** for the shelf, packaged into ZIPs and attached to GitHub Releases. End users do not install from here. If you are a contributor working on a bundle, the bundle directories and `bundles.json` are the files you edit; the [release packager](../tools/bundle-web-bundles.js) zips them and updates the release.
+
+## Concept docs
 
-- [What web bundles are and when to use them](https://docs.bmad-method.org/explanation/web-bundles/)
-- [How to install a web bundle](https://docs.bmad-method.org/how-to/use-web-bundles/)
+[What web bundles are and when to use them](https://docs.bmad-method.org/explanation/web-bundles/).

package/web-bundles/bundles.json

@@ -0,0 +1,139 @@
+{
+  "schemaVersion": "1.0",
+  "releaseTag": "web-bundles-v1.0.0",
+  "releasedAt": "2026-05-25",
+  "bundles": [
+    {
+      "slug": "brainstorming-coach",
+      "name": "Brainstorming Coach",
+      "tagline": "60 ideation techniques across 10 categories — from SCAMPER to Zombie Apocalypse Planning",
+      "description": "Sixty proven brainstorming techniques spanning structured frameworks (SCAMPER, Five Whys, First Principles), wild plays (Drunk History Retelling, Zombie Apocalypse Planning), biomimetic prompts (Nature's Solutions), introspective work (Shadow Work Mining, Values Archaeology), and quantum-flavored framings (Superposition Collapse). Pick a route — browse the library, get a recommendation, take a random surprise, or run a progressive divergence-to-action flow. The coach asks; you generate every idea. Targets ~100 ideas before organizing (the breakthroughs live past idea 20), then promotes the session into themes, a 2×2 prioritization, and a breakthrough collage in Canvas.",
+      "defaultPersona": {
+        "name": "Carson",
+        "title": "Elite Brainstorming Specialist",
+        "lineage": "Osborn lineage"
+      },
+      "swapPersona": {
+        "name": "Mary",
+        "title": "Strategic Business Analyst",
+        "lineage": "BMad analyst — research-first rigor"
+      },
+      "accentColor": "#3b82f6",
+      "motif": "constellation",
+      "knowledgeFiles": ["SKILL.md", "brain-methods.csv"],
+      "needsWebBrowsing": true,
+      "needsDeepResearch": false,
+      "stitchIntegration": false
+    },
+    {
+      "slug": "product-brief-coach",
+      "name": "Product Brief Coach",
+      "tagline": "Three modes (Create / Update / Validate), two paths (Fast / Coaching), one brief you're proud of",
+      "description": "Create a brief drawn out through real conversation. Update an existing brief against a change signal. Or Validate — honest critique against the brief's own purpose. Two working modes: Fast path batches the gaps into one or two consolidated questions and tags assumptions for you to fix in review (best for pitching tomorrow); Coaching path walks section by section, mirrors before pushing, names the assumption hiding under your confident sentence (best for the brief you want to be proud of). The coach refuses to invent moats, traction, or differentiation you didn't give it. Depth that doesn't fit the brief lands in an Addendum so nothing valuable gets lost. Length is whatever the product earns.",
+      "defaultPersona": {
+        "name": "Mary",
+        "title": "Strategic Business Analyst",
+        "lineage": "BMad analyst"
+      },
+      "swapPersona": {
+        "name": "Iris",
+        "title": "Senior Product Strategist",
+        "lineage": "Mirror-then-push, unhurried thinking-partner voice"
+      },
+      "accentColor": "#d4a853",
+      "motif": "single-page",
+      "knowledgeFiles": ["SKILL.md"],
+      "needsWebBrowsing": true,
+      "needsDeepResearch": false,
+      "stitchIntegration": false
+    },
+    {
+      "slug": "prfaq-coach",
+      "name": "PRFAQ Coach",
+      "tagline": "Amazon's Working Backwards as a forcing function — write the press release before you build",
+      "description": "Four stages of customer-first pressure: Ignition (specific customer, concrete problem, real stakes), Press Release (9 sections, each forcing a different clarity — headline, problem paragraph, solution paragraph, leader quote, customer quote, getting started), Customer FAQ (validate the value proposition from outside in), and Internal FAQ + Verdict (feasibility, trade-offs, what survived). Hardcore mode: weasel words like 'best-in-class', 'seamless', and 'revolutionary' get challenged on sight; if you lead with technology, the coach redirects to the customer's actual problem. Generates a hero image for the press release. Works for commercial products, internal tools, open source, and community initiatives — the structure stays, the language adapts.",
+      "defaultPersona": {
+        "name": "Mary",
+        "title": "Strategic Business Analyst",
+        "lineage": "BMad analyst"
+      },
+      "swapPersona": {
+        "name": "Bezos",
+        "title": "Working Backwards Coach",
+        "lineage": "Amazon discipline — direct, dry, customer-first"
+      },
+      "accentColor": "#dc2626",
+      "motif": "document-ribbon",
+      "knowledgeFiles": ["SKILL.md"],
+      "needsWebBrowsing": true,
+      "needsDeepResearch": false,
+      "stitchIntegration": false
+    },
+    {
+      "slug": "prd-coach",
+      "name": "PRD Coach",
+      "tagline": "PRD coaching with built-in validation — capabilities in the PRD, mechanism in the Addendum",
+      "description": "Three modes (Create / Update / Validate), two entry points (Vision + Features for enterprise and dev products, Journey-led for consumer and UX-heavy products). Captures named-protagonist user journeys ('Mary, mom of three, kids finally asleep') instead of abstract personas. Enforces glossary discipline: every domain noun defined once, used verbatim across FRs, UJs, and SMs. Maintains stable IDs (FR-1..N globally, success metrics paired with counter-metrics SM-C1..N). The 7-dimension validation rubric grades decision-readiness, substance over theater, strategic coherence, done-ness clarity, scope honesty, downstream usability, and shape fit, with each finding cited to a specific PRD location. Length scales with stakes — hobby PRDs hit two pages; launch PRDs run as long as the FRs require.",
+      "defaultPersona": {
+        "name": "John",
+        "title": "Product Manager",
+        "lineage": "BMad PM — Cagan lineage"
+      },
+      "swapPersona": {
+        "name": "Ezra",
+        "title": "Principal Product Manager",
+        "lineage": "Calmer, slower-tempo coaching"
+      },
+      "accentColor": "#6366f1",
+      "motif": "section-stack",
+      "knowledgeFiles": ["SKILL.md", "prd-template.md", "prd-validation-checklist.md"],
+      "needsWebBrowsing": true,
+      "needsDeepResearch": false,
+      "stitchIntegration": false
+    },
+    {
+      "slug": "ux-coach",
+      "name": "UX Coach",
+      "tagline": "Two spines engineering can build from — DESIGN.md + EXPERIENCE.md as the contract",
+      "description": "Don Norman's human-centered design as the operating method. The coach elicits your vision and never imposes its own — no colors, fonts, or layouts you didn't put on the table. Captures named-protagonist journeys ('Mary on her couch after the kids are asleep') as the unit of design thinking. Produces two spines: DESIGN.md for visual identity (tokens in YAML frontmatter), EXPERIENCE.md for information architecture, behavior, states, and accessibility. Spines win on conflict with any mock, wireframe, or Stitch output. Surface closure is the test: every stated need has a surface, every surface has a journey. Pairs with Google Stitch — the handoff produces a Stitch prompt you copy straight from Canvas to generate editable mockups.",
+      "defaultPersona": {
+        "name": "Sally",
+        "title": "UX Designer",
+        "lineage": "BMad UX designer"
+      },
+      "swapPersona": {
+        "name": "Kenji",
+        "title": "Principal Product Designer",
+        "lineage": "Rams restraint + Zhuo systems discipline"
+      },
+      "accentColor": "#10b981",
+      "motif": "nested-layers",
+      "knowledgeFiles": ["SKILL.md", "ux-validation.md"],
+      "needsWebBrowsing": true,
+      "needsDeepResearch": false,
+      "stitchIntegration": true
+    },
+    {
+      "slug": "market-and-industry-research",
+      "name": "Market & Industry Research",
+      "tagline": "Deep Research wrapped in a sharp brief — research as input to a decision, not a deliverable",
+      "description": "Built around platform Deep Research mode. The coach handles the conversation: scopes what you actually need, drafts a sharp Deep Research brief you copy directly into Gemini or ChatGPT, then ingests the report and shapes the deliverable around your decision or learning goal. Methodology anchors when they help: Michael Porter for competitive structure, Clayton Christensen for Jobs-to-be-Done. Six sections to mix and match — market dynamics, customer insights, competitive landscape, regulatory & compliance, technical & technology trends, strategic synthesis. Validates every numeric, regulatory, or competitive claim against a source and a date. Generic findings ('the market is growing') get pushed back to specifics ('which segment, what rate, citing whom'). The deliverable is the synthesis against your decision, not the research dump.",
+      "defaultPersona": {
+        "name": "Mary",
+        "title": "Strategic Business Analyst",
+        "lineage": "BMad analyst"
+      },
+      "swapPersona": {
+        "name": "Geoff",
+        "title": "Market Strategist",
+        "lineage": "Geoffrey Moore + April Dunford lineage"
+      },
+      "accentColor": "#f59e0b",
+      "motif": "positioning-rings",
+      "knowledgeFiles": ["SKILL.md"],
+      "needsWebBrowsing": true,
+      "needsDeepResearch": true,
+      "stitchIntegration": false
+    }
+  ]
+}