@codedrifters/configulator 0.0.203 → 0.0.205

package/lib/index.js

@@ -222,6 +222,7 @@ __export(index_exports, {
   addSyncLabelsWorkflow: () => addSyncLabelsWorkflow,
   awsCdkBundle: () => awsCdkBundle,
   baseBundle: () => baseBundle,
+  companyProfileBundle: () => companyProfileBundle,
   getLatestEligibleVersion: () => getLatestEligibleVersion,
   githubWorkflowBundle: () => githubWorkflowBundle,
   jestBundle: () => jestBundle,
@@ -231,6 +232,7 @@ __export(index_exports, {
   prReviewBundle: () => prReviewBundle,
   projenBundle: () => projenBundle,
   requirementsAnalystBundle: () => requirementsAnalystBundle,
+  researchPipelineBundle: () => researchPipelineBundle,
   resolveModelAlias: () => resolveModelAlias,
   resolveTemplateVariables: () => resolveTemplateVariables,
   slackBundle: () => slackBundle,
@@ -880,6 +882,559 @@ var baseBundle = {
   ]
 };
 
+// src/agent/bundles/project-context.ts
+var PROJECT_CONTEXT_PATH = "docs/project-context.md";
+var PROJECT_CONTEXT_READER_SECTION = [
+  "## Project Context",
+  "",
+  `Before doing any work, read \`${PROJECT_CONTEXT_PATH}\` at the`,
+  'repository root. It is the canonical answer to "what is this project',
+  'about?" \u2014 mission, domain vocabulary, in/out-of-scope capabilities, and',
+  "key stakeholders. Use it to frame judgment calls in this session.",
+  "",
+  `If \`${PROJECT_CONTEXT_PATH}\` does not exist, proceed with the current`,
+  "task and note the absence in your session log \u2014 the meeting-analyst and",
+  "requirements-analyst agents seed the file on their next run.",
+  "",
+  "You are a **read-only consumer** of this file. Do not edit it.",
+  "",
+  "---",
+  ""
+];
+var PROJECT_CONTEXT_MAINTAINER_SECTION = [
+  "## Project Context",
+  "",
+  `Before starting any phase, read \`${PROJECT_CONTEXT_PATH}\` at the`,
+  'repository root. It is the canonical answer to "what is this project',
+  'about?" \u2014 mission, domain vocabulary, in/out-of-scope capabilities, and',
+  "key stakeholders. Use it to judge relevance when scanning source",
+  "material in this session.",
+  "",
+  "### Seed on first use",
+  "",
+  `If \`${PROJECT_CONTEXT_PATH}\` does not exist, create it from this`,
+  "template and commit it alongside this phase's other outputs:",
+  "",
+  "```markdown",
+  "# Project Context",
+  "",
+  "> Canonical description of this project. Read by all agents before",
+  "> work. Updated by meeting-analyst and requirements-analyst when new",
+  "> scope, vocabulary, or stakeholders emerge.",
+  "",
+  "## Mission",
+  "TODO: one or two sentences on what this project exists to do.",
+  "",
+  "## Target Users",
+  "TODO: who uses this, in what role.",
+  "",
+  "## In-Scope Capabilities",
+  "TODO: bullet list of the capabilities this project owns.",
+  "",
+  "## Out-of-Scope",
+  "TODO: capabilities or concerns that are explicitly not this project's.",
+  "",
+  "## Domain Vocabulary",
+  "TODO: short glossary of domain terms, acronyms, and their definitions.",
+  "",
+  "## Key Stakeholders",
+  "TODO: named people or teams and what they care about.",
+  "",
+  "## References",
+  "TODO: links to BCM docs, competitive analysis, product roadmap, and",
+  "other authoritative sources.",
+  "```",
+  "",
+  "Fill whatever you can infer from the source material you are already",
+  "reading in this phase; leave `TODO:` placeholders for the rest.",
+  "",
+  "### Update on new facts",
+  "",
+  "When the source material you process reveals new project-scope",
+  "information \u2014 a new capability, a vocabulary term, an entity, a",
+  "stakeholder, an in/out-of-scope decision, or a shift in mission \u2014",
+  `append or revise the relevant section in \`${PROJECT_CONTEXT_PATH}\``,
+  "before closing the phase. Commit those edits with the phase's other",
+  "outputs.",
+  "",
+  "Keep edits surgical: short bullet additions, brief clarifications, or",
+  "single-line vocabulary entries. Treat the file as an accreting",
+  "reference, not a document you reshape every session.",
+  "",
+  "---",
+  ""
+];
+
+// src/agent/bundles/company-profile.ts
+var companyProfileAnalystSubAgent = {
+  name: "company-profile-analyst",
+  description: "Researches an external company (competitor, vendor, partner, customer, etc.) from public sources and produces a structured markdown profile. Optionally enqueues follow-up people and software research tasks. One company per session, tracked by company:* GitHub issue labels.",
+  model: AGENT_MODEL.POWERFUL,
+  maxTurns: 80,
+  platforms: { cursor: { exclude: true } },
+  prompt: [
+    "# Company Profile Analyst Agent",
+    "",
+    "You research a single external company from public sources and write",
+    "a structured markdown profile. Each profile cycle runs across a small",
+    "sequence of GitHub issues \u2014 one per phase \u2014 and produces a single",
+    "profile file on disk plus optional follow-up research issues.",
+    "",
+    "This agent is **domain-neutral**. It makes no assumptions about what",
+    "the consuming project sells, which industry it serves, or which",
+    "companies matter to it. All domain-specific vocabulary, output",
+    "locations, and profile-template overrides come from the invoking",
+    "issue body 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. **One company per session.** Never profile two companies in a",
+    "   single session, even if they came up together.",
+    "2. **Public sources only.** Use the company's own site, press, product",
+    "   docs, job listings, and other public material. Do not attempt to",
+    "   access gated or paywalled content unless the invoking issue body",
+    "   explicitly authorizes it.",
+    "3. **Filesystem durability.** The profile file is the deliverable. It",
+    "   is committed to disk before the profile issue closes. Downstream",
+    "   phases read from disk \u2014 never rely on session memory.",
+    "4. **Generic over specific.** No hardcoded company types, taxonomies,",
+    "   or competitive assumptions. Use the generic company-type taxonomy",
+    "   below and let consuming projects override it.",
+    "5. **Cite everything.** Every non-trivial factual claim in the profile",
+    "   must carry a source citation (URL plus access date).",
+    "6. **Follow-up, don't widen scope.** If the session turns up adjacent",
+    "   research questions (a key person worth profiling, a product worth",
+    "   evaluating), emit a follow-up issue rather than expanding the",
+    "   profile beyond its scope.",
+    "",
+    "---",
+    "",
+    "## Company Type Taxonomy",
+    "",
+    "Pick exactly one type per company profile. The taxonomy is",
+    "deliberately generic \u2014 consuming projects override it via",
+    "`agentConfig.rules` if they need a domain-specific refinement.",
+    "",
+    "| Type | Use for |",
+    "|------|---------|",
+    "| `competitor` | Companies that sell a substitutable offering to the same customers. |",
+    "| `industry-player` | Notable companies in the same industry that are not direct competitors (adjacent offerings, upstream/downstream, ecosystem). |",
+    "| `software-vendor` | Companies whose software this project uses, integrates with, or evaluates as a build-vs-buy option. |",
+    "| `customer` | Existing or prospective customers worth understanding in depth. |",
+    "| `partner` | Strategic or channel partners, integrators, resellers, design partners. |",
+    "| `investor` | Funds, angels, corporate investors relevant to fundraising or market positioning. |",
+    "",
+    "If the company plausibly fits two types, prefer the one that reflects",
+    "the **reason the profile was requested**, and note the secondary type",
+    "in the profile body.",
+    "",
+    "---",
+    "",
+    "## State Machine Overview",
+    "",
+    "```",
+    "\u250C\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\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\u2510",
+    "\u2502 1. RESEARCH       \u2502\u2500\u2500\u2500\u2500\u25B6\u2502 2. DRAFT PROFILE     \u2502\u2500\u2500\u2500\u2500\u25B6\u2502 3. FOLLOWUP       \u2502",
+    "\u2502 Collect public    \u2502     \u2502 Write the structured \u2502     \u2502 Create follow-up  \u2502",
+    "\u2502 sources into a    \u2502     \u2502 markdown profile to  \u2502     \u2502 research issues   \u2502",
+    "\u2502 bounded notes     \u2502     \u2502 the configured path  \u2502     \u2502 for people and    \u2502",
+    "\u2502 file              \u2502     \u2502                      \u2502     \u2502 software surfaced \u2502",
+    "\u2514\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\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\u2518",
+    "```",
+    "",
+    "**Issue labels encode the phase:**",
+    "",
+    "| Label | Phase | Session work |",
+    "|-------|-------|-------------|",
+    "| `company:research` | 1. Research | Gather public sources. Write a bounded research-notes file. Create the draft issue. |",
+    "| `company:draft` | 2. Draft | Read the research notes. Write the structured profile to `<PROFILES_DIR>`. Create the follow-up issue if warranted. |",
+    "| `company:followup` | 3. Followup | Read the profile. Enqueue people/software research issues for items surfaced in the profile. |",
+    "",
+    "All issues also carry `type:company-profile` and a `status:*` label.",
+    "",
+    "**Issue count per company cycle:** 1 research + 1 draft + 0\u20131 followup =",
+    "**2\u20133 sessions**. The followup phase is skipped when the profile did",
+    "not surface any person or product worth follow-up research.",
+    "",
+    "**Shortened paths:**",
+    "- Research phase determines the company is out of scope (not",
+    "  relevant, insufficient public material) \u2192 research issue closes",
+    "  with a justification and no downstream issues are created \u2192 **1 session**.",
+    "- Short profile with no follow-ups needed \u2192 **2 sessions**.",
+    "",
+    "---",
+    "",
+    "## Configurable Paths",
+    "",
+    "The pipeline uses these placeholders. Consuming projects override the",
+    "defaults by passing paths in the `/profile-company` skill invocation",
+    "or by extending this rule in their own `agentConfig.rules`.",
+    "",
+    "| Placeholder | Meaning | Default |",
+    "|-------------|---------|---------|",
+    "| `<COMPANY_ROOT>` | Root folder for company profiles | `docs/companies/` |",
+    "| `<PROFILES_DIR>` | Final company profile files | `<COMPANY_ROOT>/profiles/` |",
+    "| `<NOTES_DIR>` | Research-notes files from Phase 1 | `<COMPANY_ROOT>/notes/` |",
+    "| `<COMPANY_SLUG>` | Short kebab-case slug identifying the company | derived from the company name |",
+    "",
+    "If `docs/project-context.md` specifies a different company-research",
+    "tree (for example by reusing the research-pipeline deliverables",
+    "folder), prefer that. Otherwise fall back to the defaults above.",
+    "",
+    "---",
+    "",
+    "## Agent Loop",
+    "",
+    "Run this loop exactly once per session. Never start a second issue.",
+    "",
+    "1. Claim one open `type:company-profile` issue using phase priority:",
+    "   `company:research` > `company:draft` > `company:followup`.",
+    "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 `company:*`",
+    "   label.",
+    "4. Commit, push, open a PR (if applicable), and close the issue per",
+    "   your project's PR workflow.",
+    "",
+    "---",
+    "",
+    "## Phase 1: Research (`company:research`)",
+    "",
+    "**Goal:** Gather public sources into a bounded research-notes file.",
+    "",
+    "**Budget:** Public web search only, unless the issue body authorizes",
+    "additional sources. Write one notes file. Do not write the profile",
+    "in this phase.",
+    "",
+    "### Steps",
+    "",
+    "1. **Read the issue body.** It should include:",
+    "   - The company name and website (if known)",
+    "   - The requested company type from the taxonomy above",
+    "   - The reason the profile was requested (framing \u2014 what does the",
+    "     invoking project want to learn?)",
+    "   - Optional: `<COMPANY_SLUG>` override, custom output paths",
+    "",
+    "2. **Derive `<COMPANY_SLUG>`** if not supplied \u2014 a 2\u20134 word kebab-case",
+    "   summary of the company name. Ensure the slug is not already in use",
+    "   under `<PROFILES_DIR>/` or `<NOTES_DIR>/`.",
+    "",
+    "3. **Gather sources.** Prioritize in this order:",
+    "   - The company's own website (home, product, pricing, about, careers)",
+    "   - Recent public press releases and reputable news coverage",
+    "   - Public product documentation and changelogs",
+    "   - Job listings (signals on stack, team size, and hiring focus)",
+    "   - Public profiles on well-known directories (Crunchbase, LinkedIn",
+    "     company page, GitHub organization) when the issue body authorizes",
+    "     them",
+    "",
+    "4. **Write a research-notes file** to",
+    "   `<NOTES_DIR>/<COMPANY_SLUG>.notes.md`:",
+    "",
+    "   ```markdown",
+    "   ---",
+    '   title: "Research Notes: <company name>"',
+    "   slug: <COMPANY_SLUG>",
+    "   company_type: <one of the taxonomy values>",
+    "   date: YYYY-MM-DD",
+    "   parent_issue: <N>",
+    "   ---",
+    "",
+    "   # Research Notes: <company name>",
+    "",
+    "   ## Framing",
+    "   <why this company was requested and what to learn>",
+    "",
+    "   ## Raw Findings",
+    "   - <finding> \u2014 source: <citation>",
+    "",
+    "   ## Candidate People of Interest",
+    "   - <name, role> \u2014 source: <citation>",
+    "",
+    "   ## Candidate Products / Software of Interest",
+    "   - <product name> \u2014 source: <citation>",
+    "",
+    "   ## Open Questions",
+    "   <anything the notes could not answer from public sources>",
+    "",
+    "   ## Sources",
+    "   - <source URL or file path> \u2014 <date accessed>",
+    "   ```",
+    "",
+    "5. **Create the `company:draft` issue** with `Depends on: #<research-issue>`.",
+    "   Its body references the notes file path and the requested company",
+    "   type.",
+    "",
+    "6. **Commit and push** the notes file. Close the research issue.",
+    "",
+    "---",
+    "",
+    "## Phase 2: Draft Profile (`company:draft`)",
+    "",
+    "**Goal:** Write the structured company profile from the research notes.",
+    "",
+    "**Budget:** No new web searches unless explicitly needed to fill a",
+    "gap the notes flagged. Write one profile file.",
+    "",
+    "### Steps",
+    "",
+    "1. **Read the research-notes file** referenced in the issue body.",
+    "",
+    "2. **Check for duplicates.** If `<PROFILES_DIR>/<COMPANY_SLUG>.md`",
+    "   already exists, open it and decide whether to update in place or",
+    "   flag a naming collision. Never silently overwrite a non-trivial",
+    "   existing profile.",
+    "",
+    "3. **Write the profile** to `<PROFILES_DIR>/<COMPANY_SLUG>.md` using",
+    "   the template below. All sections are required; use",
+    "   `_Not available in public sources._` when a section cannot be",
+    "   filled from the notes.",
+    "",
+    "   ```markdown",
+    "   ---",
+    '   title: "<company name>"',
+    "   slug: <COMPANY_SLUG>",
+    "   company_type: <one of the taxonomy values>",
+    "   website: <primary URL>",
+    "   date: YYYY-MM-DD",
+    "   parent_issue: <N>",
+    "   notes: <NOTES_DIR>/<COMPANY_SLUG>.notes.md",
+    "   ---",
+    "",
+    "   # <company name>",
+    "",
+    "   ## Summary",
+    "   <2\u20134 sentence elevator description: what they do, who they sell to>",
+    "",
+    "   ## Classification",
+    "   - **Primary type:** <taxonomy value>",
+    "   - **Secondary type (if any):** <taxonomy value or `n/a`>",
+    "   - **Relevance to this project:** <1\u20132 sentences tying the company",
+    "     back to the framing from the notes>",
+    "",
+    "   ## Offering",
+    "   - **Products / services:** <bullet list with one-line descriptions>",
+    "   - **Target customers:** <who they sell to>",
+    "   - **Pricing model:** <if disclosed>",
+    "",
+    "   ## Company",
+    "   - **Founded:** <year if known>",
+    "   - **Headquarters:** <city, country if known>",
+    "   - **Size signals:** <headcount, funding stage, public/private \u2014 if known>",
+    "   - **Notable people:** <founders, relevant leaders>",
+    "",
+    "   ## Technology Signals",
+    "   <stack hints from job listings, product docs, public engineering",
+    "   content \u2014 each bullet cited>",
+    "",
+    "   ## Positioning / Differentiation",
+    "   <how they describe themselves and how they differ from adjacent",
+    "   companies \u2014 use their own language, cited, rather than inferred>",
+    "",
+    "   ## Risks / Open Questions",
+    "   <what the profile could not answer; flag anything the follow-up",
+    "   phase should escalate>",
+    "",
+    "   ## Follow-up Candidates",
+    "   - **People to profile:** <list of candidate name, role pairs>",
+    "   - **Products / software to evaluate:** <list of candidate product",
+    "     names>",
+    "",
+    "   ## Sources",
+    "   - <source URL> \u2014 <date accessed>",
+    "   ```",
+    "",
+    "4. **Decide whether a follow-up issue is warranted.** Create a",
+    "   `company:followup` issue (depending on this draft issue) only if",
+    "   the profile lists at least one follow-up candidate. Otherwise,",
+    "   note in the draft issue's closing comment that no follow-up is",
+    "   needed.",
+    "",
+    "5. **Commit and push** the profile file. Close the draft issue.",
+    "",
+    "---",
+    "",
+    "## Phase 3: Followup (`company:followup`)",
+    "",
+    "**Goal:** Create downstream research issues for the people and",
+    "products surfaced in the profile.",
+    "",
+    "**Budget:** No new research. Read the profile, enqueue issues, close",
+    "the phase.",
+    "",
+    "### Steps",
+    "",
+    "1. **Read the profile file** referenced in the issue body.",
+    "",
+    "2. **Enqueue people-profile issues** for each entry under",
+    "   `Follow-up Candidates > People to profile`. Use the consuming",
+    "   project's people-research pipeline if one exists; otherwise, open",
+    "   a generic `type:research` issue describing what to learn about the",
+    "   person and linking back to the company profile.",
+    "",
+    "3. **Enqueue software-evaluation issues** for each entry under",
+    "   `Follow-up Candidates > Products / software to evaluate`. Again,",
+    "   use a project-specific pipeline if configured, otherwise a generic",
+    "   `type:research` issue.",
+    "",
+    "4. **Cross-link** \u2014 update the profile's `## Follow-up Candidates`",
+    "   section so each entry references its newly-created issue number.",
+    "",
+    "5. **Commit and push** (if the profile was updated). Close the",
+    "   followup issue.",
+    "",
+    "---",
+    "",
+    "## Output Boundaries",
+    "",
+    "This agent writes **only** to:",
+    "",
+    "- `<NOTES_DIR>/` \u2014 research-notes files (Phase 1)",
+    "- `<PROFILES_DIR>/` \u2014 company profiles (Phase 2, updated in Phase 3)",
+    "",
+    "The pipeline produces **profiles and notes only**. Deeper research on",
+    "people or products is delegated to downstream research pipelines via",
+    "follow-up issues \u2014 this agent never writes person profiles, product",
+    "evaluations, or comparative analyses itself. Keep this boundary clean",
+    "so the company-profile pipeline stays generic.",
+    "",
+    "---",
+    "",
+    "## Rules",
+    "",
+    "- **One company per session.** Never profile two companies back-to-back.",
+    "- **Persist before closing.** Every phase must write its output file",
+    "  before closing its issue.",
+    "- **Cite everything.** Profile claims without source citations do not",
+    "  belong in the deliverable.",
+    "- **No assumed competition.** Never call a company a competitor unless",
+    "  the invoking issue body or the consuming project's configuration",
+    "  says so.",
+    "- **Produce profiles, not downstream work.** Do not open",
+    "  `type:requirement` or formal evaluation issues from this pipeline.",
+    "  Follow-up work is scoped through `company:followup` or delegated to",
+    "  downstream research agents."
+  ].join("\n")
+};
+var profileCompanySkill = {
+  name: "profile-company",
+  description: "Kick off a company-profile pipeline. Creates a company:research issue for the given company and dispatches Phase 1 (Research) in the company-profile-analyst agent.",
+  disableModelInvocation: true,
+  userInvocable: true,
+  context: "fork",
+  agent: "company-profile-analyst",
+  platforms: { cursor: { exclude: true } },
+  instructions: [
+    "# Profile Company",
+    "",
+    "Kick off a company-profile pipeline. Creates a `company:research`",
+    "issue carrying the company name, type, and framing, then dispatches",
+    "Phase 1 (Research) in the company-profile-analyst agent.",
+    "",
+    "## Usage",
+    "",
+    "/profile-company <company-name>",
+    "",
+    "Optional extensions in the issue body:",
+    "- `type: <competitor | industry-player | software-vendor | customer |",
+    "   partner | investor>` \u2014 override the default type inference",
+    "- `website: <url>` \u2014 canonical website if not obvious from the name",
+    "- `framing: <text>` \u2014 why this profile was requested and what to learn",
+    "- `slug: <kebab-case>` \u2014 override the derived company slug",
+    "- `sources: <list>` \u2014 additional authorized sources beyond public web",
+    "",
+    "## Default Paths",
+    "",
+    "If the project has no override in `docs/project-context.md` or",
+    "`agentConfig.rules`, outputs land under:",
+    "",
+    "- `docs/companies/notes/<slug>.notes.md`",
+    "- `docs/companies/profiles/<slug>.md`",
+    "",
+    "## Steps",
+    "",
+    "1. Create a `company:research` issue with `type:company-profile`,",
+    "   `priority:medium`, and `status:ready`. Body must include the",
+    "   company name, selected type, framing, and any overrides.",
+    "2. Execute Phase 1 (Research) of the company-profile-analyst agent.",
+    "3. Phase 1 creates the `company:draft` issue. Phase 2 may create a",
+    "   `company:followup` issue. Each downstream issue declares its",
+    "   `Depends on:` predecessor.",
+    "",
+    "## Output",
+    "",
+    "- A research-notes file under the project's notes directory",
+    "- A single company profile under the profiles directory",
+    "- Optional follow-up research issues for key people and products",
+    "  surfaced in the profile",
+    "- This pipeline produces **profiles only** \u2014 it does not write person",
+    "  profiles, product evaluations, or comparative analyses itself."
+  ].join("\n")
+};
+var companyProfileBundle = {
+  name: "company-profile",
+  description: "Company research and profiling pipeline: research, draft profile, followup. Opt-in only; domain-neutral; filesystem-durable between phases.",
+  appliesWhen: () => false,
+  rules: [
+    {
+      name: "company-profile-workflow",
+      description: "Describes the 3-phase company-profile pipeline, the company:* label taxonomy, and the boundary against downstream research agents.",
+      scope: AGENT_RULE_SCOPE.ALWAYS,
+      content: [
+        "# Company Profile Workflow",
+        "",
+        "Use `/profile-company <company-name>` to kick off a company",
+        "research and profiling pipeline. The pipeline runs in up to 3",
+        "phases \u2014 research, draft, followup \u2014 each tracked by its own",
+        "GitHub issue labeled `company:research`, `company:draft`, or",
+        "`company:followup`. All issues carry `type:company-profile`.",
+        "",
+        "The pipeline produces **company profiles only**. Deeper research",
+        "on people or products surfaced in a profile is delegated to",
+        "downstream research pipelines via `company:followup` issues.",
+        "",
+        "See the `company-profile-analyst` agent definition for full",
+        "workflow details, default paths, the company-type taxonomy, and",
+        "phase-by-phase instructions."
+      ].join("\n"),
+      platforms: {
+        cursor: { exclude: true }
+      },
+      tags: ["workflow"]
+    }
+  ],
+  skills: [profileCompanySkill],
+  subAgents: [companyProfileAnalystSubAgent],
+  labels: [
+    {
+      name: "type:company-profile",
+      color: "0E8A16",
+      description: "Work that produces or maintains a company profile or its research notes"
+    },
+    {
+      name: "company:research",
+      color: "C5DEF5",
+      description: "Phase 1: gather public sources about a company into a research-notes file"
+    },
+    {
+      name: "company:draft",
+      color: "BFDADC",
+      description: "Phase 2: write the structured company profile from research notes"
+    },
+    {
+      name: "company:followup",
+      color: "D4C5F9",
+      description: "Phase 3: enqueue follow-up research issues for people and products surfaced in the profile"
+    }
+  ]
+};
+
 // src/agent/bundles/github-workflow.ts
 var import_github = require("projen/lib/github");
 var githubWorkflowBundle = {
@@ -1027,154 +1582,71 @@ var githubWorkflowBundle = {
         "- Use conventional commit format for the PR title",
         "- Delegate merge to the `pr-reviewer` sub-agent \u2014 do not merge manually and do not enable auto-merge directly"
       ].join("\n"),
-      tags: ["workflow"]
-    }
-  ]
-};
-
-// src/agent/bundles/jest.ts
-var jestBundle = {
-  name: "jest",
-  description: "Jest testing conventions and patterns",
-  appliesWhen: (project) => hasDep(project, "jest"),
-  findApplicableProjects: (project) => findProjectsWithDep(project, "jest"),
-  rules: [
-    {
-      name: "jest-testing",
-      description: "Jest testing conventions and patterns",
-      scope: AGENT_RULE_SCOPE.FILE_PATTERN,
-      filePatterns: ["**/*.test.ts", "**/*.spec.ts"],
-      content: [
-        "# Jest Testing Patterns",
-        "",
-        "## Mandatory Requirements",
-        "",
-        "- **Tests MUST be created or updated whenever code functionality is added or changed**",
-        "- This applies to all code changes, including:",
-        "  - New features and functionality",
-        "  - Bug fixes",
-        "  - Refactoring that changes behavior",
-        "  - API changes",
-        "  - Configuration changes that affect functionality",
-        "- Tests should be written or updated as part of the same change that modifies the code",
-        "",
-        "## Test Structure",
-        "",
-        "- Use **Jest** with SWC for fast compilation",
-        "- Test files: `.spec.ts` or `.test.ts` (co-located with source)",
-        "- Use descriptive test names: `describe('ClassName', () => { it('should do something specific', () => {}) })`",
-        "- Prefer snapshot tests for complex object structures",
-        "- Mock external dependencies appropriately",
-        "",
-        "## Test Organization",
-        "",
-        "- Co-locate test files with source files",
-        "- Test files can use dev dependencies (ESLint rule override)",
-        "- Use `@swc/jest` for fast compilation",
-        "- Configure Jest in `jest.config.json` (not in package.json)",
-        "",
-        "## Example Test Structure",
-        "",
-        "```typescript",
-        "import { MyClass } from './my-class';",
-        "",
-        "describe('MyClass', () => {",
-        "  it('should do something specific', () => {",
-        "    // Test implementation",
-        "  });",
-        "});",
-        "```"
-      ].join("\n"),
-      tags: ["testing"]
-    }
-  ],
-  claudePermissions: {
-    allow: ["Bash(npx jest:*)"]
-  }
-};
-
-// src/agent/bundles/project-context.ts
-var PROJECT_CONTEXT_PATH = "docs/project-context.md";
-var PROJECT_CONTEXT_READER_SECTION = [
-  "## Project Context",
-  "",
-  `Before doing any work, read \`${PROJECT_CONTEXT_PATH}\` at the`,
-  'repository root. It is the canonical answer to "what is this project',
-  'about?" \u2014 mission, domain vocabulary, in/out-of-scope capabilities, and',
-  "key stakeholders. Use it to frame judgment calls in this session.",
-  "",
-  `If \`${PROJECT_CONTEXT_PATH}\` does not exist, proceed with the current`,
-  "task and note the absence in your session log \u2014 the meeting-analyst and",
-  "requirements-analyst agents seed the file on their next run.",
-  "",
-  "You are a **read-only consumer** of this file. Do not edit it.",
-  "",
-  "---",
-  ""
-];
-var PROJECT_CONTEXT_MAINTAINER_SECTION = [
-  "## Project Context",
-  "",
-  `Before starting any phase, read \`${PROJECT_CONTEXT_PATH}\` at the`,
-  'repository root. It is the canonical answer to "what is this project',
-  'about?" \u2014 mission, domain vocabulary, in/out-of-scope capabilities, and',
-  "key stakeholders. Use it to judge relevance when scanning source",
-  "material in this session.",
-  "",
-  "### Seed on first use",
-  "",
-  `If \`${PROJECT_CONTEXT_PATH}\` does not exist, create it from this`,
-  "template and commit it alongside this phase's other outputs:",
-  "",
-  "```markdown",
-  "# Project Context",
-  "",
-  "> Canonical description of this project. Read by all agents before",
-  "> work. Updated by meeting-analyst and requirements-analyst when new",
-  "> scope, vocabulary, or stakeholders emerge.",
-  "",
-  "## Mission",
-  "TODO: one or two sentences on what this project exists to do.",
-  "",
-  "## Target Users",
-  "TODO: who uses this, in what role.",
-  "",
-  "## In-Scope Capabilities",
-  "TODO: bullet list of the capabilities this project owns.",
-  "",
-  "## Out-of-Scope",
-  "TODO: capabilities or concerns that are explicitly not this project's.",
-  "",
-  "## Domain Vocabulary",
-  "TODO: short glossary of domain terms, acronyms, and their definitions.",
-  "",
-  "## Key Stakeholders",
-  "TODO: named people or teams and what they care about.",
-  "",
-  "## References",
-  "TODO: links to BCM docs, competitive analysis, product roadmap, and",
-  "other authoritative sources.",
-  "```",
-  "",
-  "Fill whatever you can infer from the source material you are already",
-  "reading in this phase; leave `TODO:` placeholders for the rest.",
-  "",
-  "### Update on new facts",
-  "",
-  "When the source material you process reveals new project-scope",
-  "information \u2014 a new capability, a vocabulary term, an entity, a",
-  "stakeholder, an in/out-of-scope decision, or a shift in mission \u2014",
-  `append or revise the relevant section in \`${PROJECT_CONTEXT_PATH}\``,
-  "before closing the phase. Commit those edits with the phase's other",
-  "outputs.",
-  "",
-  "Keep edits surgical: short bullet additions, brief clarifications, or",
-  "single-line vocabulary entries. Treat the file as an accreting",
-  "reference, not a document you reshape every session.",
-  "",
-  "---",
-  ""
-];
+      tags: ["workflow"]
+    }
+  ]
+};
+
+// src/agent/bundles/jest.ts
+var jestBundle = {
+  name: "jest",
+  description: "Jest testing conventions and patterns",
+  appliesWhen: (project) => hasDep(project, "jest"),
+  findApplicableProjects: (project) => findProjectsWithDep(project, "jest"),
+  rules: [
+    {
+      name: "jest-testing",
+      description: "Jest testing conventions and patterns",
+      scope: AGENT_RULE_SCOPE.FILE_PATTERN,
+      filePatterns: ["**/*.test.ts", "**/*.spec.ts"],
+      content: [
+        "# Jest Testing Patterns",
+        "",
+        "## Mandatory Requirements",
+        "",
+        "- **Tests MUST be created or updated whenever code functionality is added or changed**",
+        "- This applies to all code changes, including:",
+        "  - New features and functionality",
+        "  - Bug fixes",
+        "  - Refactoring that changes behavior",
+        "  - API changes",
+        "  - Configuration changes that affect functionality",
+        "- Tests should be written or updated as part of the same change that modifies the code",
+        "",
+        "## Test Structure",
+        "",
+        "- Use **Jest** with SWC for fast compilation",
+        "- Test files: `.spec.ts` or `.test.ts` (co-located with source)",
+        "- Use descriptive test names: `describe('ClassName', () => { it('should do something specific', () => {}) })`",
+        "- Prefer snapshot tests for complex object structures",
+        "- Mock external dependencies appropriately",
+        "",
+        "## Test Organization",
+        "",
+        "- Co-locate test files with source files",
+        "- Test files can use dev dependencies (ESLint rule override)",
+        "- Use `@swc/jest` for fast compilation",
+        "- Configure Jest in `jest.config.json` (not in package.json)",
+        "",
+        "## Example Test Structure",
+        "",
+        "```typescript",
+        "import { MyClass } from './my-class';",
+        "",
+        "describe('MyClass', () => {",
+        "  it('should do something specific', () => {",
+        "    // Test implementation",
+        "  });",
+        "});",
+        "```"
+      ].join("\n"),
+      tags: ["testing"]
+    }
+  ],
+  claudePermissions: {
+    allow: ["Bash(npx jest:*)"]
+  }
+};
 
 // src/agent/bundles/meeting-analysis.ts
 var meetingAnalystSubAgent = {
@@ -3494,6 +3966,481 @@ var requirementsAnalystBundle = {
   ]
 };
 
+// src/agent/bundles/research-pipeline.ts
+var researchAnalystSubAgent = {
+  name: "research-analyst",
+  description: "Runs a generic research micro-task pipeline (scope, slice search/synthesize, verify). One phase per session, tracked by research:* GitHub issue labels with filesystem-based durability between phases.",
+  model: AGENT_MODEL.POWERFUL,
+  maxTurns: 80,
+  platforms: { cursor: { exclude: true } },
+  prompt: [
+    "# Research Analyst Agent",
+    "",
+    "Generic research micro-task pipeline. Given a research question, you",
+    "break it into a scope, a fixed number of focused search/synthesize",
+    "slices, and a verification pass that reconciles the slice outputs into",
+    "a single deliverable. Each phase runs as its **own agent session**,",
+    "triggered by a GitHub issue with a `research:*` 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",
+    "is being researched (companies, products, people, markets, technical",
+    "topics, academic literature, etc.). All domain-specific vocabulary,",
+    "output locations, and acceptance criteria come from the invoking",
+    "issue body 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. **Micro-tasks, not mega-prompts.** Split work into small slices so",
+    "   each session has a bounded context window and a single deliverable.",
+    "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 domains, companies, source",
+    "   projects, or proprietary taxonomies. Use placeholders that the",
+    "   skill invocation or consuming project fills in.",
+    "5. **Verifiable synthesis.** The verify phase re-reads every slice",
+    "   output and produces a single deliverable whose claims can each be",
+    "   traced back to a slice.",
+    "",
+    "---",
+    "",
+    "## State Machine Overview",
+    "",
+    "```",
+    "\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\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. SCOPE    \u2502\u2500\u2500\u2500\u2500\u25B6\u2502  2. SLICE (\xD7N)      \u2502\u2500\u2500\u2500\u2500\u25B6\u2502  3. VERIFY   \u2502",
+    "\u2502  Turn the    \u2502     \u2502  For each slice:    \u2502     \u2502  Read every  \u2502",
+    "\u2502  question    \u2502     \u2502  search sources,    \u2502     \u2502  slice       \u2502",
+    "\u2502  into N      \u2502     \u2502  synthesize a       \u2502     \u2502  output,     \u2502",
+    "\u2502  focused     \u2502     \u2502  bounded note file  \u2502     \u2502  reconcile,  \u2502",
+    "\u2502  slices      \u2502     \u2502                     \u2502     \u2502  deliverable \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\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 |",
+    "|-------|-------|-------------|",
+    "| `research:scope` | 1. Scope | Decompose the research question into N focused slices. Write a scope file. Create N `research:slice` issues. |",
+    "| `research:slice` | 2. Slice | Execute one slice: search authorized sources, synthesize, write a single slice note file. |",
+    "| `research:verify` | 3. Verify | Read every slice note, reconcile findings, produce the final deliverable and a verification report. |",
+    "",
+    "All issues also carry `type:research` and a `status:*` label.",
+    "",
+    "**Issue count per research cycle:** 1 scope + N slice + 1 verify =",
+    "**N + 2 sessions**. Typical N is 3\u20136.",
+    "",
+    "**Shortened paths:**",
+    "- Scope phase determines the question is unanswerable or out of scope",
+    "  \u2192 scope issue closes with a justification and no downstream issues",
+    "  are created \u2192 **1 session**.",
+    "- Single-slice research (N = 1) \u2192 **3 sessions**. Never skip verify,",
+    "  even with one slice \u2014 verify is where the deliverable lands.",
+    "",
+    "---",
+    "",
+    "## Configurable Paths",
+    "",
+    "The pipeline uses these placeholders. Consuming projects override the",
+    "defaults by passing paths in the `/research` skill invocation or by",
+    "extending this rule in their own `agentConfig.rules`.",
+    "",
+    "| Placeholder | Meaning | Default |",
+    "|-------------|---------|---------|",
+    "| `<RESEARCH_ROOT>` | Root folder for all research outputs | `docs/research/` |",
+    "| `<SCOPE_DIR>` | Scope files | `<RESEARCH_ROOT>/scopes/` |",
+    "| `<SLICES_DIR>` | Slice note files | `<RESEARCH_ROOT>/slices/` |",
+    "| `<DELIVERABLES_DIR>` | Final verified deliverables | `<RESEARCH_ROOT>/deliverables/` |",
+    "| `<RESEARCH_SLUG>` | Short kebab-case slug identifying one research cycle | derived from the question |",
+    "| `<N>` | Number of slices (default 4, max 8) | `4` |",
+    "",
+    "If `docs/project-context.md` specifies a different research tree,",
+    "prefer that. Otherwise fall back to the defaults above.",
+    "",
+    "---",
+    "",
+    "## Agent Loop",
+    "",
+    "Run this loop exactly once per session. Never start a second issue.",
+    "",
+    "1. Claim one open `type:research` issue using phase priority:",
+    "   `research:scope` > `research:slice` > `research:verify`.",
+    "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 `research:*`",
+    "   label.",
+    "4. Commit, push, open a PR (if applicable), and close the issue per",
+    "   your project's PR workflow.",
+    "",
+    "---",
+    "",
+    "## Phase 1: Scope (`research:scope`)",
+    "",
+    "**Goal:** Turn a natural-language research question into a bounded",
+    "scope file and `N` focused slice issues.",
+    "",
+    "**Budget:** No web searches in this phase. Read the question, the",
+    "project context, and any cited source material already on disk. Write",
+    "one scope file. Create N slice issues.",
+    "",
+    "### Steps",
+    "",
+    "1. **Read the research question** from the issue body. The body should",
+    "   include:",
+    "   - The question itself",
+    "   - Authorized source categories (e.g. public web, vendor docs, a",
+    "     cited local file path) \u2014 if absent, default to public web only",
+    "   - Output acceptance criteria for the final deliverable",
+    "   - Optional: `<N>` override, `<RESEARCH_SLUG>` override, custom",
+    "     output paths",
+    "",
+    "2. **Derive `<RESEARCH_SLUG>`** if not supplied \u2014 a 3\u20135 word kebab-case",
+    "   summary of the question. Ensure the slug is not already in use",
+    "   under `<SCOPE_DIR>/`.",
+    "",
+    "3. **Decompose the question into N slices.** Each slice must:",
+    "   - Be answerable independently of the others",
+    "   - Fit inside a single agent session's context budget",
+    "   - Have a clearly scoped set of sources to consult",
+    "   - Produce a bounded note file (target: under 1500 words)",
+    "",
+    "4. **Write the scope file** to",
+    "   `<SCOPE_DIR>/<RESEARCH_SLUG>.scope.md`:",
+    "",
+    "   ```markdown",
+    "   ---",
+    '   title: "Research Scope: <question>"',
+    "   slug: <RESEARCH_SLUG>",
+    "   date: YYYY-MM-DD",
+    "   parent_issue: <N>",
+    "   slice_count: <N>",
+    "   ---",
+    "",
+    "   # Research Scope: <question>",
+    "",
+    "   ## Question",
+    "   <verbatim question from the issue>",
+    "",
+    "   ## Authorized Sources",
+    "   - <source category or path>",
+    "",
+    "   ## Acceptance Criteria",
+    "   - [ ] <criterion for the final deliverable>",
+    "",
+    "   ## Slices",
+    "   ### Slice 1: <title>",
+    "   - **Focus:** <what this slice answers>",
+    "   - **Sources:** <the subset of authorized sources this slice uses>",
+    "   - **Output:** <SLICES_DIR>/<RESEARCH_SLUG>-01-<slug>.slice.md",
+    "",
+    "   ### Slice 2: <title>",
+    "   ...",
+    "",
+    "   ## Out of Scope",
+    "   <sub-questions deliberately excluded from this cycle>",
+    "",
+    "   ## Deliverable",
+    "   <DELIVERABLES_DIR>/<RESEARCH_SLUG>.md",
+    "   ```",
+    "",
+    "5. **Create N `research:slice` issues**, one per slice, each with",
+    "   `Depends on: #<scope-issue>`. Each slice issue body references the",
+    "   scope file and names the exact slice (by number and title).",
+    "",
+    "6. **Create one `research:verify` issue** that depends on all N slice",
+    "   issues. Its body references the scope file and lists every slice",
+    "   output path that verify must read.",
+    "",
+    "7. **Commit and push** the scope file. Close the scope issue.",
+    "",
+    "---",
+    "",
+    "## Phase 2: Slice (`research:slice`)",
+    "",
+    "**Goal:** Answer one slice by searching the authorized sources and",
+    "writing a single slice note file.",
+    "",
+    "**Budget:** Search budget is one slice \u2014 do not expand scope. Write",
+    "one slice note. Do not create downstream issues.",
+    "",
+    "### Steps",
+    "",
+    "1. **Read the scope file** referenced in the issue body.",
+    "",
+    "2. **Identify your slice** by number and title. Re-read the slice's",
+    "   focus, sources, and output path.",
+    "",
+    "3. **Search the authorized sources.** Stay within the source list for",
+    "   your slice \u2014 do not broaden to the full scope's source list unless",
+    "   the slice explicitly permits it.",
+    "",
+    "4. **Synthesize a slice note** and write it to the slice's output",
+    "   path (e.g. `<SLICES_DIR>/<RESEARCH_SLUG>-NN-<slug>.slice.md`):",
+    "",
+    "   ```markdown",
+    "   ---",
+    '   title: "Slice NN: <title>"',
+    "   slug: <RESEARCH_SLUG>",
+    "   slice: NN",
+    "   date: YYYY-MM-DD",
+    "   parent_scope: <SCOPE_DIR>/<RESEARCH_SLUG>.scope.md",
+    "   parent_issue: <N>",
+    "   ---",
+    "",
+    "   # Slice NN: <title>",
+    "",
+    "   ## Question",
+    "   <the slice-level question>",
+    "",
+    "   ## Key Findings",
+    "   - <finding> \u2014 source: <citation>",
+    "",
+    "   ## Evidence",
+    "   <short quotations, paraphrases, or structured data with citations>",
+    "",
+    "   ## Gaps / Open Questions",
+    "   <anything the slice could not answer inside its budget>",
+    "",
+    "   ## Sources",
+    "   - <source URL or file path> \u2014 <date accessed>",
+    "   ```",
+    "",
+    "5. **Stay within the word budget** (default 1500 words). If the slice",
+    "   cannot fit, add an `## Overflow` section at the end noting what was",
+    "   cut and flag it for the verify phase \u2014 do not expand into other",
+    "   slices' territory.",
+    "",
+    "6. **Commit and push** the slice note. Close the slice issue.",
+    "",
+    "---",
+    "",
+    "## Phase 3: Verify (`research:verify`)",
+    "",
+    "**Goal:** Reconcile every slice into a single verified deliverable.",
+    "",
+    "**Budget:** No new web searches. Read the scope, read every slice",
+    "note, reconcile contradictions, write the deliverable and a short",
+    "verification report.",
+    "",
+    "### Steps",
+    "",
+    "1. **Read the scope file** and every slice note listed in the issue",
+    "   body. If any slice file is missing, stop and re-open the",
+    "   corresponding slice issue with `status:needs-attention`.",
+    "",
+    "2. **Build a claim index.** For every assertion in any slice, note",
+    "   which slice(s) support it and which sources back it.",
+    "",
+    "3. **Reconcile contradictions.** When slices disagree:",
+    "   - Prefer the slice with stronger sources",
+    "   - Flag unresolved contradictions in the verification report",
+    "   - Do not silently pick a side",
+    "",
+    "4. **Write the deliverable** to",
+    "   `<DELIVERABLES_DIR>/<RESEARCH_SLUG>.md`. The structure is dictated",
+    "   by the acceptance criteria in the scope file. Every factual claim",
+    "   in the deliverable must cite at least one slice note.",
+    "",
+    "5. **Write a verification report** to",
+    "   `<DELIVERABLES_DIR>/<RESEARCH_SLUG>.verify.md`:",
+    "",
+    "   ```markdown",
+    "   ---",
+    '   title: "Verification Report: <question>"',
+    "   slug: <RESEARCH_SLUG>",
+    "   date: YYYY-MM-DD",
+    "   parent_issue: <N>",
+    "   slices_read: <count>",
+    "   ---",
+    "",
+    "   # Verification Report: <question>",
+    "",
+    "   ## Acceptance Criteria Coverage",
+    "   - [x] <criterion> \u2014 covered by slice(s) <NN, NN>",
+    "   - [ ] <criterion> \u2014 **not covered**; gap noted in deliverable",
+    "",
+    "   ## Slice Coverage",
+    "   | Slice | Claims | Reused in deliverable | Notes |",
+    "   |-------|--------|-----------------------|-------|",
+    "   | 01 | <count> | <count> | |",
+    "",
+    "   ## Reconciled Contradictions",
+    "   - <short summary of each reconciled contradiction and why>",
+    "",
+    "   ## Unresolved Contradictions",
+    "   - <contradiction the verifier could not resolve>",
+    "",
+    "   ## Gaps",
+    "   - <question the pipeline could not answer>",
+    "   ```",
+    "",
+    "6. **Comment on the scope issue** with a summary linking to the",
+    "   deliverable and verification report.",
+    "",
+    "7. **Commit and push.** Close the verify issue.",
+    "",
+    "---",
+    "",
+    "## Output Boundaries",
+    "",
+    "This agent writes **only** to:",
+    "",
+    "- `<SCOPE_DIR>/` \u2014 scope files (Phase 1)",
+    "- `<SLICES_DIR>/` \u2014 slice notes (Phase 2)",
+    "- `<DELIVERABLES_DIR>/` \u2014 deliverables and verification reports",
+    "  (Phase 3)",
+    "",
+    "The pipeline produces **notes and deliverables only**. It does not",
+    "open downstream `type:requirement`, profile, or comparison issues \u2014",
+    "those are the responsibility of specialized downstream agents (e.g.",
+    "`requirements-analyst`, `meeting-analyst`) that consume the",
+    "deliverables produced here. Keep this boundary clean so the research",
+    "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 expand scope mid-slice.** Overflow goes into the slice's",
+    "  overflow section and is flagged for verify \u2014 not into another",
+    "  slice's territory.",
+    "- **Cite everything.** Claims without a source citation do not belong",
+    "  in a slice note or deliverable.",
+    "- **Produce notes, not downstream work.** Do not create",
+    "  `type:requirement`, profile, or comparison issues from this",
+    "  pipeline. Emit deliverables under `<DELIVERABLES_DIR>/` and let",
+    "  downstream agents decide what to do with them."
+  ].join("\n")
+};
+var researchSkill = {
+  name: "research",
+  description: "Kick off a generic research micro-task pipeline. Creates a research:scope issue and dispatches Phase 1 (Scope) in the research-analyst agent.",
+  disableModelInvocation: true,
+  userInvocable: true,
+  context: "fork",
+  agent: "research-analyst",
+  platforms: { cursor: { exclude: true } },
+  instructions: [
+    "# Research",
+    "",
+    "Kick off a generic research micro-task pipeline. Creates a",
+    "`research:scope` issue carrying the research question and dispatches",
+    "Phase 1 (Scope) in the research-analyst agent.",
+    "",
+    "## Usage",
+    "",
+    "/research <question>",
+    "",
+    "Optional extensions in the question body:",
+    "- `sources: <list>` \u2014 authorized source categories or file paths",
+    "- `slices: <N>` \u2014 override the default slice count (default 4, max 8)",
+    "- `slug: <kebab-case>` \u2014 override the derived research slug",
+    "- `acceptance: <list>` \u2014 explicit acceptance criteria for the",
+    "  deliverable",
+    "",
+    "## Default Paths",
+    "",
+    "If the project has no override in `docs/project-context.md` or",
+    "`agentConfig.rules`, outputs land under:",
+    "",
+    "- `docs/research/scopes/<slug>.scope.md`",
+    "- `docs/research/slices/<slug>-NN-<slice-slug>.slice.md`",
+    "- `docs/research/deliverables/<slug>.md`",
+    "- `docs/research/deliverables/<slug>.verify.md`",
+    "",
+    "## Steps",
+    "",
+    "1. Create a `research:scope` issue with `type:research`,",
+    "   `priority:medium`, and `status:ready`. Body must include the",
+    "   verbatim question, authorized sources, and any overrides.",
+    "2. Execute Phase 1 (Scope) of the research-analyst agent.",
+    "3. Phase 1 creates `research:slice` issues (one per slice) and a",
+    "   single `research:verify` issue. Each downstream issue declares",
+    "   its `Depends on:` predecessor.",
+    "",
+    "## Output",
+    "",
+    "- A scope file under the project's research scope directory",
+    "- One slice note per slice under the slices directory",
+    "- A single deliverable plus verification report under the deliverables",
+    "  directory",
+    "- This pipeline produces **notes and deliverables only** \u2014 it does",
+    "  not open downstream `type:requirement` or profile issues."
+  ].join("\n")
+};
+var researchPipelineBundle = {
+  name: "research-pipeline",
+  description: "Generic research micro-task pipeline: scope, N-way slice search/synthesize, and verify. Opt-in only; domain-neutral; filesystem-durable between phases.",
+  appliesWhen: () => false,
+  rules: [
+    {
+      name: "research-pipeline-workflow",
+      description: "Describes the 3-phase generic research pipeline, the research:* label taxonomy, and the boundary against downstream specialized agents.",
+      scope: AGENT_RULE_SCOPE.ALWAYS,
+      content: [
+        "# Research Pipeline Workflow",
+        "",
+        "Use `/research <question>` to kick off a generic research",
+        "micro-task pipeline. The pipeline runs in 3 phases \u2014 scope, slice,",
+        "verify \u2014 each tracked by its own GitHub issue labeled",
+        "`research:scope`, `research:slice`, or `research:verify`. All",
+        "issues carry `type:research`.",
+        "",
+        "The pipeline produces **notes and deliverables only**. It does",
+        "not open downstream `type:requirement` or profile issues \u2014 those",
+        "belong to specialized downstream agents that consume the",
+        "deliverables.",
+        "",
+        "See the `research-analyst` agent definition for full workflow",
+        "details, default paths, and phase-by-phase instructions."
+      ].join("\n"),
+      platforms: {
+        cursor: { exclude: true }
+      },
+      tags: ["workflow"]
+    }
+  ],
+  skills: [researchSkill],
+  subAgents: [researchAnalystSubAgent],
+  labels: [
+    {
+      name: "type:research",
+      color: "5319E7",
+      description: "Work that produces or consumes a research note, slice, or deliverable"
+    },
+    {
+      name: "research:scope",
+      color: "C5DEF5",
+      description: "Phase 1: decompose a research question into N focused slice issues"
+    },
+    {
+      name: "research:slice",
+      color: "BFDADC",
+      description: "Phase 2: execute one research slice \u2014 search authorized sources and write a slice note"
+    },
+    {
+      name: "research:verify",
+      color: "D4C5F9",
+      description: "Phase 3: reconcile slice notes into a verified deliverable"
+    }
+  ]
+};
+
 // src/agent/bundles/slack.ts
 var slackBundle = {
   name: "slack",
@@ -4144,7 +5091,9 @@ var BUILT_IN_BUNDLES = [
   meetingAnalysisBundle,
   orchestratorBundle,
   prReviewBundle,
-  requirementsAnalystBundle
+  requirementsAnalystBundle,
+  researchPipelineBundle,
+  companyProfileBundle
 ];
 
 // src/agent/bundles/scope.ts
@@ -7664,6 +8613,7 @@ var TypeScriptConfig = class extends import_projen22.Component {
   addSyncLabelsWorkflow,
   awsCdkBundle,
   baseBundle,
+  companyProfileBundle,
   getLatestEligibleVersion,
   githubWorkflowBundle,
   jestBundle,
@@ -7673,6 +8623,7 @@ var TypeScriptConfig = class extends import_projen22.Component {
   prReviewBundle,
   projenBundle,
   requirementsAnalystBundle,
+  researchPipelineBundle,
   resolveModelAlias,
   resolveTemplateVariables,
   slackBundle,