@codedrifters/configulator 0.0.204 → 0.0.205

package/lib/index.mjs

@@ -812,6 +812,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
 import { GitHub } from "projen/lib/github";
 var githubWorkflowBundle = {
@@ -1025,89 +1578,6 @@ var jestBundle = {
   }
 };
 
-// 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/meeting-analysis.ts
 var meetingAnalystSubAgent = {
   name: "meeting-analyst",
@@ -4552,7 +5022,8 @@ var BUILT_IN_BUNDLES = [
   orchestratorBundle,
   prReviewBundle,
   requirementsAnalystBundle,
-  researchPipelineBundle
+  researchPipelineBundle,
+  companyProfileBundle
 ];
 
 // src/agent/bundles/scope.ts
@@ -8084,6 +8555,7 @@ export {
   addSyncLabelsWorkflow,
   awsCdkBundle,
   baseBundle,
+  companyProfileBundle,
   getLatestEligibleVersion,
   githubWorkflowBundle,
   jestBundle,