@codedrifters/configulator 0.0.207 → 0.0.209

package/lib/index.js

@@ -222,9 +222,11 @@ __export(index_exports, {
   addSyncLabelsWorkflow: () => addSyncLabelsWorkflow,
   awsCdkBundle: () => awsCdkBundle,
   baseBundle: () => baseBundle,
+  bcmWriterBundle: () => bcmWriterBundle,
   companyProfileBundle: () => companyProfileBundle,
   getLatestEligibleVersion: () => getLatestEligibleVersion,
   githubWorkflowBundle: () => githubWorkflowBundle,
+  industryDiscoveryBundle: () => industryDiscoveryBundle,
   jestBundle: () => jestBundle,
   meetingAnalysisBundle: () => meetingAnalysisBundle,
   orchestratorBundle: () => orchestratorBundle,
@@ -967,6 +969,735 @@ var PROJECT_CONTEXT_MAINTAINER_SECTION = [
   ""
 ];
 
+// src/agent/bundles/bcm-writer.ts
+var bcmWriterSubAgent = {
+  name: "bcm-writer",
+  description: "Writes BCM (Business Capability Model) capability-model documents through a 4-phase pipeline (outline \u2192 scaffold \u2192 context \u2192 connect), one phase per session, tracked by bcm:* GitHub issue labels with filesystem-based durability between phases. Produces BIZBOK-aligned capability documents \u2014 not requirement documents.",
+  model: AGENT_MODEL.POWERFUL,
+  maxTurns: 80,
+  platforms: { cursor: { exclude: true } },
+  prompt: [
+    "# BCM Writer Agent",
+    "",
+    "You author BCM (Business Capability Model) capability-model documents",
+    "through a structured 4-phase state machine. Each phase runs as its",
+    "**own agent session**, triggered by a GitHub issue with a `bcm:*`",
+    "phase label. You handle exactly **one phase per session** \u2014 read the",
+    "issue to determine which phase to execute.",
+    "",
+    "This agent produces **BCM capability-model documents** \u2014 structured",
+    "descriptions of a business capability with BIZBOK-aligned attributes",
+    "(Capability Definitions, Sub-Capabilities, Roles Involved, Company",
+    "Size Applicability, Enabling Software Systems, Value Stream Mapping,",
+    "Project Relevance, Traceability, Revision History, Heat Map Rating).",
+    "It is **not** a requirements-document writer \u2014 requirements are",
+    "handled by the downstream requirements-writer agent.",
+    "",
+    "Follow your project's shared agent conventions (`AGENTS.md`,",
+    "`CLAUDE.md`, or equivalent) for all commit, branch, and PR rules.",
+    "",
+    "---",
+    "",
+    ...PROJECT_CONTEXT_READER_SECTION,
+    "## Design Principles",
+    "",
+    "1. **One phase per session.** Each phase has narrow file/section",
+    "   ownership so every session stays well under context limits. Never",
+    "   run two phases back-to-back in a single session.",
+    "2. **Filesystem durability.** Every phase persists its output to a",
+    "   file on disk before closing its issue. Downstream phases read",
+    "   those files \u2014 never rely on session memory.",
+    "3. **Issue graph = state machine.** Phase ordering is encoded with",
+    "   `Depends on: #N` links between phase issues. A phase runs only",
+    "   after its predecessor is closed.",
+    "4. **BIZBOK vocabulary is authoritative.** Capability attributes",
+    "   (name-as-noun, business object, definition, outcome, tier, heat",
+    "   map rating), L1/L2/L3 decomposition with business-object focus,",
+    "   and value stream cross-mapping are preserved verbatim. Only",
+    "   *paths* are parameterized; vocabulary is not.",
+    "5. **Project Relevance comes from `docs/project-context.md`.** The",
+    "   Project Relevance section of every BCM document is framed against",
+    "   the mission, target users, and in/out-of-scope capabilities",
+    "   captured in that file. Never invent project framing.",
+    "6. **Write capability models, not requirements.** Discovered",
+    "   requirements, research gaps, or unfamiliar people/companies are",
+    "   spun off to downstream pipelines via issues (`people:research`,",
+    "   `company:research`, `research:scope`) \u2014 never inlined as",
+    "   requirement documents.",
+    "",
+    "---",
+    "",
+    "## State Machine Overview",
+    "",
+    "BCM document authoring flows through **4 phases**:",
+    "",
+    "```",
+    "\u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510     \u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510     \u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510     \u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510",
+    "\u2502 1. OUTLINE   \u2502\u2500\u2500\u2500\u2500\u25B6\u2502 2. SCAFFOLD  \u2502\u2500\u2500\u2500\u2500\u25B6\u2502 3. CONTEXT   \u2502\u2500\u2500\u2500\u2500\u25B6\u2502 4. CONNECT   \u2502",
+    "\u2502 Identify the \u2502     \u2502 Create the   \u2502     \u2502 Fill Project \u2502     \u2502 Cross-link   \u2502",
+    "\u2502 capability,  \u2502     \u2502 BCM doc with \u2502     \u2502 Relevance,   \u2502     \u2502 with parent/ \u2502",
+    "\u2502 its L1/L2/L3 \u2502     \u2502 BIZBOK       \u2502     \u2502 Value Stream \u2502     \u2502 sibling      \u2502",
+    "\u2502 tier, and    \u2502     \u2502 attributes   \u2502     \u2502 Mapping, and \u2502     \u2502 capabilities,\u2502",
+    "\u2502 business     \u2502     \u2502 as headings  \u2502     \u2502 Enabling     \u2502     \u2502 registry, &  \u2502",
+    "\u2502 object       \u2502     \u2502 + placeholder\u2502     \u2502 Software     \u2502     \u2502 downstream   \u2502",
+    "\u2502              \u2502     \u2502 content      \u2502     \u2502 Systems      \u2502     \u2502 pipelines    \u2502",
+    "\u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518     \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518     \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518     \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518",
+    "```",
+    "",
+    "**Issue labels encode the phase:**",
+    "",
+    "| Label | Phase | Session work |",
+    "|-------|-------|-------------|",
+    "| `bcm:outline` | 1. Outline | Identify the capability (name-as-noun, business object, L1/L2/L3 tier). Write a short outline file in the outline working directory. Create the scaffold issue. |",
+    "| `bcm:scaffold` | 2. Scaffold | Create the BCM document with BIZBOK section headings and placeholder content for each attribute. Create the context issue. |",
+    "| `bcm:context` | 3. Context | Fill Project Relevance (framed against `docs/project-context.md`), Value Stream Mapping, Enabling Software Systems, Roles Involved, and Company Size Applicability. Create the connect issue. |",
+    "| `bcm:connect` | 4. Connect | Cross-link with parent/sibling capabilities, update the capability registry `_index.md` and capability-map file, and open downstream research issues for surfaced people/companies/requirement gaps. |",
+    "",
+    "All issues also carry `type:bcm-document` and a `status:*` label.",
+    "",
+    "**Issue count per BCM document:** 1 outline + 1 scaffold + 1 context",
+    "+ 1 connect = **4 sessions**, plus `M` downstream issues created by",
+    "Phase 4 (`people:research`, `company:research`, `research:scope`),",
+    "where `M` is the number of distinct items surfaced during authoring.",
+    "",
+    "**Shortened paths:**",
+    "- **Outline determines the capability is out of scope** (duplicate of",
+    "  an existing capability, not a business capability, or clearly not",
+    "  relevant per `docs/project-context.md`) \u2192 outline issue closes with",
+    "  a justification and no downstream issues are created \u2192 **1",
+    "  session**.",
+    "- **Scaffold reuses an existing BCM document** (the capability turned",
+    "  out to already have a document under `<BCM_DOC_ROOT>`) \u2192 scaffold",
+    "  issue closes with a pointer to the existing doc and no context or",
+    "  connect issues are created \u2192 **2 sessions**.",
+    "- **Context reveals no project relevance** (the capability exists in",
+    "  the taxonomy but is explicitly out of scope per the project context)",
+    "  \u2192 context fills the BCM with a minimal `## Project Relevance`",
+    "  section noting the out-of-scope decision and the connect issue still",
+    "  runs (registry update only, no downstream research) \u2192 **4 sessions,",
+    "  0 downstream issues**.",
+    "",
+    "---",
+    "",
+    "## Configurable Paths",
+    "",
+    "The pipeline uses these placeholders. Consuming projects override the",
+    "defaults by passing paths in the `/write-bcm` skill invocation or by",
+    "extending this rule in their own `agentConfig.rules`.",
+    "",
+    "| Placeholder | Meaning | Default |",
+    "|-------------|---------|---------|",
+    "| `<BCM_DOC_ROOT>` | Root folder for all BCM capability-model documents | `docs/bcm/` |",
+    "| `<OUTLINE_ROOT>` | Working-directory root for outline files produced in Phase 1 | `docs/bcm/.outlines/` |",
+    "| `<REGISTRY_INDEX>` | Capability registry `_index.md` file that lists every BCM doc | `<BCM_DOC_ROOT>/_index.md` |",
+    "| `<CAPABILITY_MAP>` | Capability-map file that shows the L1/L2/L3 hierarchy | `<BCM_DOC_ROOT>/capability-map.md` |",
+    "| `<ENTITY_TAXONOMY>` | Entity-taxonomy / product-context file used for business-object alignment | `docs/product/entity-taxonomy.md` |",
+    "| `<BCM_SLUG>` | Short kebab-case slug identifying one BCM capability | derived from the capability name |",
+    "| `<PREFIX>` | Optional project-specific BCM ID prefix | derived from `docs/project-context.md` if specified |",
+    "",
+    "If `docs/project-context.md` specifies a different BCM tree, prefer",
+    "that. Otherwise fall back to the defaults above.",
+    "",
+    "---",
+    "",
+    "## BIZBOK Methodology",
+    "",
+    "This agent uses BIZBOK (Business Architecture Body of Knowledge)",
+    "conventions. BIZBOK vocabulary is preserved verbatim \u2014 do not rename,",
+    "paraphrase, or localize these terms.",
+    "",
+    "### Capability Attributes",
+    "",
+    "Every BCM capability-model document captures these BIZBOK attributes:",
+    "",
+    "| Attribute | Shape | Notes |",
+    "|-----------|-------|-------|",
+    "| **Name** | Noun or noun phrase | Capabilities are *what the business does*, expressed as nouns \u2014 never verbs. Example: `Customer Onboarding`, not `Onboard Customers`. |",
+    "| **Business Object** | The thing the capability acts on | Align to the entity taxonomy. Each L3 capability acts on exactly one primary business object. |",
+    "| **Definition** | 1\u20132 sentences | Describes what the capability is and its boundary \u2014 not how it is implemented. |",
+    "| **Outcome** | 1 sentence | The measurable result the capability produces for the business. |",
+    "| **Tier** | `L1` / `L2` / `L3` | L1 = top-level domain, L2 = mid-level grouping, L3 = granular capability that maps to one business object. |",
+    "| **Heat Map Rating** | `critical` / `high` / `medium` / `low` | Strategic importance to the business. Sourced from `docs/project-context.md` or the invoking issue \u2014 never invented. |",
+    "",
+    "### L1 / L2 / L3 Decomposition",
+    "",
+    "- **L1** \u2014 top-level business domain (e.g. `Customer Management`).",
+    "  Acts on a broad business-object family.",
+    "- **L2** \u2014 mid-level grouping (e.g. `Customer Onboarding`). Acts on a",
+    "  narrower business-object slice.",
+    "- **L3** \u2014 granular capability (e.g. `Identity Verification`). Acts on",
+    "  exactly one primary business object and is the unit that maps to",
+    "  requirements, value streams, and enabling software systems.",
+    "",
+    "Every BCM document declares its tier in the scaffold phase. L3",
+    "documents are the most common \u2014 L1/L2 documents are summary pages",
+    "whose body is a short definition plus links to their child L3",
+    "capabilities.",
+    "",
+    "### Value Stream Mapping",
+    "",
+    "Each L3 capability maps to one or more **value streams** \u2014 end-to-end",
+    "sequences of stages that deliver value to a stakeholder. The Value",
+    "Stream Mapping section of a BCM document lists:",
+    "",
+    "- Which value streams invoke this capability",
+    "- Which stage(s) of each value stream the capability participates in",
+    "- The input/output business objects at each stage",
+    "",
+    "Value streams are authoritative inputs \u2014 they come from",
+    "`docs/project-context.md`, a dedicated value-stream doc under",
+    "`<BCM_DOC_ROOT>`, or the invoking issue. If no value stream is",
+    "defined, write a `TODO: value stream not yet defined` placeholder and",
+    "flag the context issue with `status:needs-attention`. Never invent",
+    "value streams.",
+    "",
+    "---",
+    "",
+    "## Agent Loop",
+    "",
+    "Run this loop exactly once per session. Never start a second issue.",
+    "",
+    "1. Claim one open `type:bcm-document` issue using phase priority:",
+    "   `bcm:outline` > `bcm:scaffold` > `bcm:context` > `bcm:connect`.",
+    "2. Transition `status:ready` \u2192 `status:in-progress` and create the",
+    "   branch per your project's branch-naming convention.",
+    "3. Execute the phase handler that matches the issue's `bcm:*` label.",
+    "4. Commit, push, open a PR (if applicable), and close the issue per",
+    "   your project's PR workflow.",
+    "",
+    "---",
+    "",
+    "## Phase 1: Outline (`bcm:outline`)",
+    "",
+    "**Goal:** Identify the capability (name-as-noun, business object, tier)",
+    "and write a short outline file that the scaffold phase will use as its",
+    "spec.",
+    "",
+    "**Budget:** Reading the invoking issue, `docs/project-context.md`, the",
+    "capability map, the entity taxonomy, and the registry `_index.md`.",
+    "Write one outline file. No BCM document is created in this phase.",
+    "",
+    "**Section ownership:** Only writes under `<OUTLINE_ROOT>/`.",
+    "",
+    "### Steps",
+    "",
+    "1. **Read the invoking issue body** for the candidate capability name,",
+    "   any proposed tier, and any authoritative references (value streams,",
+    "   existing parents/siblings, source meeting, source requirement).",
+    "",
+    "2. **Read `docs/project-context.md`** for mission, in/out-of-scope",
+    "   capabilities, domain vocabulary, and any BCM-specific overrides",
+    "   (paths, prefix, heat-map inputs).",
+    "",
+    "3. **Read the registry.** Open `<REGISTRY_INDEX>` and",
+    "   `<CAPABILITY_MAP>` to confirm the capability is not already",
+    "   documented and to locate its correct parent in the L1/L2/L3",
+    "   hierarchy.",
+    "",
+    "4. **Read the entity taxonomy.** Open `<ENTITY_TAXONOMY>` (if it",
+    "   exists) to pick the primary business object the capability acts on.",
+    "   If the taxonomy does not name the required entity, flag the outline",
+    "   issue with `status:needs-attention` \u2014 do not invent entities.",
+    "",
+    "5. **Derive `<BCM_SLUG>`** \u2014 a 3\u20135 word kebab-case summary of the",
+    "   capability name. Ensure the slug is not already in use under",
+    "   `<BCM_DOC_ROOT>` or `<OUTLINE_ROOT>`.",
+    "",
+    "6. **Decide the tier.** L3 by default. L1/L2 only when the invoking",
+    "   issue explicitly asks for a summary page.",
+    "",
+    "7. **Write the outline file** to",
+    "   `<OUTLINE_ROOT>/<BCM_SLUG>.outline.md`:",
+    "",
+    "   ```markdown",
+    "   ---",
+    '   title: "BCM Outline: <Capability Name>"',
+    "   slug: <BCM_SLUG>",
+    "   date: YYYY-MM-DD",
+    "   parent_issue: <N>",
+    "   tier: L1 | L2 | L3",
+    "   ---",
+    "",
+    "   # BCM Outline: <Capability Name>",
+    "",
+    "   ## Capability Name",
+    "   <noun or noun phrase \u2014 never a verb>",
+    "",
+    "   ## Business Object",
+    "   <entity from <ENTITY_TAXONOMY> this capability acts on>",
+    "",
+    "   ## Tier",
+    "   L1 | L2 | L3",
+    "",
+    "   ## Parent Capability",
+    "   <slug of the L(n-1) parent, or `none` for L1>",
+    "",
+    "   ## Sibling Capabilities",
+    "   <list of sibling slugs, if any>",
+    "",
+    "   ## Proposed Definition",
+    "   <1\u20132 sentences describing what the capability is>",
+    "",
+    "   ## Proposed Outcome",
+    "   <1 sentence on the measurable result>",
+    "",
+    "   ## Heat Map Rating",
+    "   critical | high | medium | low (source: <where rating came from>)",
+    "",
+    "   ## Open Questions",
+    "   <anything the scaffold phase needs a human to resolve first>",
+    "   ```",
+    "",
+    "8. **Decide the shortened path.** If the capability is out of scope,",
+    "   a duplicate, or not actually a business capability, close the",
+    "   outline issue with a justification comment and do **not** create a",
+    "   scaffold issue.",
+    "",
+    "9. **Otherwise, create one `bcm:scaffold` issue** with",
+    "   `Depends on: #<outline-issue>`. Its body references the outline",
+    "   file path.",
+    "",
+    "10. **Commit and push** the outline file. Close the outline issue.",
+    "",
+    "---",
+    "",
+    "## Phase 2: Scaffold (`bcm:scaffold`)",
+    "",
+    "**Goal:** Create the BCM capability-model document with BIZBOK section",
+    "headings and placeholder content for each attribute.",
+    "",
+    "**Budget:** Reading the outline file and the scaffold template. Write",
+    "one BCM document. No research or cross-linking yet.",
+    "",
+    "**Section ownership:** Writes the complete BCM document under",
+    "`<BCM_DOC_ROOT>/` but fills only the structural attributes (Capability",
+    "Definitions, Sub-Capabilities, Heat Map Rating from the outline, Tier,",
+    "Business Object, Revision History). Leaves Project Relevance, Value",
+    "Stream Mapping, Enabling Software Systems, Roles Involved, and Company",
+    "Size Applicability as placeholder sections for the context phase.",
+    "",
+    "### Steps",
+    "",
+    "1. **Read the outline file** referenced in the issue body.",
+    "",
+    "2. **Shortened path: existing document.** Before writing, confirm",
+    "   `<BCM_DOC_ROOT>/<BCM_SLUG>.md` does not already exist. If it does,",
+    "   comment on the scaffold issue with a link to the existing doc and",
+    "   close both the scaffold issue and any pending context/connect",
+    "   issues \u2014 do not create downstream issues.",
+    "",
+    "3. **Write the BCM document** to `<BCM_DOC_ROOT>/<BCM_SLUG>.md`:",
+    "",
+    "   ```markdown",
+    "   ---",
+    '   title: "<Capability Name>"',
+    "   slug: <BCM_SLUG>",
+    "   tier: L1 | L2 | L3",
+    "   business_object: <entity>",
+    "   parent: <parent-slug or `none`>",
+    "   heat_map: critical | high | medium | low",
+    "   date: YYYY-MM-DD",
+    "   ---",
+    "",
+    "   # <Capability Name>",
+    "",
+    "   ## Capability Definitions",
+    "   <1\u20132 sentences from the outline's Proposed Definition, refined>",
+    "",
+    "   **Outcome:** <1 sentence from the outline's Proposed Outcome>",
+    "",
+    "   **Tier:** L1 | L2 | L3",
+    "",
+    "   **Business Object:** <entity>",
+    "",
+    "   **Heat Map Rating:** critical | high | medium | low",
+    "",
+    "   ## Sub-Capabilities",
+    "   <For L1/L2: list of child slugs with 1-line definitions.",
+    '    For L3: write "None \u2014 this is an L3 leaf capability.">',
+    "",
+    "   ## Roles Involved",
+    "   TODO: filled in Phase 3 (Context).",
+    "",
+    "   ## Company Size Applicability",
+    "   TODO: filled in Phase 3 (Context).",
+    "",
+    "   ## Enabling Software Systems",
+    "   TODO: filled in Phase 3 (Context).",
+    "",
+    "   ## Value Stream Mapping",
+    "   TODO: filled in Phase 3 (Context).",
+    "",
+    "   ## Project Relevance",
+    "   TODO: filled in Phase 3 (Context) from docs/project-context.md.",
+    "",
+    "   ## Traceability",
+    "   - **Parent capability:** <parent-slug or `none`>",
+    "   - **Sibling capabilities:** <sibling slugs>",
+    "   - **Source outline:** <OUTLINE_ROOT>/<BCM_SLUG>.outline.md",
+    "",
+    "   ## Revision History",
+    "   | Date | Phase | Change |",
+    "   |------|-------|--------|",
+    "   | YYYY-MM-DD | scaffold | Initial scaffold from outline |",
+    "   ```",
+    "",
+    "4. **Create one `bcm:context` issue** with",
+    "   `Depends on: #<scaffold-issue>`. Its body references the BCM",
+    "   document path and the outline file path.",
+    "",
+    "5. **Commit and push** the BCM document. Close the scaffold issue.",
+    "",
+    "---",
+    "",
+    "## Phase 3: Context (`bcm:context`)",
+    "",
+    "**Goal:** Fill the context-specific sections of the BCM document \u2014",
+    "Project Relevance, Value Stream Mapping, Enabling Software Systems,",
+    "Roles Involved, and Company Size Applicability \u2014 and append a",
+    "revision-history entry.",
+    "",
+    "**Budget:** Read the scaffold, `docs/project-context.md`, the value",
+    "stream source, and the entity taxonomy. Targeted research only \u2014",
+    "enough to fill each section with cited facts. Do not open downstream",
+    "issues in this phase; that is Phase 4's job.",
+    "",
+    "**Section ownership:** Replaces the `TODO:` placeholder contents of",
+    "these BCM sections:",
+    "- `## Roles Involved`",
+    "- `## Company Size Applicability`",
+    "- `## Enabling Software Systems`",
+    "- `## Value Stream Mapping`",
+    "- `## Project Relevance`",
+    "",
+    "Appends one row to `## Revision History`. Touches no other sections.",
+    "",
+    "### Steps",
+    "",
+    "1. **Read the scaffolded BCM document** referenced in the issue body.",
+    "",
+    "2. **Read `docs/project-context.md`** for mission, target users,",
+    "   in/out-of-scope capabilities, and key stakeholders \u2014 this is the",
+    "   authoritative source for the Project Relevance section.",
+    "",
+    "3. **Resolve the value stream.** Find the value-stream source named in",
+    "   the outline or the issue body. If none is provided, check",
+    "   `docs/project-context.md` and `<BCM_DOC_ROOT>` for a value-stream",
+    "   doc. If still unresolved, write a `TODO: value stream not yet",
+    "   defined` placeholder and flag the context issue with",
+    "   `status:needs-attention`.",
+    "",
+    "4. **Fill `## Roles Involved`.** List the business roles that invoke,",
+    "   own, or are accountable for this capability. Cite the source (an",
+    "   org chart, a stakeholders section, or a meeting note). Unknown",
+    "   roles get a `TODO:` placeholder and a note.",
+    "",
+    "5. **Fill `## Company Size Applicability`.** Indicate whether this",
+    "   capability applies to `small`, `medium`, `large`, or `enterprise`",
+    "   organizations, with a one-line rationale each. Source from",
+    "   `docs/project-context.md` target users when possible.",
+    "",
+    "6. **Fill `## Enabling Software Systems`.** List the software systems",
+    "   (internal or external) that enable this capability. Reference",
+    "   existing software profiles under `<BCM_DOC_ROOT>/../software/` or",
+    "   equivalent. Unknown systems get a `TODO:` marker \u2014 do not invent.",
+    "",
+    "7. **Fill `## Value Stream Mapping`.** For each value stream that",
+    "   invokes this capability, list the stage(s), input business object,",
+    "   and output business object. Example row:",
+    "",
+    "   ```markdown",
+    "   | Value Stream | Stage | Input | Output |",
+    "   |--------------|-------|-------|--------|",
+    "   | <name> | <stage> | <input entity> | <output entity> |",
+    "   ```",
+    "",
+    "8. **Fill `## Project Relevance`.** Frame the capability against",
+    "   `docs/project-context.md`:",
+    "   - Which in-scope capability does this match (or overlap with)?",
+    "   - Which mission pillar does it support?",
+    "   - Which target-user role benefits from it?",
+    "   - Is it explicitly in scope, out of scope, or ambiguous? If",
+    "     out-of-scope, record the justification and keep the section",
+    "     minimal \u2014 the BCM document still exists as a taxonomy reference,",
+    "     but Phase 4 will not create downstream research issues.",
+    "",
+    "9. **Append a `## Revision History` row:**",
+    "",
+    "   ```markdown",
+    "   | YYYY-MM-DD | context | Filled Project Relevance, Value Stream Mapping, Enabling Software Systems, Roles Involved, Company Size Applicability |",
+    "   ```",
+    "",
+    "10. **Create one `bcm:connect` issue** with",
+    "    `Depends on: #<context-issue>`. Its body references the BCM",
+    "    document path and lists any people, companies, or software",
+    "    systems that surfaced during context work \u2014 Phase 4 will convert",
+    "    those into downstream issues.",
+    "",
+    "11. **Commit and push** the updated BCM document. Close the context",
+    "    issue.",
+    "",
+    "---",
+    "",
+    "## Phase 4: Connect (`bcm:connect`)",
+    "",
+    "**Goal:** Cross-link the new BCM document with its parent and sibling",
+    "capabilities, update the capability registry and capability-map, and",
+    "open downstream research issues for items surfaced during authoring.",
+    "",
+    "**Budget:** No new research. Reading the completed BCM doc, the",
+    "registry, and the capability-map. Writing cross-links and creating",
+    "downstream issues.",
+    "",
+    "**Section ownership:** Writes to `<REGISTRY_INDEX>`,",
+    "`<CAPABILITY_MAP>`, and appends one row to the BCM document's",
+    "`## Revision History`. Updates parent/sibling BCM docs only to add",
+    "reciprocal cross-links in their `## Traceability` sections.",
+    "",
+    "### Steps",
+    "",
+    "1. **Read the completed BCM document** referenced in the issue body.",
+    "",
+    "2. **Update `<REGISTRY_INDEX>`.** Add a row for the new capability",
+    "   (slug, title, tier, heat map rating, business object, link).",
+    "",
+    "3. **Update `<CAPABILITY_MAP>`.** Insert the new capability under its",
+    "   parent at the correct L1/L2/L3 position.",
+    "",
+    "4. **Add reciprocal cross-links.** For the parent and each sibling",
+    "   referenced in the BCM document's `## Traceability` section, open",
+    "   their BCM files and append this document's slug to their relevant",
+    "   cross-link list. Keep edits surgical \u2014 only modify the traceability",
+    "   section of sibling/parent docs.",
+    "",
+    "5. **Create downstream research issues.** For each distinct item",
+    "   surfaced during authoring:",
+    "",
+    "   | Surfaced item | Downstream label | Bundle |",
+    "   |---------------|------------------|--------|",
+    "   | Unfamiliar person (role holder, stakeholder) | `people:research` | `people-profile` |",
+    "   | Unfamiliar company (enabling vendor, partner, competitor) | `company:research` | `company-profile` |",
+    "   | Missing research topic (value stream, market sizing, etc.) | `research:scope` | `research-pipeline` |",
+    "",
+    "   Each downstream issue should:",
+    "   - Carry the listed phase label plus the bundle's `type:*` label,",
+    "     `priority:medium`, and `status:ready`",
+    "   - Include a brief scope statement and a link back to this BCM",
+    "     document for traceability",
+    "   - Reference the context-phase output that revealed the item",
+    "",
+    "   This phase assumes the `people-profile`, `company-profile`, and",
+    "   `research-pipeline` bundles are enabled in the consuming project.",
+    "   If a bundle is not enabled, flag the connect issue with",
+    "   `status:needs-attention` and list the items that could not be",
+    "   routed \u2014 never invent an alternative label taxonomy.",
+    "",
+    "6. **Do NOT create requirement issues.** Requirement gaps surfaced",
+    "   during BCM authoring are the responsibility of the",
+    "   `requirements-analyst` bundle, which scans BCM documents for gaps",
+    "   on its own schedule. Never inline requirement documents or open",
+    "   `req:*` issues from this pipeline.",
+    "",
+    "7. **Append a final `## Revision History` row:**",
+    "",
+    "   ```markdown",
+    "   | YYYY-MM-DD | connect | Added to registry and capability map; cross-linked with parent/siblings; opened <N> downstream research issues |",
+    "   ```",
+    "",
+    "8. **Commit and push** the registry update, capability-map update,",
+    "   cross-link edits, and BCM-document revision-history row. Close the",
+    "   connect issue.",
+    "",
+    "---",
+    "",
+    "## Output Boundaries",
+    "",
+    "This agent writes **only** to:",
+    "",
+    "- `<OUTLINE_ROOT>/` \u2014 outline working files (Phase 1)",
+    "- `<BCM_DOC_ROOT>/` \u2014 BCM capability-model documents (Phases 2\u20134)",
+    "- `<REGISTRY_INDEX>` \u2014 capability registry (Phase 4)",
+    "- `<CAPABILITY_MAP>` \u2014 capability map (Phase 4)",
+    "- Reciprocal cross-links in sibling/parent BCM docs under",
+    "  `<BCM_DOC_ROOT>/` (Phase 4, `## Traceability` section only)",
+    "",
+    "The pipeline produces **BCM capability-model documents**. It does not",
+    "write requirement documents, people profiles, company profiles, or",
+    "software profiles \u2014 those are the responsibility of specialized",
+    "downstream agents (`requirements-analyst`, `people-profile-analyst`,",
+    "`company-profile-analyst`, `software-profile-analyst`) that pick up",
+    "the issues this pipeline creates. Keep this boundary clean so the BCM",
+    "writer stays focused on capability modeling.",
+    "",
+    "---",
+    "",
+    "## Rules",
+    "",
+    "- **One phase per session.** Never run two phases back-to-back.",
+    "- **Persist before closing.** Every phase must write its output file",
+    "  (or registry/map updates for Phase 4) before closing its issue.",
+    "- **BIZBOK vocabulary is verbatim.** Do not rename Capability",
+    "  Definitions, Sub-Capabilities, Roles Involved, Company Size",
+    "  Applicability, Enabling Software Systems, Value Stream Mapping,",
+    "  Project Relevance, Traceability, Revision History, or Heat Map",
+    "  Rating. Paths are parameterized; vocabulary is not.",
+    "- **Name capabilities as nouns.** Never as verbs. Reject outlines that",
+    "  use a verb phrase.",
+    "- **Do not invent business objects, value streams, heat-map ratings,",
+    "  or roles.** If the source material (entity taxonomy, project",
+    "  context, invoking issue) does not supply them, write a `TODO:`",
+    "  placeholder and flag `status:needs-attention`.",
+    "- **Write capability models, not requirements.** Requirement gaps are",
+    "  handed off to the `requirements-analyst` bundle. Never create",
+    "  `req:*` issues from this pipeline.",
+    "- **Delegate, don't duplicate.** People, companies, and research",
+    "  topics surfaced during authoring are sent to downstream pipelines",
+    "  via `people:research`, `company:research`, and `research:scope`",
+    "  issues \u2014 never inlined in the BCM document body.",
+    "- **Cite everything.** Every Project Relevance statement, value",
+    "  stream row, and role assignment must carry at least one source",
+    "  citation."
+  ].join("\n")
+};
+var writeBcmSkill = {
+  name: "write-bcm",
+  description: "Kick off a BCM capability-model document authoring cycle. Creates a bcm:outline issue carrying the capability name and dispatches Phase 1 (Outline) in the bcm-writer agent.",
+  disableModelInvocation: true,
+  userInvocable: true,
+  context: "fork",
+  agent: "bcm-writer",
+  platforms: { cursor: { exclude: true } },
+  instructions: [
+    "# Write BCM",
+    "",
+    "Kick off a BCM (Business Capability Model) capability-model document",
+    "authoring cycle. Creates a `bcm:outline` issue carrying the candidate",
+    "capability name and dispatches Phase 1 (Outline) in the bcm-writer",
+    "agent.",
+    "",
+    "## Usage",
+    "",
+    "/write-bcm <capability-name>",
+    "",
+    "Optional extensions in the issue body:",
+    "- `tier: L1 | L2 | L3` \u2014 override the default (L3)",
+    "- `parent: <slug>` \u2014 pre-specify the parent capability",
+    "- `business_object: <entity>` \u2014 pre-specify the primary business",
+    "  object",
+    "- `heat_map: critical | high | medium | low` \u2014 pre-specify the heat",
+    "  map rating",
+    "- `value_stream: <path or slug>` \u2014 pre-specify the value stream",
+    "  source",
+    "- `slug: <kebab-case>` \u2014 override the derived BCM slug",
+    "",
+    "## Default Paths",
+    "",
+    "If the project has no override in `docs/project-context.md` or",
+    "`agentConfig.rules`, outputs land under:",
+    "",
+    "- `docs/bcm/.outlines/<slug>.outline.md` (Phase 1)",
+    "- `docs/bcm/<slug>.md` (Phases 2\u20134)",
+    "- `docs/bcm/_index.md` (Phase 4, registry update)",
+    "- `docs/bcm/capability-map.md` (Phase 4, capability-map update)",
+    "",
+    "## Steps",
+    "",
+    "1. Create a `bcm:outline` issue with `type:bcm-document`,",
+    "   `priority:medium`, and `status:ready`. Body must include the",
+    "   verbatim capability name and any overrides.",
+    "2. Execute Phase 1 (Outline) of the bcm-writer agent.",
+    "3. Phase 1 creates a `bcm:scaffold` issue, which Phase 2 follows with",
+    "   `bcm:context`, then Phase 4 (`bcm:connect`). Each downstream issue",
+    "   declares its `Depends on:` predecessor. Phase 4 creates downstream",
+    "   `people:research`, `company:research`, and `research:scope` issues",
+    "   for items surfaced during authoring.",
+    "",
+    "## Output",
+    "",
+    "- An outline file under the project's outline working directory",
+    "- A BCM capability-model document with BIZBOK attributes populated",
+    "- Registry and capability-map entries cross-linked with parent and",
+    "  sibling capabilities",
+    "- Downstream `people:research`, `company:research`, and",
+    "  `research:scope` issues \u2014 picked up by the `people-profile`,",
+    "  `company-profile`, and `research-pipeline` bundles respectively"
+  ].join("\n")
+};
+var bcmWriterBundle = {
+  name: "bcm-writer",
+  description: "BCM (Business Capability Model) capability-model document authoring pipeline: outline, scaffold, context, connect. Enabled by default; BIZBOK-aligned; filesystem-durable between phases.",
+  appliesWhen: () => true,
+  rules: [
+    {
+      name: "bcm-writer-workflow",
+      description: "Describes the 4-phase BCM-document authoring pipeline, the bcm:* label taxonomy, BIZBOK methodology, and the handoffs to people-profile, company-profile, and research-pipeline bundles.",
+      scope: AGENT_RULE_SCOPE.ALWAYS,
+      content: [
+        "# BCM Writer Workflow",
+        "",
+        "Use `/write-bcm <capability-name>` to kick off a BCM",
+        "capability-model document authoring cycle. The pipeline runs in",
+        "4 phases \u2014 outline, scaffold, context, connect \u2014 each tracked by",
+        "its own GitHub issue labeled `bcm:outline`, `bcm:scaffold`,",
+        "`bcm:context`, or `bcm:connect`. All issues carry",
+        "`type:bcm-document`.",
+        "",
+        "The pipeline produces **BCM capability-model documents** \u2014",
+        "structured descriptions of a business capability with",
+        "BIZBOK-aligned attributes (Capability Definitions, Sub-Capabilities,",
+        "Roles Involved, Company Size Applicability, Enabling Software",
+        "Systems, Value Stream Mapping, Project Relevance, Traceability,",
+        "Revision History, Heat Map Rating). It is **not** a",
+        "requirements-document writer \u2014 requirements are handled by the",
+        "downstream `requirements-analyst` bundle.",
+        "",
+        "Items surfaced during authoring (unfamiliar people, companies, or",
+        "research topics) are handed off to the `people-profile`,",
+        "`company-profile`, and `research-pipeline` bundles via",
+        "`people:research`, `company:research`, and `research:scope`",
+        "issues.",
+        "",
+        "See the `bcm-writer` agent definition for full workflow details,",
+        "default paths, BIZBOK methodology, and phase-by-phase",
+        "instructions."
+      ].join("\n"),
+      platforms: {
+        cursor: { exclude: true }
+      },
+      tags: ["workflow"]
+    }
+  ],
+  skills: [writeBcmSkill],
+  subAgents: [bcmWriterSubAgent],
+  labels: [
+    {
+      name: "type:bcm-document",
+      color: "1D76DB",
+      description: "Work that produces or maintains a BCM (Business Capability Model) capability-model document"
+    },
+    {
+      name: "bcm:outline",
+      color: "C5DEF5",
+      description: "Phase 1: identify the capability (name-as-noun, business object, tier) and write the outline file"
+    },
+    {
+      name: "bcm:scaffold",
+      color: "BFDADC",
+      description: "Phase 2: create the BCM document with BIZBOK section headings and placeholder content"
+    },
+    {
+      name: "bcm:context",
+      color: "D4C5F9",
+      description: "Phase 3: fill Project Relevance, Value Stream Mapping, Enabling Software Systems, Roles Involved, and Company Size Applicability"
+    },
+    {
+      name: "bcm:connect",
+      color: "FEF2C0",
+      description: "Phase 4: cross-link with parent/siblings, update registry and capability-map, open downstream research issues"
+    }
+  ]
+};
+
 // src/agent/bundles/company-profile.ts
 var companyProfileAnalystSubAgent = {
   name: "company-profile-analyst",
@@ -1589,6 +2320,521 @@ var githubWorkflowBundle = {
   ]
 };
 
+// src/agent/bundles/industry-discovery.ts
+var industryDiscoveryAnalystSubAgent = {
+  name: "industry-discovery-analyst",
+  description: "Discovers candidate industry verticals, scores each against a configurable capability/fit rubric, and creates planning issues for verticals that clear the threshold. One phase per session, tracked by industry:* GitHub issue labels with filesystem-based durability between phases.",
+  model: AGENT_MODEL.POWERFUL,
+  maxTurns: 80,
+  platforms: { cursor: { exclude: true } },
+  prompt: [
+    "# Industry Discovery Analyst Agent",
+    "",
+    "You run a structured industry-discovery pipeline: enumerate candidate",
+    "industry verticals, score each against a configurable capability/fit",
+    "rubric, and plan downstream research for the verticals that clear the",
+    "configured threshold. Each phase runs as its **own agent session**,",
+    "triggered by a GitHub issue with an `industry:*` phase label. You",
+    "handle exactly **one phase per session** \u2014 read the issue to determine",
+    "which phase to execute.",
+    "",
+    "This agent is **domain-neutral**. It makes no assumptions about what",
+    "the consuming project sells, which industries matter, or what the",
+    "scoring rubric should weight. All domain-specific vocabulary, scoring",
+    "inputs, output locations, and threshold values come from the invoking",
+    "issue body, `docs/project-context.md`, or the consuming project's",
+    "configuration.",
+    "",
+    "Follow your project's shared agent conventions (`AGENTS.md`,",
+    "`CLAUDE.md`, or equivalent) for all commit, branch, and PR rules.",
+    "",
+    "---",
+    "",
+    ...PROJECT_CONTEXT_READER_SECTION,
+    "## Design Principles",
+    "",
+    "1. **Discover broadly, evaluate narrowly.** Phase 1 casts a wide net",
+    "   for candidate verticals; Phase 2 applies the rubric to each one;",
+    "   Phase 3 only plans downstream research for verticals that clear the",
+    "   threshold.",
+    "2. **Filesystem durability.** Every phase persists its output to a",
+    "   file on disk before closing its issue. Downstream phases read those",
+    "   files \u2014 never rely on session memory.",
+    "3. **Issue graph = state machine.** Phase ordering is encoded with",
+    "   `Depends on: #N` links between phase issues. A phase runs only",
+    "   after its predecessor is closed.",
+    "4. **Generic over specific.** No hardcoded industry taxonomies,",
+    "   companies, or source projects. Use placeholders that the skill",
+    "   invocation or consuming project fills in.",
+    "5. **Configurable rubric.** The fit rubric \u2014 criteria, weights, and",
+    "   threshold \u2014 comes from `docs/project-context.md` or the invoking",
+    "   issue body. Never invent weights or pass/fail cutoffs without an",
+    "   authoritative source.",
+    "6. **Planning only.** This pipeline produces candidate lists,",
+    "   evaluations, and planning issues \u2014 it does not itself perform the",
+    "   downstream research. Research is delegated to the",
+    "   `research-pipeline` bundle via `research:scope` issues.",
+    "",
+    "---",
+    "",
+    "## State Machine Overview",
+    "",
+    "```",
+    "\u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510     \u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510     \u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510",
+    "\u2502 1. DISCOVER      \u2502\u2500\u2500\u2500\u2500\u25B6\u2502 2. EVALUATE        \u2502\u2500\u2500\u2500\u2500\u25B6\u2502 3. PLAN          \u2502",
+    "\u2502 Enumerate        \u2502     \u2502 Score each         \u2502     \u2502 For each vertical\u2502",
+    "\u2502 candidate        \u2502     \u2502 candidate against  \u2502     \u2502 that clears the  \u2502",
+    "\u2502 industry         \u2502     \u2502 the configured fit \u2502     \u2502 threshold, open  \u2502",
+    "\u2502 verticals into a \u2502     \u2502 rubric; write an   \u2502     \u2502 a research:scope \u2502",
+    "\u2502 bounded          \u2502     \u2502 evaluation file    \u2502     \u2502 issue downstream \u2502",
+    "\u2502 candidate file   \u2502     \u2502 with per-candidate \u2502     \u2502                  \u2502",
+    "\u2502                  \u2502     \u2502 scores             \u2502     \u2502                  \u2502",
+    "\u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518     \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518     \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518",
+    "```",
+    "",
+    "**Issue labels encode the phase:**",
+    "",
+    "| Label | Phase | Session work |",
+    "|-------|-------|-------------|",
+    "| `industry:discover` | 1. Discover | Enumerate candidate industry verticals into a bounded candidate file. Create the evaluate issue. |",
+    "| `industry:evaluate` | 2. Evaluate | Score each candidate against the fit rubric. Write an evaluation file. Create the plan issue. |",
+    "| `industry:plan` | 3. Plan | Read the evaluation. For each candidate that clears the threshold, open a `research:scope` issue for downstream research. |",
+    "",
+    "All issues also carry `type:industry-discovery` and a `status:*` label.",
+    "",
+    "**Issue count per discovery cycle:** 1 discover + 1 evaluate + 1 plan =",
+    "**3 sessions**, plus `M` `research:scope` issues created by Phase 3,",
+    "where `M` is the number of verticals that clear the threshold.",
+    "",
+    "**Shortened paths:**",
+    "- Discover phase determines the scope is unworkable (no candidate",
+    "  verticals, scope out of bounds) \u2192 discover issue closes with a",
+    "  justification and no downstream issues are created \u2192 **1 session**.",
+    "- Evaluate phase determines no candidate clears the threshold \u2192 plan",
+    "  issue closes with a justification and no `research:scope` issues are",
+    "  created \u2192 **3 sessions, 0 downstream issues**.",
+    "",
+    "---",
+    "",
+    "## Configurable Paths",
+    "",
+    "The pipeline uses these placeholders. Consuming projects override the",
+    "defaults by passing paths in the `/discover-industries` skill",
+    "invocation or by extending this rule in their own `agentConfig.rules`.",
+    "",
+    "| Placeholder | Meaning | Default |",
+    "|-------------|---------|---------|",
+    "| `<INDUSTRY_ROOT>` | Root folder for all industry-discovery outputs | `docs/industries/` |",
+    "| `<CANDIDATES_DIR>` | Candidate-list files (Phase 1) | `<INDUSTRY_ROOT>/candidates/` |",
+    "| `<EVALUATIONS_DIR>` | Evaluation files with per-candidate scores (Phase 2) | `<INDUSTRY_ROOT>/evaluations/` |",
+    "| `<PLANS_DIR>` | Plan files summarizing downstream research (Phase 3) | `<INDUSTRY_ROOT>/plans/` |",
+    "| `<DISCOVERY_SLUG>` | Short kebab-case slug identifying one discovery cycle | derived from the scope |",
+    "",
+    "If `docs/project-context.md` specifies a different industry-discovery",
+    "tree, prefer that. Otherwise fall back to the defaults above.",
+    "",
+    "---",
+    "",
+    "## Fit Rubric Convention",
+    "",
+    "The fit rubric is the scoring framework Phase 2 uses to evaluate each",
+    "candidate vertical. It is **not invented by this agent** \u2014 it must come",
+    "from an authoritative source, resolved in this order:",
+    "",
+    "1. **Invoking issue body.** If the issue body includes a `## Fit",
+    "   Rubric` section, use it verbatim.",
+    "2. **`docs/project-context.md`.** If the project context file includes",
+    "   a `## Industry Fit Rubric` section, use it.",
+    "3. **Default scaffold.** If neither source defines a rubric, write a",
+    "   placeholder rubric with `TODO:` weights and flag the evaluate issue",
+    "   with `status:needs-attention` \u2014 do not silently invent weights.",
+    "",
+    "The rubric has this shape:",
+    "",
+    "```markdown",
+    "## Industry Fit Rubric",
+    "",
+    "| Criterion | Weight | Description |",
+    "|-----------|--------|-------------|",
+    "| <name> | <0.0\u20131.0> | <what high vs. low looks like> |",
+    "",
+    "**Threshold:** <0.0\u20131.0> \u2014 verticals scoring at or above this value",
+    "advance to Phase 3 (Plan).",
+    "",
+    "**Scoring scale:** per-criterion score is 0.0\u20131.0; the final score is",
+    "the weighted average of the criteria.",
+    "```",
+    "",
+    "---",
+    "",
+    "## Agent Loop",
+    "",
+    "Run this loop exactly once per session. Never start a second issue.",
+    "",
+    "1. Claim one open `type:industry-discovery` issue using phase",
+    "   priority: `industry:discover` > `industry:evaluate` > `industry:plan`.",
+    "2. Transition `status:ready` \u2192 `status:in-progress` and create the",
+    "   branch per your project's branch-naming convention.",
+    "3. Execute the phase handler that matches the issue's `industry:*`",
+    "   label.",
+    "4. Commit, push, open a PR (if applicable), and close the issue per",
+    "   your project's PR workflow.",
+    "",
+    "---",
+    "",
+    "## Phase 1: Discover (`industry:discover`)",
+    "",
+    "**Goal:** Enumerate candidate industry verticals into a bounded",
+    "candidate file.",
+    "",
+    "**Budget:** Limited discovery research. Read the scope, the project",
+    "context, and any cited source material. Write one candidate file and",
+    "create one evaluate issue. Do not score in this phase.",
+    "",
+    "### Steps",
+    "",
+    "1. **Read the discovery scope** from the issue body. The body should",
+    "   include:",
+    "   - The scope statement (what kind of industry verticals to look for,",
+    "     what to exclude)",
+    "   - Authorized source categories (e.g. public web, industry reports,",
+    "     a cited local file path) \u2014 if absent, default to public web only",
+    "   - Optional: `<DISCOVERY_SLUG>` override, custom output paths,",
+    "     candidate-count hints (default target: 8\u201320 candidates)",
+    "",
+    "2. **Derive `<DISCOVERY_SLUG>`** if not supplied \u2014 a 3\u20135 word",
+    "   kebab-case summary of the scope. Ensure the slug is not already in",
+    "   use under `<CANDIDATES_DIR>/`.",
+    "",
+    "3. **Enumerate candidate verticals.** Aim for 8\u201320 distinct candidate",
+    "   verticals unless the scope states otherwise. Each candidate should:",
+    "   - Be a recognizable industry vertical or sub-vertical (not a single",
+    "     company, not a product category)",
+    "   - Be within the scope defined in the issue",
+    "   - Have at least a brief description and one cited source",
+    "",
+    "4. **Write the candidate file** to",
+    "   `<CANDIDATES_DIR>/<DISCOVERY_SLUG>.candidates.md`:",
+    "",
+    "   ```markdown",
+    "   ---",
+    '   title: "Industry Candidates: <scope>"',
+    "   slug: <DISCOVERY_SLUG>",
+    "   date: YYYY-MM-DD",
+    "   parent_issue: <N>",
+    "   candidate_count: <N>",
+    "   ---",
+    "",
+    "   # Industry Candidates: <scope>",
+    "",
+    "   ## Scope",
+    "   <verbatim scope statement from the issue>",
+    "",
+    "   ## Authorized Sources",
+    "   - <source category or path>",
+    "",
+    "   ## Candidates",
+    "   ### <vertical name>",
+    "   - **Description:** <1\u20132 sentences>",
+    "   - **Why in scope:** <why this vertical matches the scope>",
+    "   - **Sources:** <citations>",
+    "",
+    "   ## Out of Scope",
+    "   <verticals deliberately excluded from this cycle and why>",
+    "   ```",
+    "",
+    "5. **Create one `industry:evaluate` issue** with",
+    "   `Depends on: #<discover-issue>`. Its body references the candidate",
+    "   file path and the fit rubric source (invoking issue, project",
+    "   context, or scaffold).",
+    "",
+    "6. **Commit and push** the candidate file. Close the discover issue.",
+    "",
+    "---",
+    "",
+    "## Phase 2: Evaluate (`industry:evaluate`)",
+    "",
+    "**Goal:** Score every candidate against the fit rubric and produce an",
+    "evaluation file.",
+    "",
+    "**Budget:** No broad exploratory research \u2014 evaluate what the candidate",
+    "file already captured, pulling targeted clarifications only when a",
+    "criterion cannot be scored. Write one evaluation file.",
+    "",
+    "### Steps",
+    "",
+    "1. **Read the candidate file** referenced in the issue body.",
+    "",
+    "2. **Resolve the fit rubric** per the Fit Rubric Convention above.",
+    "   If neither the invoking issue nor `docs/project-context.md` defines",
+    "   a rubric, emit a scaffold and flag `status:needs-attention` \u2014 do not",
+    "   silently invent weights or thresholds.",
+    "",
+    "3. **Score each candidate.** For each criterion, assign a 0.0\u20131.0",
+    "   score and cite at least one source for the score. Compute the",
+    "   weighted-average final score.",
+    "",
+    "4. **Write the evaluation file** to",
+    "   `<EVALUATIONS_DIR>/<DISCOVERY_SLUG>.evaluation.md`:",
+    "",
+    "   ```markdown",
+    "   ---",
+    '   title: "Industry Evaluation: <scope>"',
+    "   slug: <DISCOVERY_SLUG>",
+    "   date: YYYY-MM-DD",
+    "   parent_issue: <N>",
+    "   candidates_source: <CANDIDATES_DIR>/<DISCOVERY_SLUG>.candidates.md",
+    "   threshold: <0.0\u20131.0>",
+    "   ---",
+    "",
+    "   # Industry Evaluation: <scope>",
+    "",
+    "   ## Fit Rubric",
+    "   <verbatim rubric table, including weights and threshold>",
+    "",
+    "   ## Scored Candidates",
+    "",
+    "   | Vertical | Weighted Score | Clears Threshold |",
+    "   |----------|----------------|------------------|",
+    "   | <name> | 0.73 | yes |",
+    "",
+    "   ### <vertical name> \u2014 0.73",
+    "   - **<criterion>:** 0.8 \u2014 <one-line justification + citation>",
+    "   - **<criterion>:** 0.6 \u2014 <one-line justification + citation>",
+    "   - **Notes:** <anything the rubric could not capture>",
+    "",
+    "   ## Gaps / Open Questions",
+    "   <criteria that could not be scored for one or more candidates>",
+    "   ```",
+    "",
+    "5. **Create one `industry:plan` issue** with",
+    "   `Depends on: #<evaluate-issue>`. Its body references the evaluation",
+    "   file path and lists the verticals that clear the threshold (if any).",
+    "",
+    "6. **Commit and push** the evaluation file. Close the evaluate issue.",
+    "",
+    "---",
+    "",
+    "## Phase 3: Plan (`industry:plan`)",
+    "",
+    "**Goal:** For each vertical that clears the threshold, open a",
+    "`research:scope` issue so the `research-pipeline` bundle can pick it up",
+    "and produce a research deliverable.",
+    "",
+    "**Budget:** No new web searches. Read the evaluation, write a plan",
+    "file, and create one downstream research issue per cleared vertical.",
+    "",
+    "### Steps",
+    "",
+    "1. **Read the evaluation file** referenced in the issue body.",
+    "",
+    "2. **Identify cleared verticals.** Any vertical whose weighted score",
+    "   meets or exceeds the threshold advances. If the evaluation flagged",
+    "   scoring gaps that block a pass/fail decision, treat the vertical as",
+    "   **not cleared** and note it in the plan.",
+    "",
+    "3. **Write the plan file** to",
+    "   `<PLANS_DIR>/<DISCOVERY_SLUG>.plan.md`:",
+    "",
+    "   ```markdown",
+    "   ---",
+    '   title: "Industry Plan: <scope>"',
+    "   slug: <DISCOVERY_SLUG>",
+    "   date: YYYY-MM-DD",
+    "   parent_issue: <N>",
+    "   evaluation_source: <EVALUATIONS_DIR>/<DISCOVERY_SLUG>.evaluation.md",
+    "   ---",
+    "",
+    "   # Industry Plan: <scope>",
+    "",
+    "   ## Cleared Verticals",
+    "   | Vertical | Score | Downstream Issue |",
+    "   |----------|-------|------------------|",
+    "   | <name> | 0.73 | #<research-scope-issue> |",
+    "",
+    "   ## Not Cleared",
+    "   | Vertical | Score | Reason |",
+    "   |----------|-------|--------|",
+    "   | <name> | 0.41 | below threshold |",
+    "",
+    "   ## Notes",
+    "   <anything the plan author wants to preserve for future iterations>",
+    "   ```",
+    "",
+    "4. **Create one `research:scope` issue per cleared vertical.** This",
+    "   assumes the `research-pipeline` bundle is enabled in the consuming",
+    "   project. Each downstream issue should:",
+    "   - Carry `type:research`, `research:scope`, `priority:medium`, and",
+    "     `status:ready` labels",
+    "   - Include the research question framed for the vertical (what the",
+    "     downstream research needs to answer)",
+    "   - Cite the evaluation row that justified advancing the vertical",
+    "   - Reference the plan file path for traceability",
+    "",
+    "5. **Cross-link** \u2014 update the plan file's `## Cleared Verticals`",
+    "   table so each row references its newly-created `research:scope`",
+    "   issue number.",
+    "",
+    "6. **Commit and push** the plan file. Close the plan issue.",
+    "",
+    "---",
+    "",
+    "## Output Boundaries",
+    "",
+    "This agent writes **only** to:",
+    "",
+    "- `<CANDIDATES_DIR>/` \u2014 candidate files (Phase 1)",
+    "- `<EVALUATIONS_DIR>/` \u2014 evaluation files (Phase 2)",
+    "- `<PLANS_DIR>/` \u2014 plan files (Phase 3, cross-linked with downstream",
+    "  research issue numbers)",
+    "",
+    "The pipeline produces **candidate lists, evaluations, and plans**. It",
+    "does not itself perform the downstream research, write industry",
+    "profiles, or publish deliverables \u2014 those are the responsibility of",
+    "specialized downstream agents (notably `research-analyst` from the",
+    "`research-pipeline` bundle) that pick up the `research:scope` issues",
+    "this pipeline creates. Keep this boundary clean so the industry",
+    "discovery pipeline stays generic.",
+    "",
+    "---",
+    "",
+    "## Rules",
+    "",
+    "- **One phase per session.** Never run two phases back-to-back in a",
+    "  single session.",
+    "- **Persist before closing.** Every phase must write its output file",
+    "  before closing its issue.",
+    "- **Do not invent the rubric.** If no authoritative rubric is",
+    "  available, emit a scaffold and flag `status:needs-attention` \u2014 never",
+    "  silently guess weights or thresholds.",
+    "- **Cite everything.** Every candidate, score, and pass/fail decision",
+    "  must carry at least one source citation.",
+    "- **Produce plans, not downstream work.** Do not open profile,",
+    "  requirement, or comparison issues from this pipeline. Downstream",
+    "  research is delegated to the `research-pipeline` bundle via",
+    "  `research:scope` issues."
+  ].join("\n")
+};
+var discoverIndustriesSkill = {
+  name: "discover-industries",
+  description: "Kick off an industry-discovery pipeline. Creates an industry:discover issue carrying the discovery scope and dispatches Phase 1 (Discover) in the industry-discovery-analyst agent.",
+  disableModelInvocation: true,
+  userInvocable: true,
+  context: "fork",
+  agent: "industry-discovery-analyst",
+  platforms: { cursor: { exclude: true } },
+  instructions: [
+    "# Discover Industries",
+    "",
+    "Kick off an industry-discovery pipeline. Creates an",
+    "`industry:discover` issue carrying the discovery scope and dispatches",
+    "Phase 1 (Discover) in the industry-discovery-analyst agent.",
+    "",
+    "## Usage",
+    "",
+    "/discover-industries <scope>",
+    "",
+    "Optional extensions in the issue body:",
+    "- `sources: <list>` \u2014 authorized source categories or file paths",
+    "- `candidates: <N>` \u2014 override the default candidate-count target",
+    "  (default range 8\u201320)",
+    "- `slug: <kebab-case>` \u2014 override the derived discovery slug",
+    "- `rubric: inline` \u2014 include an inline `## Fit Rubric` section to use",
+    "  for Phase 2; otherwise the agent falls back to",
+    "  `docs/project-context.md` or a scaffold",
+    "- `threshold: <0.0\u20131.0>` \u2014 override the rubric's default threshold",
+    "",
+    "## Default Paths",
+    "",
+    "If the project has no override in `docs/project-context.md` or",
+    "`agentConfig.rules`, outputs land under:",
+    "",
+    "- `docs/industries/candidates/<slug>.candidates.md`",
+    "- `docs/industries/evaluations/<slug>.evaluation.md`",
+    "- `docs/industries/plans/<slug>.plan.md`",
+    "",
+    "## Steps",
+    "",
+    "1. Create an `industry:discover` issue with `type:industry-discovery`,",
+    "   `priority:medium`, and `status:ready`. Body must include the",
+    "   verbatim scope, authorized sources, and any overrides.",
+    "2. Execute Phase 1 (Discover) of the industry-discovery-analyst",
+    "   agent.",
+    "3. Phase 1 creates an `industry:evaluate` issue, which Phase 2 follows",
+    "   with an `industry:plan` issue. Each downstream issue declares its",
+    "   `Depends on:` predecessor. Phase 3 creates one `research:scope`",
+    "   issue for each vertical that clears the threshold.",
+    "",
+    "## Output",
+    "",
+    "- A candidate file under the project's candidates directory",
+    "- An evaluation file with per-candidate scores under the evaluations",
+    "  directory",
+    "- A plan file under the plans directory, cross-linked to downstream",
+    "  research issues",
+    "- One `research:scope` issue per cleared vertical \u2014 picked up by the",
+    "  `research-pipeline` bundle's `research-analyst` agent"
+  ].join("\n")
+};
+var industryDiscoveryBundle = {
+  name: "industry-discovery",
+  description: "Industry-vertical discovery pipeline: discover candidates, evaluate against a fit rubric, plan downstream research. Opt-in only; domain-neutral; filesystem-durable between phases.",
+  appliesWhen: () => false,
+  rules: [
+    {
+      name: "industry-discovery-workflow",
+      description: "Describes the 3-phase industry-discovery pipeline, the industry:* label taxonomy, and the handoff to the research-pipeline bundle.",
+      scope: AGENT_RULE_SCOPE.ALWAYS,
+      content: [
+        "# Industry Discovery Workflow",
+        "",
+        "Use `/discover-industries <scope>` to kick off an industry-vertical",
+        "discovery pipeline. The pipeline runs in 3 phases \u2014 discover,",
+        "evaluate, plan \u2014 each tracked by its own GitHub issue labeled",
+        "`industry:discover`, `industry:evaluate`, or `industry:plan`. All",
+        "issues carry `type:industry-discovery`.",
+        "",
+        "The pipeline produces **candidate lists, evaluations, and plans**.",
+        "Verticals that clear the configured fit threshold are handed off",
+        "to the `research-pipeline` bundle via `research:scope` issues for",
+        "downstream deliverables.",
+        "",
+        "See the `industry-discovery-analyst` agent definition for full",
+        "workflow details, default paths, the fit rubric convention, and",
+        "phase-by-phase instructions."
+      ].join("\n"),
+      platforms: {
+        cursor: { exclude: true }
+      },
+      tags: ["workflow"]
+    }
+  ],
+  skills: [discoverIndustriesSkill],
+  subAgents: [industryDiscoveryAnalystSubAgent],
+  labels: [
+    {
+      name: "type:industry-discovery",
+      color: "1D76DB",
+      description: "Work that discovers, evaluates, or plans research on industry verticals"
+    },
+    {
+      name: "industry:discover",
+      color: "C5DEF5",
+      description: "Phase 1: enumerate candidate industry verticals into a bounded candidate file"
+    },
+    {
+      name: "industry:evaluate",
+      color: "BFDADC",
+      description: "Phase 2: score candidate verticals against the configured fit rubric"
+    },
+    {
+      name: "industry:plan",
+      color: "D4C5F9",
+      description: "Phase 3: plan downstream research for verticals that clear the fit threshold"
+    }
+  ]
+};
+
 // src/agent/bundles/jest.ts
 var jestBundle = {
   name: "jest",
@@ -6263,7 +7509,9 @@ var BUILT_IN_BUNDLES = [
   researchPipelineBundle,
   companyProfileBundle,
   peopleProfileBundle,
-  softwareProfileBundle
+  softwareProfileBundle,
+  industryDiscoveryBundle,
+  bcmWriterBundle
 ];
 
 // src/agent/bundles/scope.ts
@@ -9783,9 +11031,11 @@ var TypeScriptConfig = class extends import_projen22.Component {
   addSyncLabelsWorkflow,
   awsCdkBundle,
   baseBundle,
+  bcmWriterBundle,
   companyProfileBundle,
   getLatestEligibleVersion,
   githubWorkflowBundle,
+  industryDiscoveryBundle,
   jestBundle,
   meetingAnalysisBundle,
   orchestratorBundle,