@codedrifters/configulator 0.0.205 → 0.0.207

package/lib/index.mjs

@@ -2645,506 +2645,522 @@ var orchestratorBundle = {
   }
 };
 
-// src/pnpm/pnpm-workspace.ts
-import { relative } from "path";
-import { Component, YamlFile } from "projen";
-var MINIMUM_RELEASE_AGE = {
-  ZERO_DAYS: 0,
-  ONE_HOUR: 60,
-  SIX_HOURS: 360,
-  TWELVE_HOURS: 720,
-  ONE_DAY: 1440,
-  TWO_DAYS: 2880,
-  THREE_DAYS: 4320,
-  FOUR_DAYS: 5760,
-  FIVE_DAYS: 7200,
-  SIX_DAYS: 8640,
-  ONE_WEEK: 10080
-};
-var PnpmWorkspace = class _PnpmWorkspace extends Component {
-  /**
-   * Get the pnpm workspace component of a project. If it does not exist,
-   * return undefined.
-   *
-   * @param project
-   * @returns
-   */
-  static of(project) {
-    const isDefined = (c) => c instanceof _PnpmWorkspace;
-    return project.root.components.find(isDefined);
-  }
-  constructor(project, options = {}) {
-    super(project);
-    project.tryFindObjectFile("package.json")?.addDeletionOverride("pnpm");
-    this.fileName = options.fileName ?? "pnpm-workspace.yaml";
-    this.minimumReleaseAge = options.minimumReleaseAge ?? MINIMUM_RELEASE_AGE.ONE_DAY;
-    this.minimumReleaseAgeExclude = options.minimumReleaseAgeExclude ? ["@codedrifters/*", ...options.minimumReleaseAgeExclude] : ["@codedrifters/*"];
-    this.onlyBuiltDependencies = options.onlyBuiltDependencies ? options.onlyBuiltDependencies : [];
-    this.ignoredBuiltDependencies = options.ignoredBuiltDependencies ? options.ignoredBuiltDependencies : [];
-    this.subprojects = options.subprojects ?? [];
-    this.defaultCatalog = options.defaultCatalog;
-    this.namedCatalogs = options.namedCatalogs;
-    project.addPackageIgnore(this.fileName);
-    new YamlFile(this.project, this.fileName, {
-      obj: () => {
-        const pnpmConfig = {};
-        const packages = new Array();
-        for (const subproject of project.subprojects) {
-          packages.push(relative(this.project.outdir, subproject.outdir));
-        }
-        const packageSet = new Set(packages);
-        for (const subprojectPath of this.subprojects) {
-          packageSet.add(subprojectPath);
-        }
-        if (this.subprojects.length > 0) {
-          packages.length = 0;
-          packages.push(...packageSet);
-        }
-        pnpmConfig.minimumReleaseAge = this.minimumReleaseAge;
-        if (this.minimumReleaseAgeExclude.length > 0) {
-          pnpmConfig.minimumReleaseAgeExclude = this.minimumReleaseAgeExclude;
-        }
-        if (this.onlyBuiltDependencies.length > 0) {
-          pnpmConfig.onlyBuiltDependencies = this.onlyBuiltDependencies;
-        }
-        if (this.ignoredBuiltDependencies.length > 0) {
-          pnpmConfig.ignoreBuiltDependencies = this.ignoredBuiltDependencies;
-        }
-        if (this.defaultCatalog && Object.keys(this.defaultCatalog).length > 0) {
-          pnpmConfig.catalog = this.defaultCatalog;
-        }
-        if (this.namedCatalogs && Object.keys(this.namedCatalogs).length > 0) {
-          pnpmConfig.namedCatalogs = this.namedCatalogs;
-        }
-        return {
-          ...packages.length > 0 ? { packages } : {},
-          ...pnpmConfig ? { ...pnpmConfig } : {}
-        };
-      }
-    });
-  }
-};
-var MIMIMUM_RELEASE_AGE = MINIMUM_RELEASE_AGE;
-
-// src/agent/bundles/pnpm.ts
-var pnpmBundle = {
-  name: "pnpm",
-  description: "PNPM workspace rules and dependency management conventions",
-  appliesWhen: (project) => hasComponent(project, PnpmWorkspace),
-  rules: [
-    {
-      name: "pnpm-workspace",
-      description: "PNPM workspace and dependency management conventions",
-      scope: AGENT_RULE_SCOPE.FILE_PATTERN,
-      filePatterns: ["package.json", "pnpm-workspace.yaml", "pnpm-lock.yaml"],
-      content: [
-        "# PNPM Workspace Conventions",
-        "",
-        "## Package Management",
-        "",
-        "- Use **PNPM** for package management",
-        "- Workspace configuration in `pnpm-workspace.yaml`",
-        "- Dependencies managed through Projen, not directly in `package.json`",
-        "- **Always use workspace dependencies** (`workspace:*` or `workspace:^`) for packages within this monorepo",
-        "- Never use published NPM versions of internal packages; always reference the local workspace version",
-        "",
-        "## Dependency Management",
-        "",
-        "**DO:**",
-        "- Configure dependencies in Projen configuration files (`.projenrc.ts` or `projenrc/*.ts`)",
-        "- Add dependencies to `deps`, `devDeps`, or `peerDeps` arrays in project configuration",
-        '- Use catalog dependencies when available (e.g., `"aws-cdk-lib@catalog:"`)',
-        "- Ask the user to run `npx projen` and `pnpm install` after updating dependency configuration",
-        "",
-        "**DO NOT:**",
-        "- Run `npm install some-package`",
-        "- Run `pnpm add some-package`",
-        "- Run `yarn add some-package`",
-        "- Manually edit `package.json` dependencies",
-        "",
-        "Manual package installation creates conflicts with Projen-managed files."
-      ].join("\n"),
-      tags: ["workflow"]
-    }
-  ]
-};
-
-// src/agent/bundles/pr-review.ts
-var prReviewerSubAgent = {
-  name: "pr-reviewer",
-  description: "Reviews a pull request against its linked issue's acceptance criteria, then enables squash auto-merge or comments with findings",
+// src/agent/bundles/people-profile.ts
+var peopleProfileAnalystSubAgent = {
+  name: "people-profile-analyst",
+  description: "Researches an individual person (colleague, customer contact, vendor contact, partner contact, industry expert, or connector) from public sources and produces a structured markdown profile cross-linked to companies, software, and meeting notes. One person per session, tracked by people:* GitHub issue labels.",
   model: AGENT_MODEL.POWERFUL,
-  maxTurns: 40,
+  maxTurns: 80,
   platforms: { cursor: { exclude: true } },
   prompt: [
-    "# PR Reviewer Agent",
+    "# People Profile Analyst Agent",
     "",
-    "You review a single pull request in **{{repository.owner}}/{{repository.name}}**",
-    "against its linked issue's acceptance criteria, verify code quality and",
-    "convention compliance, and then either enable squash auto-merge or leave",
-    "a review comment with findings. You handle exactly **one PR per session**",
-    "unless invoked from the multi-PR loop skill (`/review-prs`), in which case",
-    "you process each eligible PR in turn.",
+    "You research a single person 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 cross-references to related entities",
+    "(companies, software, meeting notes) already tracked elsewhere in",
+    "the project.",
+    "",
+    "This agent is **domain-neutral**. It makes no assumptions about what",
+    "the consuming project sells, which industry it serves, or which",
+    "people matter to it. All domain-specific vocabulary, output",
+    "locations, cross-reference targets, 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,
-    "## Phase 1: Identify the PR",
+    "## Design Principles",
     "",
-    "If a PR number was provided in your instructions, use that. Otherwise stop",
-    "and report that you need a PR number \u2014 do not pick one yourself.",
+    "1. **One person per session.** Never profile two people in a single",
+    "   session, even if they came up together (e.g. co-founders).",
+    "2. **Public sources only.** Use the person's own public writing,",
+    "   company bios, conference talks, public interviews, and similar",
+    "   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 role types, taxonomies, or",
+    "   relationship assumptions. Use the generic person-role 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. **Respect privacy.** Profile only public, professional information.",
+    "   Never capture home addresses, personal phone numbers, family",
+    "   details, health information, or other private data even when",
+    "   encountered in public sources.",
+    "7. **Cross-reference, don't duplicate.** When the profile mentions a",
+    "   company, software product, or meeting already tracked by the",
+    "   consuming project, link to the existing artifact rather than",
+    "   duplicating its content. Do not create downstream research",
+    "   issues for these cross-references \u2014 only link.",
     "",
-    "## Phase 1.5: Pre-flight Eligibility Filter",
+    "---",
     "",
-    "Before spending turns on a full review, run a cheap eligibility check:",
+    "## Person Role Taxonomy",
     "",
-    "```bash",
-    "gh pr view <pr-number> --json number,title,body,headRefName,mergeable,mergeStateStatus,statusCheckRollup",
-    "```",
+    "Pick exactly one role per person profile. The taxonomy is",
+    "deliberately generic \u2014 consuming projects override it via",
+    "`agentConfig.rules` if they need a domain-specific refinement.",
     "",
-    "The PR is **eligible** only when **all** of the following hold:",
+    "| Role | Use for |",
+    "|------|---------|",
+    "| `colleague` | People inside your own organization worth tracking (teammates, cross-functional partners, leadership). |",
+    "| `customer-contact` | Named individuals at existing or prospective customer accounts. |",
+    "| `vendor-contact` | Named individuals at vendors, suppliers, or software providers you depend on. |",
+    "| `partner-contact` | Named individuals at strategic, channel, or integration partners. |",
+    "| `industry-expert` | Analysts, researchers, journalists, or well-known practitioners whose work shapes the market. |",
+    "| `connector` | People who primarily provide introductions, referrals, or access across networks \u2014 advisors, investors acting as connectors, community hubs. |",
     "",
-    '1. `mergeable == "MERGEABLE"` (no merge conflicts).',
-    "2. No **failing** required checks in `statusCheckRollup` \u2014 CI must be",
-    "   green or still pending. Any `FAILURE`, `TIMED_OUT`, `CANCELLED`, or",
-    "   `ERROR` conclusion on a required check disqualifies the PR.",
-    "3. The PR body contains a linked issue via one of the closing keywords:",
-    "   `Closes #N`, `Fixes #N`, or `Resolves #N` (case-insensitive).",
+    "If the person plausibly fits two roles, prefer the one that reflects",
+    "the **reason the profile was requested**, and note the secondary",
+    "role in the profile body.",
     "",
-    "If **any** check fails, post a short comment explaining the reason and",
-    "stop. Do not proceed to full review.",
+    "---",
     "",
-    "```bash",
-    "gh pr comment <pr-number> --body '<reason>'",
+    "## 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 Cross-link the    \u2502",
+    "\u2502 sources into a    \u2502     \u2502 markdown profile to  \u2502     \u2502 profile to existing\u2502",
+    "\u2502 bounded notes     \u2502     \u2502 the configured path  \u2502     \u2502 companies, software\u2502",
+    "\u2502 file              \u2502     \u2502                      \u2502     \u2502 and meeting notes \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",
     "```",
     "",
-    "Typical reasons:",
+    "**Issue labels encode the phase:**",
     "",
-    "- `Not reviewable: merge conflicts \u2014 please rebase onto the default branch.`",
-    "- `Not reviewable: required CI check <name> is failing.`",
-    "- `Not reviewable: PR body is missing a linked issue (Closes #N / Fixes #N / Resolves #N).`",
+    "| Label | Phase | Session work |",
+    "|-------|-------|-------------|",
+    "| `people:research` | 1. Research | Gather public sources. Write a bounded research-notes file. Create the draft issue. |",
+    "| `people:draft` | 2. Draft | Read the research notes. Write the structured profile to `<PROFILES_DIR>`. Create the followup issue if warranted. |",
+    "| `people:followup` | 3. Followup | Read the profile. Update cross-references to existing companies, software, and meeting notes. No new downstream issues. |",
     "",
-    "## Phase 2: Gather Context",
+    "All issues also carry `type:people-profile` and a `status:*` label.",
     "",
-    "```bash",
-    "gh pr view <pr-number> --json number,title,body,headRefName,baseRefName,isDraft,state,labels,reviews",
-    "gh pr diff <pr-number>",
-    "gh pr checks <pr-number>",
-    "```",
+    "**Issue count per person cycle:** 1 research + 1 draft + 0\u20131 followup =",
+    "**2\u20133 sessions**. The followup phase is skipped when the profile did",
+    "not surface any cross-references worth linking.",
     "",
-    "Extract the linked issue number from the PR body using the closing keywords",
-    "(`Closes #N`, `Fixes #N`, or `Resolves #N`) identified in Phase 1.5.",
+    "**Shortened paths:**",
+    "- Research phase determines the person 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 cross-references needed \u2192 **2 sessions**.",
     "",
-    "Then fetch the linked issue:",
+    "---",
     "",
-    "```bash",
-    "gh issue view <issue-number>",
-    "```",
+    "## Configurable Paths",
     "",
-    "## Phase 3: Compare Diff to Acceptance Criteria",
+    "The pipeline uses these placeholders. Consuming projects override the",
+    "defaults by passing paths in the `/profile-person` skill invocation",
+    "or by extending this rule in their own `agentConfig.rules`.",
     "",
-    "Read the issue body for an **Acceptance Criteria** (or equivalent) section.",
-    "Build a checklist from it. For each item:",
+    "| Placeholder | Meaning | Default |",
+    "|-------------|---------|---------|",
+    "| `<PEOPLE_ROOT>` | Root folder for person profiles | `docs/people/` |",
+    "| `<PROFILES_DIR>` | Final person profile files | `<PEOPLE_ROOT>/profiles/` |",
+    "| `<NOTES_DIR>` | Research-notes files from Phase 1 | `<PEOPLE_ROOT>/notes/` |",
+    "| `<PERSON_SLUG>` | Short kebab-case slug identifying the person | derived from the person's name |",
+    "| `<COMPANIES_DIR>` | Where existing company profiles live (for cross-references) | `docs/companies/profiles/` |",
+    "| `<SOFTWARE_DIR>` | Where existing software profiles live (for cross-references) | `docs/software/profiles/` |",
+    "| `<MEETINGS_DIR>` | Where meeting notes live (for cross-references) | `docs/meetings/` |",
+    "",
+    "If `docs/project-context.md` specifies a different people-research",
+    "tree or cross-reference target, prefer that. Otherwise fall back to",
+    "the defaults above. Cross-reference directories are read-only \u2014 this",
+    "agent never writes into them.",
     "",
-    "1. Locate the changes in the diff that satisfy it.",
-    "2. Mark it as `met`, `partial`, or `missing`.",
-    "3. Record the specific files / functions / tests that provide evidence.",
+    "---",
     "",
-    "Also evaluate:",
+    "## Refresh Cadence",
     "",
-    "- **Convention compliance** \u2014 PR title uses a conventional commit prefix,",
-    "  body includes a closing keyword, branch name follows project conventions",
-    "- **Test coverage** \u2014 new or changed behavior has tests",
-    "- **CI status** \u2014 `gh pr checks` reports all required checks passing",
-    "- **Scope creep** \u2014 diff stays within the issue's stated scope",
+    "Profiles go stale. A person changes jobs, publishes new work, or",
+    "shifts focus. The pipeline supports a configurable refresh cadence:",
     "",
-    "## Phase 4: Decide and Act",
+    "- **Default cadence:** 180 days from the profile's `date` frontmatter.",
+    "- **Override:** the invoking issue body may specify a `refresh_days: N`",
+    "  field, or the consuming project may set a project-wide default in",
+    "  `docs/project-context.md`.",
     "",
-    "### If all acceptance criteria are met and CI is green",
+    "When the `/profile-person` skill is invoked for a slug that already",
+    "has a profile:",
     "",
-    "Enable squash auto-merge with branch deletion. This queues the merge to",
-    "happen once required checks pass; no separate approval review is needed.",
+    "- If the profile is **younger** than the refresh cadence, the skill",
+    "  exits with a message pointing to the existing profile. Pass",
+    "  `force: true` in the issue body to refresh anyway.",
+    "- If the profile is **older** than the refresh cadence, the pipeline",
+    "  proceeds in update-in-place mode: Phase 2 edits the existing file,",
+    "  preserves its slug, and bumps the `date` frontmatter.",
     "",
-    "```bash",
-    "gh pr merge <pr-number> --auto --squash --delete-branch \\",
-    "  --subject '<conventional-commit-title>' \\",
-    "  --body '<extended-description>'",
-    "```",
+    "Refresh mode never changes the profile's role without an explicit",
+    "override in the refresh request \u2014 role changes are material and",
+    "warrant a human review step.",
     "",
-    "The squash-merge subject should follow conventional commit format (e.g.",
-    "`feat(scope): description`). The body should bullet the changes and end",
-    "with `Closes #<issue-number>`.",
+    "---",
     "",
-    "### If any criterion is missing, partial, or CI is failing",
+    "## Agent Loop",
     "",
-    "Post a plain comment (not a formal review block) with grouped findings:",
+    "Run this loop exactly once per session. Never start a second issue.",
     "",
-    "```bash",
-    "gh pr comment <pr-number> --body '<grouped findings>'",
-    "```",
+    "1. Claim one open `type:people-profile` issue using phase priority:",
+    "   `people:research` > `people:draft` > `people: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 `people:*`",
+    "   label.",
+    "4. Commit, push, open a PR (if applicable), and close the issue per",
+    "   your project's PR workflow.",
     "",
-    "Group findings by severity (**Blocking** / **Suggested** / **Nitpick**).",
-    "For each blocking finding, cite the unmet acceptance criterion and the",
-    "file or function the gap lives in. Do **not** merge, and do **not** push",
-    "any commits to the PR's branch.",
+    "---",
     "",
-    "Rationale for using a plain comment rather than `gh pr review",
-    "--request-changes`: it is lighter-weight, doesn't require the author to",
-    "dismiss a formal review, and composes cleanly with the multi-PR loop.",
+    "## Phase 1: Research (`people:research`)",
     "",
-    "## Phase 5: Branch Cleanup and Issue Closure Verification",
+    "**Goal:** Gather public sources into a bounded research-notes file.",
     "",
-    "Auto-merge may not be immediate. Poll the PR state up to 10 times, waiting",
-    "30 seconds between polls:",
+    "**Budget:** Public web search only, unless the issue body authorizes",
+    "additional sources. Write one notes file. Do not write the profile",
+    "in this phase.",
     "",
-    "```bash",
-    "gh pr view <pr-number> --json state --jq '.state'",
-    "```",
+    "### Steps",
     "",
-    "- **`MERGED`** \u2014 clean up locally **and** verify the linked issue closed:",
-    "  ```bash",
-    "  git checkout {{repository.defaultBranch}}",
-    "  git pull origin {{repository.defaultBranch}}",
-    "  git fetch --prune origin",
-    "  git branch -d <branch-name> 2>/dev/null || git branch -D <branch-name> 2>/dev/null || true",
-    "  ```",
-    "  Then check the linked issue state:",
-    "  ```bash",
-    "  gh issue view <issue-number> --json state --jq '.state'",
-    "  ```",
-    "  If the issue is **not** `CLOSED`, close it explicitly (this covers",
-    "  malformed or missing closing keywords on the merge commit):",
-    "  ```bash",
-    "  gh issue close <issue-number> --reason completed",
-    "  gh issue comment <issue-number> --body 'PR #<pr-number> merged. Closing issue.'",
-    "  ```",
-    "- **`CLOSED` (not merged)** \u2014 leave the branch in place; report the closure.",
-    "- **Still `OPEN`** \u2014 auto-merge is pending; report and stop without deleting.",
+    "1. **Read the issue body.** It should include:",
+    "   - The person's name and primary affiliation (company) if known",
+    "   - The requested role from the taxonomy above",
+    "   - The reason the profile was requested (framing \u2014 what does the",
+    "     invoking project want to learn?)",
+    "   - Optional: `<PERSON_SLUG>` override, custom output paths,",
+    "     `refresh_days` override, `force: true` for out-of-cadence refresh",
+    "",
+    "2. **Derive `<PERSON_SLUG>`** if not supplied \u2014 a 2\u20134 word kebab-case",
+    "   summary of the person's name. Disambiguate against any existing",
+    "   slug under `<PROFILES_DIR>/` or `<NOTES_DIR>/` by appending a",
+    "   company or role qualifier (e.g. `jane-doe-acme`).",
+    "",
+    "3. **Check for an existing profile.** If `<PROFILES_DIR>/<PERSON_SLUG>.md`",
+    "   exists, read its `date` frontmatter and apply the refresh cadence",
+    "   rules above before proceeding.",
+    "",
+    "4. **Gather sources.** Prioritize in this order:",
+    "   - The person's own public writing (personal site, blog, newsletter)",
+    "   - Their current employer's bio / leadership page",
+    "   - Public conference talks, podcast appearances, and interviews",
+    "   - Public directories that the invoking issue body authorizes",
+    "     (LinkedIn, GitHub, company profiles, Crunchbase)",
+    "   - Public contributions (open-source repos, published papers)",
+    "",
+    "5. **Write a research-notes file** to",
+    "   `<NOTES_DIR>/<PERSON_SLUG>.notes.md`:",
+    "",
+    "   ```markdown",
+    "   ---",
+    '   title: "Research Notes: <person name>"',
+    "   slug: <PERSON_SLUG>",
+    "   role: <one of the taxonomy values>",
+    "   primary_company: <company name if known>",
+    "   date: YYYY-MM-DD",
+    "   parent_issue: <N>",
+    "   ---",
+    "",
+    "   # Research Notes: <person name>",
+    "",
+    "   ## Framing",
+    "   <why this person was requested and what to learn>",
+    "",
+    "   ## Raw Findings",
+    "   - <finding> \u2014 source: <citation>",
+    "",
+    "   ## Candidate Cross-References",
+    "   - **Companies mentioned:** <list of company names>",
+    "   - **Software mentioned:** <list of product names>",
+    "   - **Meetings mentioned:** <list of meeting identifiers>",
+    "",
+    "   ## Open Questions",
+    "   <anything the notes could not answer from public sources>",
+    "",
+    "   ## Sources",
+    "   - <source URL or file path> \u2014 <date accessed>",
+    "   ```",
+    "",
+    "6. **Create the `people:draft` issue** with `Depends on: #<research-issue>`.",
+    "   Its body references the notes file path, the requested role, and",
+    "   any refresh-mode flags.",
+    "",
+    "7. **Commit and push** the notes file. Close the research issue.",
     "",
     "---",
     "",
-    "## Output Format",
+    "## Phase 2: Draft Profile (`people:draft`)",
     "",
-    "Return a structured report:",
+    "**Goal:** Write the structured person profile from the research notes.",
     "",
-    "```",
-    "PR #<number> \u2014 <title>",
-    "Linked issue: #<issue-number>",
-    "Verdict: AUTO_MERGE_ENABLED | NEEDS_CHANGES | INELIGIBLE | BLOCKED",
+    "**Budget:** No new web searches unless explicitly needed to fill a",
+    "gap the notes flagged. Write one profile file.",
     "",
-    "Acceptance criteria:",
-    "  [x] <criterion> \u2014 <evidence>",
-    "  [~] <criterion> \u2014 partial: <gap>",
-    "  [ ] <criterion> \u2014 missing",
+    "### Steps",
     "",
-    "Findings:",
-    "  - Blocking: <items>",
-    "  - Suggested: <items>",
-    "  - Nitpick: <items>",
+    "1. **Read the research-notes file** referenced in the issue body.",
     "",
-    "Action taken: <enable-auto-merge | commented-on-the-pr | none>",
-    "Branch state: <merged | open | closed>",
-    "Issue state: <closed | open>",
-    "```",
+    "2. **Check for duplicates / refresh.** If `<PROFILES_DIR>/<PERSON_SLUG>.md`",
+    "   already exists:",
+    "   - In refresh mode, open the existing file and update in place,",
+    "     preserving the slug and bumping the `date` frontmatter.",
+    "   - Otherwise, flag a naming collision and stop \u2014 never silently",
+    "     overwrite a non-trivial existing profile.",
+    "",
+    "3. **Write the profile** to `<PROFILES_DIR>/<PERSON_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: "<person name>"',
+    "   slug: <PERSON_SLUG>",
+    "   role: <one of the taxonomy values>",
+    "   primary_company: <company name>",
+    "   date: YYYY-MM-DD",
+    "   refresh_days: <N, default 180>",
+    "   parent_issue: <N>",
+    "   notes: <NOTES_DIR>/<PERSON_SLUG>.notes.md",
+    "   ---",
+    "",
+    "   # <person name>",
+    "",
+    "   ## Summary",
+    "   <2\u20134 sentence elevator description: who they are, what they do,",
+    "   why they matter to this project>",
+    "",
+    "   ## Classification",
+    "   - **Primary role:** <taxonomy value>",
+    "   - **Secondary role (if any):** <taxonomy value or `n/a`>",
+    "   - **Relevance to this project:** <1\u20132 sentences tying the person",
+    "     back to the framing from the notes>",
+    "",
+    "   ## Current Position",
+    "   - **Company:** <primary company \u2014 link to company profile if tracked>",
+    "   - **Title:** <current title>",
+    "   - **Tenure:** <since YYYY, if known>",
+    "   - **Focus areas:** <what they work on day-to-day>",
+    "",
+    "   ## Background",
+    "   - **Prior roles:** <short reverse-chronological list>",
+    "   - **Education / credentials:** <if publicly disclosed>",
+    "   - **Notable contributions:** <open-source, publications, talks>",
+    "",
+    "   ## Expertise Signals",
+    "   <topics they write or speak about \u2014 each bullet cited to a public",
+    "   source>",
+    "",
+    "   ## Positioning / Point of View",
+    "   <how they describe their own work and views \u2014 use their own",
+    "   language, cited, rather than inferred>",
+    "",
+    "   ## Cross-References",
+    "   - **Companies:** <links to `<COMPANIES_DIR>/*.md` for companies",
+    "     already tracked by this project>",
+    "   - **Software:** <links to `<SOFTWARE_DIR>/*.md` for software",
+    "     already tracked by this project>",
+    "   - **Meetings:** <links to `<MEETINGS_DIR>/*.md` for meeting notes",
+    "     this person participated in>",
+    "",
+    "   ## Contact Preferences",
+    "   <public channels only \u2014 company email if listed, social handles,",
+    "   speaker inquiry forms. Never private contact info.>",
+    "",
+    "   ## Risks / Open Questions",
+    "   <what the profile could not answer; flag anything the followup",
+    "   phase should cross-reference>",
+    "",
+    "   ## Sources",
+    "   - <source URL> \u2014 <date accessed>",
+    "   ```",
+    "",
+    "4. **Decide whether a followup issue is warranted.** Create a",
+    "   `people:followup` issue (depending on this draft issue) only if",
+    "   the profile's Candidate Cross-References lists at least one",
+    "   company, software product, or meeting already tracked by the",
+    "   consuming project. Otherwise, note in the draft issue's closing",
+    "   comment that no followup is needed.",
+    "",
+    "5. **Commit and push** the profile file. Close the draft issue.",
     "",
     "---",
     "",
-    "## Rules",
+    "## Phase 3: Followup (`people:followup`)",
     "",
-    "1. **One PR per session** when invoked directly (`/review-pr`). When",
-    "   invoked from the multi-PR loop (`/review-prs`), process every eligible",
-    "   PR in turn.",
-    "2. **Never merge without a linked issue.** If the PR body has no",
-    "   `Closes #N` / `Fixes #N` / `Resolves #N`, comment and stop.",
-    "3. **Never merge with failing CI.** Even if every criterion is met,",
-    "   block on red checks.",
-    "4. **Never bypass review conventions.** Always use `--squash`, `--auto`,",
-    "   and `--delete-branch` for merges. Do not force-merge.",
-    "5. **Do not implement code.** You review, decide, and orchestrate. If",
-    "   the PR needs changes, comment and stop.",
-    "6. **Never push commits to the PR's branch.** If the PR needs changes,",
-    "   comment and stop \u2014 do not attempt to fix it yourself. The PR author",
-    "   owns the branch; pushing to someone else's branch is out of scope.",
-    "7. **In loop mode (`/review-prs`), never stop early.** If any review",
-    "   fails, comment and move to the next PR. Only abort the loop on a",
-    "   fatal error (e.g. `gh` auth failure, network outage).",
-    "8. **Follow CLAUDE.md conventions** for all `git` and `gh` operations."
-  ].join("\n")
-};
-var reviewPrSkill = {
-  name: "review-pr",
-  description: "Review a single pull request against its linked issue's acceptance criteria, then enable squash auto-merge or comment with findings",
-  disableModelInvocation: true,
-  userInvocable: true,
-  context: "fork",
-  agent: "pr-reviewer",
-  platforms: { cursor: { exclude: true } },
-  instructions: [
-    "# Review Pull Request",
+    "**Goal:** Populate the profile's `## Cross-References` section with",
+    "links to existing artifacts \u2014 companies, software, meetings \u2014 that",
+    "the consuming project already tracks.",
     "",
-    "Run a full PR review against the linked issue's acceptance criteria,",
-    "then either enable squash auto-merge or post a findings comment.",
+    "**Budget:** No new web searches. No new downstream research issues.",
+    "Read the candidate cross-references, resolve them against the",
+    "configured directories, update the profile.",
     "",
-    "## Usage",
+    "### Steps",
     "",
-    "/review-pr <pr-number>",
+    "1. **Read the profile file** referenced in the issue body.",
     "",
-    "## What This Skill Does",
+    "2. **Resolve company cross-references.** For each company named in",
+    "   the profile's research notes or body text, look for a matching",
+    "   file under `<COMPANIES_DIR>/`. If found, link it under",
+    "   `## Cross-References > Companies`. If not found, leave a TODO",
+    "   comment naming the company \u2014 the invoking project's team decides",
+    "   whether to kick off a separate company-profile pipeline.",
     "",
-    "1. Runs a pre-flight eligibility filter (mergeable, CI not failing, has linked issue)",
-    "2. Fetches the PR, its diff, CI status, and the linked issue",
-    "3. Builds a checklist from the issue's acceptance criteria",
-    "4. Compares the diff against each criterion",
-    "5. Verifies PR conventions (title, closing keyword, branch name)",
-    "6. Verifies CI is green",
-    "7. **If all checks pass:** enables squash auto-merge (with `--delete-branch`)",
-    "8. **If any check fails:** posts a findings comment via `gh pr comment`",
-    "9. After merge, verifies the linked issue is closed and closes it if not",
-    "10. Cleans up the local branch after merge",
+    "3. **Resolve software cross-references.** Same pattern against",
+    "   `<SOFTWARE_DIR>/`. Link what matches; leave TODOs for what",
+    "   doesn't.",
     "",
-    "## Input",
+    "4. **Resolve meeting cross-references.** For meetings the person",
+    "   participated in, look for a matching file under `<MEETINGS_DIR>/`",
+    "   by date or slug. Link matches; leave TODOs otherwise.",
     "",
-    "Provide the PR number to review. The skill resolves the linked issue from",
-    "the PR body (`Closes #N` / `Fixes #N` / `Resolves #N`).",
+    "5. **Do not open downstream issues.** This pipeline emits no",
+    "   `company:research`, `research:scope`, or similar issues. Cross-",
+    "   references are link-only; downstream research is a separate",
+    "   human decision.",
     "",
-    "## Output",
+    "6. **Commit and push** the updated profile. Close the followup issue.",
     "",
-    "A structured report covering verdict, per-criterion status, findings",
-    "grouped by severity, the action taken, and the final branch / issue state.",
+    "---",
     "",
-    "## Composability",
+    "## Output Boundaries",
     "",
-    "This skill is generic and can be composed with the `github-workflow`",
-    "bundle. The reviewer never implements code and never pushes to the PR",
-    "branch \u2014 it only reviews, decides, and orchestrates merge or comment."
+    "This agent writes **only** to:",
+    "",
+    "- `<NOTES_DIR>/` \u2014 research-notes files (Phase 1)",
+    "- `<PROFILES_DIR>/` \u2014 person profiles (Phase 2, updated in Phase 3)",
+    "",
+    "The pipeline produces **profiles and notes only**. It does not",
+    "create new companies, software evaluations, meeting notes, or any",
+    "other downstream artifacts \u2014 it only links to those that already",
+    "exist under the configured cross-reference directories. Keep this",
+    "boundary clean so the people-profile pipeline stays generic and",
+    "cheap to run.",
+    "",
+    "---",
+    "",
+    "## Rules",
+    "",
+    "- **One person per session.** Never profile two people 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.",
+    "- **Respect privacy.** Never record private contact details, family",
+    "  information, or other non-professional personal data, even when",
+    "  encountered in a public source.",
+    "- **Cross-reference, don't duplicate.** Link to existing company,",
+    "  software, and meeting artifacts rather than re-describing them.",
+    "- **No downstream issue creation.** Phase 3 emits no new research,",
+    "  profile, or requirement issues. Only link.",
+    "- **Refresh, don't fork.** When a profile exists and is past its",
+    "  cadence, update in place rather than creating a new slug."
   ].join("\n")
 };
-var reviewPrsSkill = {
-  name: "review-prs",
-  description: "Loop over every eligible open pull request in the repository and review each one through the full pipeline",
+var profilePersonSkill = {
+  name: "profile-person",
+  description: "Kick off a people-profile pipeline. Creates a people:research issue for the given person and dispatches Phase 1 (Research) in the people-profile-analyst agent.",
   disableModelInvocation: true,
   userInvocable: true,
   context: "fork",
-  agent: "pr-reviewer",
+  agent: "people-profile-analyst",
   platforms: { cursor: { exclude: true } },
   instructions: [
-    "# Review All Eligible Pull Requests",
+    "# Profile Person",
     "",
-    "Run the pr-reviewer pipeline over every eligible open PR in",
-    "**{{repository.owner}}/{{repository.name}}**, one after another, until",
-    "the eligible queue is empty.",
+    "Kick off a people-profile pipeline. Creates a `people:research`",
+    "issue carrying the person's name, role, primary affiliation, and",
+    "framing, then dispatches Phase 1 (Research) in the",
+    "people-profile-analyst agent.",
     "",
     "## Usage",
     "",
-    "/review-prs",
-    "",
-    "## What This Skill Does",
-    "",
-    "### Step 1: Enumerate open PRs",
-    "",
-    "```bash",
-    "gh pr list --json number,title,body,headRefName,mergeable,mergeStateStatus,statusCheckRollup --limit 50",
-    "```",
-    "",
-    "### Step 2: Filter to eligible PRs",
-    "",
-    "A PR is **eligible** when all of the following hold:",
+    "/profile-person <person-name>",
     "",
-    '1. `state == "OPEN"` (implicit from `gh pr list`).',
-    '2. `mergeable == "MERGEABLE"` (no conflicts).',
-    "3. No required check in `statusCheckRollup` has a failing conclusion",
-    "   (`FAILURE`, `TIMED_OUT`, `CANCELLED`, `ERROR`). CI green or still",
-    "   pending is fine.",
-    "4. The PR body contains a linked issue (`Closes #N` / `Fixes #N` /",
-    "   `Resolves #N`, case-insensitive).",
+    "Optional extensions in the issue body:",
+    "- `role: <colleague | customer-contact | vendor-contact |",
+    "   partner-contact | industry-expert | connector>` \u2014 override the",
+    "   default role inference",
+    "- `company: <name>` \u2014 primary company affiliation 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 person slug",
+    "- `refresh_days: <N>` \u2014 override the default 180-day refresh cadence",
+    "- `force: true` \u2014 refresh even if the profile is younger than the",
+    "   cadence window",
+    "- `sources: <list>` \u2014 additional authorized sources beyond public web",
     "",
-    "Drop any PR that fails the filter from the queue. Do not comment on",
-    "them from this skill \u2014 the individual `/review-pr` invocation handles",
-    "the inline rejection comment when run on a specific PR.",
+    "## Default Paths",
     "",
-    "### Step 3: Process each eligible PR",
+    "If the project has no override in `docs/project-context.md` or",
+    "`agentConfig.rules`, outputs land under:",
     "",
-    "For every eligible PR, invoke the full pr-reviewer pipeline",
-    "(Phases 1 through 5) as if `/review-pr <number>` had been called",
-    "directly:",
+    "- `docs/people/notes/<slug>.notes.md`",
+    "- `docs/people/profiles/<slug>.md`",
     "",
-    "- Gather context (diff, checks, linked issue)",
-    "- Compare diff to acceptance criteria",
-    "- Decide and act (enable auto-merge **or** post findings comment)",
-    "- Verify branch / issue cleanup after merge",
+    "Cross-references are resolved against:",
     "",
-    "Continue to the next PR after each one completes. Never stop the loop",
-    "early because a single PR's review failed \u2014 comment and move on.",
+    "- `docs/companies/profiles/`",
+    "- `docs/software/profiles/`",
+    "- `docs/meetings/`",
     "",
-    "### Step 4: Stop when the queue is empty",
+    "## Steps",
     "",
-    "When no eligible PRs remain, emit a final summary listing every PR",
-    "processed and the verdict for each, then stop.",
+    "1. Create a `people:research` issue with `type:people-profile`,",
+    "   `priority:medium`, and `status:ready`. Body must include the",
+    "   person's name, selected role, primary company, framing, and any",
+    "   overrides.",
+    "2. Execute Phase 1 (Research) of the people-profile-analyst agent.",
+    "3. Phase 1 creates the `people:draft` issue. Phase 2 may create a",
+    "   `people:followup` issue. Each downstream issue declares its",
+    "   `Depends on:` predecessor.",
     "",
     "## Output",
     "",
-    "Per-PR structured report (same shape as `/review-pr`), followed by a",
-    "one-line-per-PR summary at the end:",
-    "",
-    "```",
-    "Summary:",
-    "  PR #<n>: <verdict>",
-    "  PR #<n>: <verdict>",
-    "  ...",
-    "Total processed: <count>",
-    "```",
-    "",
-    "## Failure Handling",
-    "",
-    "Only abort the loop on a fatal error (e.g. `gh` authentication failure,",
-    "network outage). A failed review for an individual PR is not fatal \u2014",
-    "comment on that PR and continue with the next."
+    "- A research-notes file under the project's notes directory",
+    "- A single person profile under the profiles directory",
+    "- Cross-references to existing companies, software, and meetings",
+    "  tracked elsewhere in the project",
+    "- This pipeline produces **profiles only** \u2014 it does not create",
+    "  companies, software, meetings, or any other downstream artifacts."
   ].join("\n")
 };
-var prReviewBundle = {
-  name: "pr-review",
-  description: "Pull request review workflow: verifies PRs against their linked issues' acceptance criteria and orchestrates squash-merge, single or looped over all eligible PRs",
-  // Default-apply: the PR review workflow is safe to include everywhere,
-  // and keeping review/merge policy centralised in the pr-reviewer agent
-  // means consumers get consistent behaviour out of the box. Consumers can
-  // still exclude it explicitly via `excludeBundles` if desired.
-  appliesWhen: () => true,
+var peopleProfileBundle = {
+  name: "people-profile",
+  description: "People research and profiling pipeline: research, draft profile, followup. Opt-in only; domain-neutral; filesystem-durable between phases; cross-references existing companies, software, and meeting notes without creating new downstream issues.",
+  appliesWhen: () => false,
   rules: [
     {
-      name: "pr-review-workflow",
-      description: "Describes the /review-pr and /review-prs skills and their delegation to the pr-reviewer sub-agent",
+      name: "people-profile-workflow",
+      description: "Describes the 3-phase people-profile pipeline, the people:* label taxonomy, the cross-reference model, and the boundary against downstream research agents.",
       scope: AGENT_RULE_SCOPE.ALWAYS,
       content: [
-        "# PR Review Workflow",
-        "",
-        "Two skills are available, both backed by the same `pr-reviewer`",
-        "sub-agent:",
-        "",
-        "- **`/review-pr <pr-number>`** \u2014 review a single targeted PR.",
-        "- **`/review-prs`** \u2014 loop over every eligible open PR in the",
-        "  repository and review each one in turn.",
+        "# People Profile Workflow",
         "",
-        "The `pr-reviewer` sub-agent:",
+        "Use `/profile-person <person-name>` to kick off a person",
+        "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 `people:research`, `people:draft`, or",
+        "`people:followup`. All issues carry `type:people-profile`.",
         "",
-        "1. Runs a pre-flight eligibility filter (mergeable, CI not failing,",
-        "   has a linked issue). Ineligible PRs get a short comment and are",
-        "   skipped.",
-        "2. Fetches the PR, its diff, CI status, and the linked issue",
-        "3. Builds a checklist from the issue's acceptance criteria",
-        "4. Verifies the diff satisfies each criterion and that CI is green",
-        "5. **Enables squash auto-merge** (with `--delete-branch`) when all",
-        "   checks pass \u2014 no explicit approval review",
-        "6. **Comments with grouped findings** when any check fails (plain",
-        "   `gh pr comment`, not a formal `--request-changes` review)",
-        "7. After a successful merge, verifies the linked issue is closed",
-        "   and closes it explicitly if the merge commit did not",
-        "8. Cleans up the local branch after merge",
+        "The pipeline produces **person profiles only**. Cross-references",
+        "to companies, software products, and meeting notes are link-only",
+        "\u2014 the followup phase never creates new downstream research,",
+        "profile, or requirement issues.",
         "",
-        "The reviewer **never** implements code and **never** pushes commits",
-        "to a PR's branch \u2014 it only reviews, decides, and orchestrates merge",
-        "or comment. In loop mode, a failed review for one PR never stops",
-        "the loop; the reviewer comments and moves on. See the `pr-reviewer`",
-        "agent definition for the full phase-by-phase contract."
+        "See the `people-profile-analyst` agent definition for full",
+        "workflow details, default paths, the person-role taxonomy, the",
+        "refresh cadence rules, and phase-by-phase instructions."
       ].join("\n"),
       platforms: {
         cursor: { exclude: true }
@@ -3152,368 +3168,1384 @@ var prReviewBundle = {
       tags: ["workflow"]
     }
   ],
-  skills: [reviewPrSkill, reviewPrsSkill],
-  subAgents: [prReviewerSubAgent]
+  skills: [profilePersonSkill],
+  subAgents: [peopleProfileAnalystSubAgent],
+  labels: [
+    {
+      name: "type:people-profile",
+      color: "0E8A16",
+      description: "Work that produces or maintains a person profile or its research notes"
+    },
+    {
+      name: "people:research",
+      color: "C5DEF5",
+      description: "Phase 1: gather public sources about a person into a research-notes file"
+    },
+    {
+      name: "people:draft",
+      color: "BFDADC",
+      description: "Phase 2: write the structured person profile from research notes"
+    },
+    {
+      name: "people:followup",
+      color: "D4C5F9",
+      description: "Phase 3: cross-link the profile to existing companies, software, and meeting notes"
+    }
+  ]
 };
 
-// src/agent/bundles/projen.ts
-var projenBundle = {
-  name: "projen",
-  description: "Projen conventions, synthesis workflow, .projenrc.ts patterns",
-  appliesWhen: (project) => hasDep(project, "projen"),
+// src/pnpm/pnpm-workspace.ts
+import { relative } from "path";
+import { Component, YamlFile } from "projen";
+var MINIMUM_RELEASE_AGE = {
+  ZERO_DAYS: 0,
+  ONE_HOUR: 60,
+  SIX_HOURS: 360,
+  TWELVE_HOURS: 720,
+  ONE_DAY: 1440,
+  TWO_DAYS: 2880,
+  THREE_DAYS: 4320,
+  FOUR_DAYS: 5760,
+  FIVE_DAYS: 7200,
+  SIX_DAYS: 8640,
+  ONE_WEEK: 10080
+};
+var PnpmWorkspace = class _PnpmWorkspace extends Component {
+  /**
+   * Get the pnpm workspace component of a project. If it does not exist,
+   * return undefined.
+   *
+   * @param project
+   * @returns
+   */
+  static of(project) {
+    const isDefined = (c) => c instanceof _PnpmWorkspace;
+    return project.root.components.find(isDefined);
+  }
+  constructor(project, options = {}) {
+    super(project);
+    project.tryFindObjectFile("package.json")?.addDeletionOverride("pnpm");
+    this.fileName = options.fileName ?? "pnpm-workspace.yaml";
+    this.minimumReleaseAge = options.minimumReleaseAge ?? MINIMUM_RELEASE_AGE.ONE_DAY;
+    this.minimumReleaseAgeExclude = options.minimumReleaseAgeExclude ? ["@codedrifters/*", ...options.minimumReleaseAgeExclude] : ["@codedrifters/*"];
+    this.onlyBuiltDependencies = options.onlyBuiltDependencies ? options.onlyBuiltDependencies : [];
+    this.ignoredBuiltDependencies = options.ignoredBuiltDependencies ? options.ignoredBuiltDependencies : [];
+    this.subprojects = options.subprojects ?? [];
+    this.defaultCatalog = options.defaultCatalog;
+    this.namedCatalogs = options.namedCatalogs;
+    project.addPackageIgnore(this.fileName);
+    new YamlFile(this.project, this.fileName, {
+      obj: () => {
+        const pnpmConfig = {};
+        const packages = new Array();
+        for (const subproject of project.subprojects) {
+          packages.push(relative(this.project.outdir, subproject.outdir));
+        }
+        const packageSet = new Set(packages);
+        for (const subprojectPath of this.subprojects) {
+          packageSet.add(subprojectPath);
+        }
+        if (this.subprojects.length > 0) {
+          packages.length = 0;
+          packages.push(...packageSet);
+        }
+        pnpmConfig.minimumReleaseAge = this.minimumReleaseAge;
+        if (this.minimumReleaseAgeExclude.length > 0) {
+          pnpmConfig.minimumReleaseAgeExclude = this.minimumReleaseAgeExclude;
+        }
+        if (this.onlyBuiltDependencies.length > 0) {
+          pnpmConfig.onlyBuiltDependencies = this.onlyBuiltDependencies;
+        }
+        if (this.ignoredBuiltDependencies.length > 0) {
+          pnpmConfig.ignoreBuiltDependencies = this.ignoredBuiltDependencies;
+        }
+        if (this.defaultCatalog && Object.keys(this.defaultCatalog).length > 0) {
+          pnpmConfig.catalog = this.defaultCatalog;
+        }
+        if (this.namedCatalogs && Object.keys(this.namedCatalogs).length > 0) {
+          pnpmConfig.namedCatalogs = this.namedCatalogs;
+        }
+        return {
+          ...packages.length > 0 ? { packages } : {},
+          ...pnpmConfig ? { ...pnpmConfig } : {}
+        };
+      }
+    });
+  }
+};
+var MIMIMUM_RELEASE_AGE = MINIMUM_RELEASE_AGE;
+
+// src/agent/bundles/pnpm.ts
+var pnpmBundle = {
+  name: "pnpm",
+  description: "PNPM workspace rules and dependency management conventions",
+  appliesWhen: (project) => hasComponent(project, PnpmWorkspace),
   rules: [
     {
-      name: "development-commands",
-      description: "Projen development commands for building, testing, linting, and validating changes",
-      scope: AGENT_RULE_SCOPE.ALWAYS,
+      name: "pnpm-workspace",
+      description: "PNPM workspace and dependency management conventions",
+      scope: AGENT_RULE_SCOPE.FILE_PATTERN,
+      filePatterns: ["package.json", "pnpm-workspace.yaml", "pnpm-lock.yaml"],
       content: [
-        "# Development Commands",
-        "",
-        "This project uses Projen to manage configuration and Turborepo to orchestrate builds across the monorepo. Run all commands from the **repository root** unless otherwise noted.",
-        "",
-        "## Synthesizing Projen Configuration",
-        "",
-        "After modifying any file in `projenrc/` or `.projenrc.ts`, regenerate project files:",
-        "",
-        "```sh",
-        "npx projen",
-        "pnpm install",
-        "```",
-        "",
-        "Both steps are required \u2014 `npx projen` regenerates files, `pnpm install` updates the lockfile to match.",
-        "",
-        "## Building",
-        "",
-        "**Full monorepo build** (compile + test + package, all sub-packages via Turborepo):",
-        "",
-        "```sh",
-        "pnpm build:all",
-        "```",
-        "",
-        "**Root project only** (synthesize + compile + lint):",
-        "",
-        "```sh",
-        "pnpm build",
-        "```",
-        "",
-        "**Single sub-package** (compile only):",
-        "",
-        "```sh",
-        "pnpm --filter @codedrifters/<package> compile",
-        "```",
-        "",
-        "Replace `<package>` with `configulator`, `constructs`, or `utils`.",
-        "",
-        "## Testing",
-        "",
-        "**Run tests for a single sub-package:**",
-        "",
-        "```sh",
-        "pnpm --filter @codedrifters/<package> test",
-        "```",
-        "",
-        "This runs ESLint + Vitest for the specified package.",
-        "",
-        "**Run only Vitest (skip lint) in a sub-package:**",
-        "",
-        "```sh",
-        "cd packages/@codedrifters/<package>",
-        "pnpm exec vitest run",
-        "```",
-        "",
-        "**Run a specific test file:**",
-        "",
-        "```sh",
-        "cd packages/@codedrifters/<package>",
-        "pnpm exec vitest run src/path/to/file.test.ts",
-        "```",
-        "",
-        "## Linting",
-        "",
-        "**Lint the root project:**",
-        "",
-        "```sh",
-        "pnpm eslint",
-        "```",
-        "",
-        "**Lint a single sub-package:**",
-        "",
-        "```sh",
-        "pnpm --filter @codedrifters/<package> eslint",
-        "```",
-        "",
-        "## Resetting Build Artifacts",
-        "",
-        "**Reset everything** (all packages + root):",
-        "",
-        "```sh",
-        "pnpm reset:all",
-        "```",
+        "# PNPM Workspace Conventions",
         "",
-        "**Reset root only:**",
+        "## Package Management",
         "",
-        "```sh",
-        "pnpm reset",
-        "```",
+        "- Use **PNPM** for package management",
+        "- Workspace configuration in `pnpm-workspace.yaml`",
+        "- Dependencies managed through Projen, not directly in `package.json`",
+        "- **Always use workspace dependencies** (`workspace:*` or `workspace:^`) for packages within this monorepo",
+        "- Never use published NPM versions of internal packages; always reference the local workspace version",
         "",
-        "## Validating Changes Are Complete",
+        "## Dependency Management",
         "",
-        "After finishing implementation work, validate that changes are correct by running the appropriate commands depending on what was changed:",
+        "**DO:**",
+        "- Configure dependencies in Projen configuration files (`.projenrc.ts` or `projenrc/*.ts`)",
+        "- Add dependencies to `deps`, `devDeps`, or `peerDeps` arrays in project configuration",
+        '- Use catalog dependencies when available (e.g., `"aws-cdk-lib@catalog:"`)',
+        "- Ask the user to run `npx projen` and `pnpm install` after updating dependency configuration",
         "",
-        "1. **Projen config changes** (`projenrc/`, `.projenrc.ts`):",
-        "   - Run `npx projen` then `pnpm install`",
-        "   - Verify no unexpected generated file changes with `git diff`",
+        "**DO NOT:**",
+        "- Run `npm install some-package`",
+        "- Run `pnpm add some-package`",
+        "- Run `yarn add some-package`",
+        "- Manually edit `package.json` dependencies",
         "",
-        "2. **Source code changes** (in a sub-package):",
-        "   - Compile: `pnpm --filter @codedrifters/<package> compile`",
-        "   - Test: `pnpm --filter @codedrifters/<package> test`",
-        "",
-        "3. **Changes spanning multiple packages**:",
-        "   - Run `pnpm build:all` to validate the full monorepo build",
-        "",
-        "4. **Root-level changes** (projenrc, root config):",
-        "   - Run `pnpm build` to validate root synthesis + compilation + lint",
-        "",
-        "## Command Reference",
-        "",
-        "| Task | Command |",
-        "|------|---------|",
-        "| Synthesize projen | `npx projen` |",
-        "| Install deps | `pnpm install` |",
-        "| Full monorepo build | `pnpm build:all` |",
-        "| Root build only | `pnpm build` |",
-        "| Compile one package | `pnpm --filter @codedrifters/<pkg> compile` |",
-        "| Test one package | `pnpm --filter @codedrifters/<pkg> test` |",
-        "| Lint one package | `pnpm --filter @codedrifters/<pkg> eslint` |",
-        "| Lint root | `pnpm eslint` |",
-        "| Reset all artifacts | `pnpm reset:all` |"
+        "Manual package installation creates conflicts with Projen-managed files."
       ].join("\n"),
       tags: ["workflow"]
-    },
+    }
+  ]
+};
+
+// src/agent/bundles/pr-review.ts
+var prReviewerSubAgent = {
+  name: "pr-reviewer",
+  description: "Reviews a pull request against its linked issue's acceptance criteria, then enables squash auto-merge or comments with findings",
+  model: AGENT_MODEL.POWERFUL,
+  maxTurns: 40,
+  platforms: { cursor: { exclude: true } },
+  prompt: [
+    "# PR Reviewer Agent",
+    "",
+    "You review a single pull request in **{{repository.owner}}/{{repository.name}}**",
+    "against its linked issue's acceptance criteria, verify code quality and",
+    "convention compliance, and then either enable squash auto-merge or leave",
+    "a review comment with findings. You handle exactly **one PR per session**",
+    "unless invoked from the multi-PR loop skill (`/review-prs`), in which case",
+    "you process each eligible PR in turn.",
+    "",
+    "---",
+    "",
+    ...PROJECT_CONTEXT_READER_SECTION,
+    "## Phase 1: Identify the PR",
+    "",
+    "If a PR number was provided in your instructions, use that. Otherwise stop",
+    "and report that you need a PR number \u2014 do not pick one yourself.",
+    "",
+    "## Phase 1.5: Pre-flight Eligibility Filter",
+    "",
+    "Before spending turns on a full review, run a cheap eligibility check:",
+    "",
+    "```bash",
+    "gh pr view <pr-number> --json number,title,body,headRefName,mergeable,mergeStateStatus,statusCheckRollup",
+    "```",
+    "",
+    "The PR is **eligible** only when **all** of the following hold:",
+    "",
+    '1. `mergeable == "MERGEABLE"` (no merge conflicts).',
+    "2. No **failing** required checks in `statusCheckRollup` \u2014 CI must be",
+    "   green or still pending. Any `FAILURE`, `TIMED_OUT`, `CANCELLED`, or",
+    "   `ERROR` conclusion on a required check disqualifies the PR.",
+    "3. The PR body contains a linked issue via one of the closing keywords:",
+    "   `Closes #N`, `Fixes #N`, or `Resolves #N` (case-insensitive).",
+    "",
+    "If **any** check fails, post a short comment explaining the reason and",
+    "stop. Do not proceed to full review.",
+    "",
+    "```bash",
+    "gh pr comment <pr-number> --body '<reason>'",
+    "```",
+    "",
+    "Typical reasons:",
+    "",
+    "- `Not reviewable: merge conflicts \u2014 please rebase onto the default branch.`",
+    "- `Not reviewable: required CI check <name> is failing.`",
+    "- `Not reviewable: PR body is missing a linked issue (Closes #N / Fixes #N / Resolves #N).`",
+    "",
+    "## Phase 2: Gather Context",
+    "",
+    "```bash",
+    "gh pr view <pr-number> --json number,title,body,headRefName,baseRefName,isDraft,state,labels,reviews",
+    "gh pr diff <pr-number>",
+    "gh pr checks <pr-number>",
+    "```",
+    "",
+    "Extract the linked issue number from the PR body using the closing keywords",
+    "(`Closes #N`, `Fixes #N`, or `Resolves #N`) identified in Phase 1.5.",
+    "",
+    "Then fetch the linked issue:",
+    "",
+    "```bash",
+    "gh issue view <issue-number>",
+    "```",
+    "",
+    "## Phase 3: Compare Diff to Acceptance Criteria",
+    "",
+    "Read the issue body for an **Acceptance Criteria** (or equivalent) section.",
+    "Build a checklist from it. For each item:",
+    "",
+    "1. Locate the changes in the diff that satisfy it.",
+    "2. Mark it as `met`, `partial`, or `missing`.",
+    "3. Record the specific files / functions / tests that provide evidence.",
+    "",
+    "Also evaluate:",
+    "",
+    "- **Convention compliance** \u2014 PR title uses a conventional commit prefix,",
+    "  body includes a closing keyword, branch name follows project conventions",
+    "- **Test coverage** \u2014 new or changed behavior has tests",
+    "- **CI status** \u2014 `gh pr checks` reports all required checks passing",
+    "- **Scope creep** \u2014 diff stays within the issue's stated scope",
+    "",
+    "## Phase 4: Decide and Act",
+    "",
+    "### If all acceptance criteria are met and CI is green",
+    "",
+    "Enable squash auto-merge with branch deletion. This queues the merge to",
+    "happen once required checks pass; no separate approval review is needed.",
+    "",
+    "```bash",
+    "gh pr merge <pr-number> --auto --squash --delete-branch \\",
+    "  --subject '<conventional-commit-title>' \\",
+    "  --body '<extended-description>'",
+    "```",
+    "",
+    "The squash-merge subject should follow conventional commit format (e.g.",
+    "`feat(scope): description`). The body should bullet the changes and end",
+    "with `Closes #<issue-number>`.",
+    "",
+    "### If any criterion is missing, partial, or CI is failing",
+    "",
+    "Post a plain comment (not a formal review block) with grouped findings:",
+    "",
+    "```bash",
+    "gh pr comment <pr-number> --body '<grouped findings>'",
+    "```",
+    "",
+    "Group findings by severity (**Blocking** / **Suggested** / **Nitpick**).",
+    "For each blocking finding, cite the unmet acceptance criterion and the",
+    "file or function the gap lives in. Do **not** merge, and do **not** push",
+    "any commits to the PR's branch.",
+    "",
+    "Rationale for using a plain comment rather than `gh pr review",
+    "--request-changes`: it is lighter-weight, doesn't require the author to",
+    "dismiss a formal review, and composes cleanly with the multi-PR loop.",
+    "",
+    "## Phase 5: Branch Cleanup and Issue Closure Verification",
+    "",
+    "Auto-merge may not be immediate. Poll the PR state up to 10 times, waiting",
+    "30 seconds between polls:",
+    "",
+    "```bash",
+    "gh pr view <pr-number> --json state --jq '.state'",
+    "```",
+    "",
+    "- **`MERGED`** \u2014 clean up locally **and** verify the linked issue closed:",
+    "  ```bash",
+    "  git checkout {{repository.defaultBranch}}",
+    "  git pull origin {{repository.defaultBranch}}",
+    "  git fetch --prune origin",
+    "  git branch -d <branch-name> 2>/dev/null || git branch -D <branch-name> 2>/dev/null || true",
+    "  ```",
+    "  Then check the linked issue state:",
+    "  ```bash",
+    "  gh issue view <issue-number> --json state --jq '.state'",
+    "  ```",
+    "  If the issue is **not** `CLOSED`, close it explicitly (this covers",
+    "  malformed or missing closing keywords on the merge commit):",
+    "  ```bash",
+    "  gh issue close <issue-number> --reason completed",
+    "  gh issue comment <issue-number> --body 'PR #<pr-number> merged. Closing issue.'",
+    "  ```",
+    "- **`CLOSED` (not merged)** \u2014 leave the branch in place; report the closure.",
+    "- **Still `OPEN`** \u2014 auto-merge is pending; report and stop without deleting.",
+    "",
+    "---",
+    "",
+    "## Output Format",
+    "",
+    "Return a structured report:",
+    "",
+    "```",
+    "PR #<number> \u2014 <title>",
+    "Linked issue: #<issue-number>",
+    "Verdict: AUTO_MERGE_ENABLED | NEEDS_CHANGES | INELIGIBLE | BLOCKED",
+    "",
+    "Acceptance criteria:",
+    "  [x] <criterion> \u2014 <evidence>",
+    "  [~] <criterion> \u2014 partial: <gap>",
+    "  [ ] <criterion> \u2014 missing",
+    "",
+    "Findings:",
+    "  - Blocking: <items>",
+    "  - Suggested: <items>",
+    "  - Nitpick: <items>",
+    "",
+    "Action taken: <enable-auto-merge | commented-on-the-pr | none>",
+    "Branch state: <merged | open | closed>",
+    "Issue state: <closed | open>",
+    "```",
+    "",
+    "---",
+    "",
+    "## Rules",
+    "",
+    "1. **One PR per session** when invoked directly (`/review-pr`). When",
+    "   invoked from the multi-PR loop (`/review-prs`), process every eligible",
+    "   PR in turn.",
+    "2. **Never merge without a linked issue.** If the PR body has no",
+    "   `Closes #N` / `Fixes #N` / `Resolves #N`, comment and stop.",
+    "3. **Never merge with failing CI.** Even if every criterion is met,",
+    "   block on red checks.",
+    "4. **Never bypass review conventions.** Always use `--squash`, `--auto`,",
+    "   and `--delete-branch` for merges. Do not force-merge.",
+    "5. **Do not implement code.** You review, decide, and orchestrate. If",
+    "   the PR needs changes, comment and stop.",
+    "6. **Never push commits to the PR's branch.** If the PR needs changes,",
+    "   comment and stop \u2014 do not attempt to fix it yourself. The PR author",
+    "   owns the branch; pushing to someone else's branch is out of scope.",
+    "7. **In loop mode (`/review-prs`), never stop early.** If any review",
+    "   fails, comment and move to the next PR. Only abort the loop on a",
+    "   fatal error (e.g. `gh` auth failure, network outage).",
+    "8. **Follow CLAUDE.md conventions** for all `git` and `gh` operations."
+  ].join("\n")
+};
+var reviewPrSkill = {
+  name: "review-pr",
+  description: "Review a single pull request against its linked issue's acceptance criteria, then enable squash auto-merge or comment with findings",
+  disableModelInvocation: true,
+  userInvocable: true,
+  context: "fork",
+  agent: "pr-reviewer",
+  platforms: { cursor: { exclude: true } },
+  instructions: [
+    "# Review Pull Request",
+    "",
+    "Run a full PR review against the linked issue's acceptance criteria,",
+    "then either enable squash auto-merge or post a findings comment.",
+    "",
+    "## Usage",
+    "",
+    "/review-pr <pr-number>",
+    "",
+    "## What This Skill Does",
+    "",
+    "1. Runs a pre-flight eligibility filter (mergeable, CI not failing, has linked issue)",
+    "2. Fetches the PR, its diff, CI status, and the linked issue",
+    "3. Builds a checklist from the issue's acceptance criteria",
+    "4. Compares the diff against each criterion",
+    "5. Verifies PR conventions (title, closing keyword, branch name)",
+    "6. Verifies CI is green",
+    "7. **If all checks pass:** enables squash auto-merge (with `--delete-branch`)",
+    "8. **If any check fails:** posts a findings comment via `gh pr comment`",
+    "9. After merge, verifies the linked issue is closed and closes it if not",
+    "10. Cleans up the local branch after merge",
+    "",
+    "## Input",
+    "",
+    "Provide the PR number to review. The skill resolves the linked issue from",
+    "the PR body (`Closes #N` / `Fixes #N` / `Resolves #N`).",
+    "",
+    "## Output",
+    "",
+    "A structured report covering verdict, per-criterion status, findings",
+    "grouped by severity, the action taken, and the final branch / issue state.",
+    "",
+    "## Composability",
+    "",
+    "This skill is generic and can be composed with the `github-workflow`",
+    "bundle. The reviewer never implements code and never pushes to the PR",
+    "branch \u2014 it only reviews, decides, and orchestrates merge or comment."
+  ].join("\n")
+};
+var reviewPrsSkill = {
+  name: "review-prs",
+  description: "Loop over every eligible open pull request in the repository and review each one through the full pipeline",
+  disableModelInvocation: true,
+  userInvocable: true,
+  context: "fork",
+  agent: "pr-reviewer",
+  platforms: { cursor: { exclude: true } },
+  instructions: [
+    "# Review All Eligible Pull Requests",
+    "",
+    "Run the pr-reviewer pipeline over every eligible open PR in",
+    "**{{repository.owner}}/{{repository.name}}**, one after another, until",
+    "the eligible queue is empty.",
+    "",
+    "## Usage",
+    "",
+    "/review-prs",
+    "",
+    "## What This Skill Does",
+    "",
+    "### Step 1: Enumerate open PRs",
+    "",
+    "```bash",
+    "gh pr list --json number,title,body,headRefName,mergeable,mergeStateStatus,statusCheckRollup --limit 50",
+    "```",
+    "",
+    "### Step 2: Filter to eligible PRs",
+    "",
+    "A PR is **eligible** when all of the following hold:",
+    "",
+    '1. `state == "OPEN"` (implicit from `gh pr list`).',
+    '2. `mergeable == "MERGEABLE"` (no conflicts).',
+    "3. No required check in `statusCheckRollup` has a failing conclusion",
+    "   (`FAILURE`, `TIMED_OUT`, `CANCELLED`, `ERROR`). CI green or still",
+    "   pending is fine.",
+    "4. The PR body contains a linked issue (`Closes #N` / `Fixes #N` /",
+    "   `Resolves #N`, case-insensitive).",
+    "",
+    "Drop any PR that fails the filter from the queue. Do not comment on",
+    "them from this skill \u2014 the individual `/review-pr` invocation handles",
+    "the inline rejection comment when run on a specific PR.",
+    "",
+    "### Step 3: Process each eligible PR",
+    "",
+    "For every eligible PR, invoke the full pr-reviewer pipeline",
+    "(Phases 1 through 5) as if `/review-pr <number>` had been called",
+    "directly:",
+    "",
+    "- Gather context (diff, checks, linked issue)",
+    "- Compare diff to acceptance criteria",
+    "- Decide and act (enable auto-merge **or** post findings comment)",
+    "- Verify branch / issue cleanup after merge",
+    "",
+    "Continue to the next PR after each one completes. Never stop the loop",
+    "early because a single PR's review failed \u2014 comment and move on.",
+    "",
+    "### Step 4: Stop when the queue is empty",
+    "",
+    "When no eligible PRs remain, emit a final summary listing every PR",
+    "processed and the verdict for each, then stop.",
+    "",
+    "## Output",
+    "",
+    "Per-PR structured report (same shape as `/review-pr`), followed by a",
+    "one-line-per-PR summary at the end:",
+    "",
+    "```",
+    "Summary:",
+    "  PR #<n>: <verdict>",
+    "  PR #<n>: <verdict>",
+    "  ...",
+    "Total processed: <count>",
+    "```",
+    "",
+    "## Failure Handling",
+    "",
+    "Only abort the loop on a fatal error (e.g. `gh` authentication failure,",
+    "network outage). A failed review for an individual PR is not fatal \u2014",
+    "comment on that PR and continue with the next."
+  ].join("\n")
+};
+var prReviewBundle = {
+  name: "pr-review",
+  description: "Pull request review workflow: verifies PRs against their linked issues' acceptance criteria and orchestrates squash-merge, single or looped over all eligible PRs",
+  // Default-apply: the PR review workflow is safe to include everywhere,
+  // and keeping review/merge policy centralised in the pr-reviewer agent
+  // means consumers get consistent behaviour out of the box. Consumers can
+  // still exclude it explicitly via `excludeBundles` if desired.
+  appliesWhen: () => true,
+  rules: [
+    {
+      name: "pr-review-workflow",
+      description: "Describes the /review-pr and /review-prs skills and their delegation to the pr-reviewer sub-agent",
+      scope: AGENT_RULE_SCOPE.ALWAYS,
+      content: [
+        "# PR Review Workflow",
+        "",
+        "Two skills are available, both backed by the same `pr-reviewer`",
+        "sub-agent:",
+        "",
+        "- **`/review-pr <pr-number>`** \u2014 review a single targeted PR.",
+        "- **`/review-prs`** \u2014 loop over every eligible open PR in the",
+        "  repository and review each one in turn.",
+        "",
+        "The `pr-reviewer` sub-agent:",
+        "",
+        "1. Runs a pre-flight eligibility filter (mergeable, CI not failing,",
+        "   has a linked issue). Ineligible PRs get a short comment and are",
+        "   skipped.",
+        "2. Fetches the PR, its diff, CI status, and the linked issue",
+        "3. Builds a checklist from the issue's acceptance criteria",
+        "4. Verifies the diff satisfies each criterion and that CI is green",
+        "5. **Enables squash auto-merge** (with `--delete-branch`) when all",
+        "   checks pass \u2014 no explicit approval review",
+        "6. **Comments with grouped findings** when any check fails (plain",
+        "   `gh pr comment`, not a formal `--request-changes` review)",
+        "7. After a successful merge, verifies the linked issue is closed",
+        "   and closes it explicitly if the merge commit did not",
+        "8. Cleans up the local branch after merge",
+        "",
+        "The reviewer **never** implements code and **never** pushes commits",
+        "to a PR's branch \u2014 it only reviews, decides, and orchestrates merge",
+        "or comment. In loop mode, a failed review for one PR never stops",
+        "the loop; the reviewer comments and moves on. See the `pr-reviewer`",
+        "agent definition for the full phase-by-phase contract."
+      ].join("\n"),
+      platforms: {
+        cursor: { exclude: true }
+      },
+      tags: ["workflow"]
+    }
+  ],
+  skills: [reviewPrSkill, reviewPrsSkill],
+  subAgents: [prReviewerSubAgent]
+};
+
+// src/agent/bundles/projen.ts
+var projenBundle = {
+  name: "projen",
+  description: "Projen conventions, synthesis workflow, .projenrc.ts patterns",
+  appliesWhen: (project) => hasDep(project, "projen"),
+  rules: [
+    {
+      name: "development-commands",
+      description: "Projen development commands for building, testing, linting, and validating changes",
+      scope: AGENT_RULE_SCOPE.ALWAYS,
+      content: [
+        "# Development Commands",
+        "",
+        "This project uses Projen to manage configuration and Turborepo to orchestrate builds across the monorepo. Run all commands from the **repository root** unless otherwise noted.",
+        "",
+        "## Synthesizing Projen Configuration",
+        "",
+        "After modifying any file in `projenrc/` or `.projenrc.ts`, regenerate project files:",
+        "",
+        "```sh",
+        "npx projen",
+        "pnpm install",
+        "```",
+        "",
+        "Both steps are required \u2014 `npx projen` regenerates files, `pnpm install` updates the lockfile to match.",
+        "",
+        "## Building",
+        "",
+        "**Full monorepo build** (compile + test + package, all sub-packages via Turborepo):",
+        "",
+        "```sh",
+        "pnpm build:all",
+        "```",
+        "",
+        "**Root project only** (synthesize + compile + lint):",
+        "",
+        "```sh",
+        "pnpm build",
+        "```",
+        "",
+        "**Single sub-package** (compile only):",
+        "",
+        "```sh",
+        "pnpm --filter @codedrifters/<package> compile",
+        "```",
+        "",
+        "Replace `<package>` with `configulator`, `constructs`, or `utils`.",
+        "",
+        "## Testing",
+        "",
+        "**Run tests for a single sub-package:**",
+        "",
+        "```sh",
+        "pnpm --filter @codedrifters/<package> test",
+        "```",
+        "",
+        "This runs ESLint + Vitest for the specified package.",
+        "",
+        "**Run only Vitest (skip lint) in a sub-package:**",
+        "",
+        "```sh",
+        "cd packages/@codedrifters/<package>",
+        "pnpm exec vitest run",
+        "```",
+        "",
+        "**Run a specific test file:**",
+        "",
+        "```sh",
+        "cd packages/@codedrifters/<package>",
+        "pnpm exec vitest run src/path/to/file.test.ts",
+        "```",
+        "",
+        "## Linting",
+        "",
+        "**Lint the root project:**",
+        "",
+        "```sh",
+        "pnpm eslint",
+        "```",
+        "",
+        "**Lint a single sub-package:**",
+        "",
+        "```sh",
+        "pnpm --filter @codedrifters/<package> eslint",
+        "```",
+        "",
+        "## Resetting Build Artifacts",
+        "",
+        "**Reset everything** (all packages + root):",
+        "",
+        "```sh",
+        "pnpm reset:all",
+        "```",
+        "",
+        "**Reset root only:**",
+        "",
+        "```sh",
+        "pnpm reset",
+        "```",
+        "",
+        "## Validating Changes Are Complete",
+        "",
+        "After finishing implementation work, validate that changes are correct by running the appropriate commands depending on what was changed:",
+        "",
+        "1. **Projen config changes** (`projenrc/`, `.projenrc.ts`):",
+        "   - Run `npx projen` then `pnpm install`",
+        "   - Verify no unexpected generated file changes with `git diff`",
+        "",
+        "2. **Source code changes** (in a sub-package):",
+        "   - Compile: `pnpm --filter @codedrifters/<package> compile`",
+        "   - Test: `pnpm --filter @codedrifters/<package> test`",
+        "",
+        "3. **Changes spanning multiple packages**:",
+        "   - Run `pnpm build:all` to validate the full monorepo build",
+        "",
+        "4. **Root-level changes** (projenrc, root config):",
+        "   - Run `pnpm build` to validate root synthesis + compilation + lint",
+        "",
+        "## Command Reference",
+        "",
+        "| Task | Command |",
+        "|------|---------|",
+        "| Synthesize projen | `npx projen` |",
+        "| Install deps | `pnpm install` |",
+        "| Full monorepo build | `pnpm build:all` |",
+        "| Root build only | `pnpm build` |",
+        "| Compile one package | `pnpm --filter @codedrifters/<pkg> compile` |",
+        "| Test one package | `pnpm --filter @codedrifters/<pkg> test` |",
+        "| Lint one package | `pnpm --filter @codedrifters/<pkg> eslint` |",
+        "| Lint root | `pnpm eslint` |",
+        "| Reset all artifacts | `pnpm reset:all` |"
+      ].join("\n"),
+      tags: ["workflow"]
+    },
+    {
+      name: "agent-rules-customization",
+      description: "How to customize agent rules for this repo via the Projen project definition",
+      scope: AGENT_RULE_SCOPE.FILE_PATTERN,
+      filePatterns: [
+        "projenrc/**/*.ts",
+        ".projenrc.ts",
+        ".claude/rules/*.md",
+        ".cursor/rules/*.mdc",
+        "CLAUDE.md"
+      ],
+      content: [
+        "# Customizing Agent Rules",
+        "",
+        "Agent rules for Claude and Cursor are **generated** by configulator's `AgentConfig` component. The generated output files (`.claude/rules/`, `.cursor/rules/`, `CLAUDE.md`) must not be edited directly \u2014 they are overwritten on every `npx projen` run.",
+        "",
+        "## Adding Repo-Specific Rules",
+        "",
+        "Rules that only apply to this repository should be added to the `agentConfig.rules` array in the Projen project definition (`.projenrc.ts` or `projenrc/*.ts`):",
+        "",
+        "```typescript",
+        "agentConfig: {",
+        "  rules: [",
+        "    {",
+        "      name: 'my-repo-rule',",
+        "      description: 'What this rule does',",
+        "      scope: AGENT_RULE_SCOPE.ALWAYS, // or FILE_PATTERN with filePatterns",
+        "      content: '# My Rule\\n\\n- Guideline 1\\n- Guideline 2',",
+        "    },",
+        "  ],",
+        "}",
+        "```",
+        "",
+        "## Extending Existing Bundle Rules",
+        "",
+        "To append repo-specific content to a rule provided by a configulator bundle (without replacing it), use `agentConfig.ruleExtensions`:",
+        "",
+        "```typescript",
+        "agentConfig: {",
+        "  ruleExtensions: {",
+        "    'typescript-conventions': '## Additional Guidelines\\n\\n- My custom guideline',",
+        "  },",
+        "}",
+        "```",
+        "",
+        "## After Any Change",
+        "",
+        "Run `npx projen` then `pnpm install` to regenerate the output files."
+      ].join("\n"),
+      tags: ["workflow"]
+    },
+    {
+      name: "projen-conventions",
+      description: "Projen configuration patterns and best practices",
+      scope: AGENT_RULE_SCOPE.FILE_PATTERN,
+      filePatterns: ["projenrc/**/*.ts", ".projenrc.ts"],
+      content: [
+        "# Projen Conventions",
+        "",
+        "## Configuration Management",
+        "",
+        "- **Never edit generated files** (`package.json`, `tsconfig.json`, etc. marked with `// ~~ Generated by projen`)",
+        "- Edit Projen configuration in:",
+        "  - `.projenrc.ts` (root)",
+        "  - `projenrc/*.ts` (package-specific)",
+        "- After making Projen changes, run `npx projen` to synthesize",
+        "",
+        "## Workspace Dependencies",
+        "",
+        "When adding dependencies between packages in a monorepo:",
+        "",
+        '- Use the workspace protocol: `project.addDeps("@org/sibling-pkg@workspace:*")`',
+        "- This ensures the local version is always resolved, not a registry version",
+        '- For dev dependencies: `project.addDevDeps("@org/sibling-pkg@workspace:*")`',
+        "",
+        "## The `configureMyProject` Pattern",
+        "",
+        "Each package should expose a `configureMyProject(options)` factory function that creates and configures its Projen project:",
+        "",
+        "```typescript",
+        "export function configureMyProject(",
+        "  options: MyProjectOptions,",
+        "): TypeScriptProject {",
+        "  const project = new TypeScriptProject({",
+        "    ...options,",
+        "    // package-specific defaults",
+        "  });",
+        "",
+        "  // Attach components, configure rules, etc.",
+        "  return project;",
+        "}",
+        "```",
+        "",
+        "This pattern keeps `.projenrc.ts` clean and makes package configuration reusable and testable.",
+        "",
+        "## Custom Projen Components",
+        "",
+        "All custom components must extend `Component` from Projen and use a static `.of()` factory for discovery:",
+        "",
+        "```typescript",
+        "export class MyComponent extends Component {",
+        "  public static of(project: Project): MyComponent | undefined {",
+        "    const isDefined = (c: Component): c is MyComponent =>",
+        "      c instanceof MyComponent;",
+        "    return project.components.find(isDefined);",
+        "  }",
+        "",
+        "  constructor(project: Project, options: MyComponentOptions) {",
+        "    super(project);",
+        "    // Implementation",
+        "  }",
+        "}",
+        "```",
+        "",
+        "## Component Authoring",
+        "",
+        "- Export project types and utilities from `index.ts`",
+        "- Follow Projen's component lifecycle patterns",
+        "- Use `merge` from `ts-deepmerge` for deep merging configuration objects",
+        "- Components should be reusable and configurable; use TypeScript interfaces for component options",
+        "- Provide sensible defaults while allowing customization",
+        "- Document public APIs with minimal JSDoc; put extended documentation in markdown",
+        "",
+        "## Dependencies",
+        "",
+        "- Dependencies managed through Projen configuration, not directly in `package.json`",
+        '- Use catalog dependencies when available (e.g., `"projen": "catalog:"`)',
+        "- Peer dependencies for shared libraries (e.g., `constructs`, `projen`, `aws-cdk-lib`)",
+        '- Use workspace protocol for internal packages: `"@org/pkg@workspace:*"`'
+      ].join("\n"),
+      tags: ["workflow"]
+    }
+  ]
+};
+
+// src/agent/bundles/requirements-analyst.ts
+var requirementsAnalystSubAgent = {
+  name: "requirements-analyst",
+  description: "Discovers requirement gaps from BCM model docs, competitive analysis, product docs, and meeting extracts. Produces scan reports and proposals for the downstream requirements-writer agent. Runs through a 3-phase pipeline (scan \u2192 draft \u2192 trace), one phase per session, tracked by req:* GitHub issue labels.",
+  model: AGENT_MODEL.POWERFUL,
+  maxTurns: 80,
+  platforms: { cursor: { exclude: true } },
+  prompt: [
+    "# Requirements Analyst Agent",
+    "",
+    "Dedicated agent loop for discovering requirement gaps from BCM (Business",
+    "Capability Model) documents, product docs, and competitive analysis \u2014 then",
+    "creating well-formed requirement issues for the downstream",
+    "requirements-writer (BCM writer) agent to draft. Designed for scheduled",
+    "execution downstream of the BCM writer and company research agents.",
+    "",
+    "Follow your project's shared agent conventions (`AGENTS.md`,",
+    "`CLAUDE.md`, or equivalent) for all commit, branch, and PR rules.",
+    "",
+    "---",
+    "",
+    ...PROJECT_CONTEXT_MAINTAINER_SECTION,
+    "## Design Principles",
+    "",
+    "1. **Discover, don't write.** This agent identifies *what requirements are",
+    "   missing*. The requirements-writer skill writes the actual documents. The",
+    "   boundary keeps this agent fast and the requirements-writer authoritative.",
+    "2. **Trace everything.** Every discovered gap links to the source that",
+    "   revealed it (a BCM model doc, competitive analysis, product doc, or",
+    "   meeting extract).",
+    "3. **Respect the taxonomy.** Route every discovered requirement to the",
+    "   correct BCM category (FR, BR, NFR, SEC, DR, INT, OPS, UX, MT, ADR, TR)",
+    "   using the disambiguation rules in the requirements-writer skill.",
+    "4. **Deduplicate.** Before creating an issue, check whether a requirement",
+    "   already exists or an issue is already open for it.",
+    "",
+    "---",
+    "",
+    "## State Machine Overview",
+    "",
+    "Requirements synthesis flows through **3 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",
+    "\u2502  1. SCAN     \u2502\u2500\u2500\u2500\u2500\u25B6\u2502  2. DRAFT    \u2502\u2500\u2500\u2500\u2500\u25B6\u2502  3. TRACE    \u2502",
+    "\u2502  Read docs,  \u2502     \u2502  Write gap   \u2502     \u2502  Create GH   \u2502",
+    "\u2502  identify    \u2502     \u2502  report with \u2502     \u2502  issues and  \u2502",
+    "\u2502  gaps, check \u2502     \u2502  requirement \u2502     \u2502  update src  \u2502",
+    "\u2502  for dupes   \u2502     \u2502  proposals   \u2502     \u2502  docs with   \u2502",
+    "\u2502              \u2502     \u2502              \u2502     \u2502  traceability\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",
+    "```",
+    "",
+    "**Issue labels encode the phase:**",
+    "",
+    "| Label | Phase | Session work |",
+    "|-------|-------|-------------|",
+    "| `req:scan` | 1. Scan | Read source docs, identify potential requirement gaps, check against existing requirements and open issues, write deduplicated scan report |",
+    "| `req:draft` | 2. Draft | Write gap report with proposed requirements |",
+    "| `req:trace` | 3. Trace | Create GitHub issues for each proposed requirement and update source documents with traceability notes |",
+    "",
+    "All issues also carry `type:requirement` and a `status:*` label.",
+    "",
+    "**Issue count per scan cycle:** 1 scan + 1 draft + 1 trace = **3 sessions**.",
+    "",
+    "**Shortened paths:**",
+    "- No gaps found after scan \u2192 skip draft and trace \u2192 **1 session**",
+    "- No source docs need traceability updates \u2192 still **3 sessions** (trace",
+    "  handles both issue creation and doc updates)",
+    "",
+    "---",
+    "",
+    "## Configurable Paths",
+    "",
+    "Projects adopting this bundle must define these paths in their agent",
+    "configuration (`agentConfig.rules` extension or project-level docs):",
+    "",
+    "| Placeholder | Meaning | Typical value |",
+    "|-------------|---------|---------------|",
+    "| `<BCM_DOCS_ROOT>` | Root of BCM model docs (capability models) | `src/content/docs/concepts/` |",
+    "| `<COMPETITIVE_ROOT>` | Competitive analysis docs | `src/content/docs/business-strategy/competitive/` |",
+    "| `<PRODUCT_ROOT>` | Product roadmap / entity taxonomy | `src/content/docs/product/` |",
+    "| `<MEETINGS_ROOT>` | Meeting extracts | `src/content/docs/research/meetings/` |",
+    "| `<RESEARCH_REQUIREMENTS_ROOT>` | Scan reports and proposals | `src/content/docs/research/requirements/` |",
+    "| `<REQUIREMENTS_ROOT>` | Final requirement documents (owned by requirements-writer) | `src/content/docs/requirements/` |",
+    "| `<PREFIX>` | Project-specific requirement ID prefix | e.g. `VRTX`, `ACME` |",
+    "",
+    "If your project stores these in different locations, substitute accordingly",
+    "wherever the phase instructions reference a path.",
+    "",
+    "---",
+    "",
+    "## Agent Loop",
+    "",
+    "Run this loop exactly once per session. Never start a second issue.",
+    "",
+    "1. Claim one open `type:requirement` issue using phase priority:",
+    "   `req:scan` > `req:draft` > `req:trace`.",
+    "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 `req:*` label.",
+    "4. Commit, push, open a PR (if applicable), and close the issue per your",
+    "   project's PR workflow.",
+    "",
+    "---",
+    "",
+    "## Phase 1: Scan (`req:scan`)",
+    "",
+    "**Goal:** Read source documents, identify where requirements are missing,",
+    "incomplete, or contradictory, then check each potential gap against existing",
+    "requirements and open issues to eliminate duplicates. Produces a single",
+    "deduplicated scan report.",
+    "",
+    "**Budget:** Reading source docs + reading requirement registries + searching",
+    "issues. Write one deduplicated scan output file.",
+    "",
+    "### Scan Sources",
+    "",
+    "The issue specifies which source(s) to scan. Common scan scopes:",
+    "",
+    "| Scope | What to read | What to look for |",
+    "|-------|-------------|-----------------|",
+    "| **BCM model doc** | One `{PREFIX}-NNN` doc under `<BCM_DOCS_ROOT>` | The doc's project-relevance section (commonly `## <Project> Relevance` or `## Strategic Implications`) \u2014 gaps where capabilities exist but no FR/BR/INT addresses them. Use `docs/project-context.md` to judge what is relevant. |",
+    "| **Competitive analysis** | One `comp-*.md` doc under `<COMPETITIVE_ROOT>` | Feature comparison gaps \u2014 competitor features the product lacks requirements for |",
+    "| **Product roadmap** | `<PRODUCT_ROOT>/prioritized-feature-roadmap.md` | Roadmap items without corresponding FRs |",
+    "| **Entity taxonomy** | `<PRODUCT_ROOT>/entity-taxonomy.md` | Entities without CRUD requirements (FR), data requirements (DR), or security requirements (SEC) |",
+    "| **Meeting extract** | `<MEETINGS_ROOT>/meeting-*.extract.md` | Requirements identified but not yet formalized |",
+    "",
+    "### Steps",
+    "",
+    "1. **Read the source documents** specified in the issue.",
+    "",
+    "2. **Identify potential gaps.** For each potential missing requirement:",
+    "   - Classify into the correct BCM category (FR, BR, NFR, SEC, DR, INT,",
+    "     OPS, UX, MT, ADR, TR)",
+    "   - Apply the disambiguation rules from the requirements-writer skill",
+    "   - Note the source that revealed the gap",
+    "   - Estimate priority based on the source context",
+    "",
+    "3. **Read the requirements registry.** Scan `_index.md` files in each",
+    "   `<REQUIREMENTS_ROOT>/<category>/` directory to know what already exists.",
+    "",
+    "4. **Search for existing issues.** For each potential gap, search open issues:",
+    "   ```bash",
+    '   gh issue list --label "type:requirement" --state open \\',
+    "     --json number,title --limit 100",
+    "   ```",
+    "",
+    "5. **Classify each gap:**",
+    "   - **New** \u2014 no existing requirement or open issue covers this",
+    "   - **Duplicate** \u2014 an existing requirement already addresses this",
+    "   - **In progress** \u2014 an open issue already targets this",
+    "   - **Partial** \u2014 existing requirement partially covers this; note the gap",
+    "",
+    "6. **Write the deduplicated scan report** to:",
+    "   ```",
+    "   <RESEARCH_REQUIREMENTS_ROOT>/req-scan-<scope>-<YYYY-MM-DD>.md",
+    "   ```",
+    "",
+    "   Format:",
+    "   ```markdown",
+    "   ---",
+    '   title: "Requirements Scan: <scope>"',
+    "   date: YYYY-MM-DD",
+    "   parent_issue: <N>",
+    "   status: complete",
+    "   ---",
+    "",
+    "   # Requirements Scan: <scope>",
+    "",
+    "   ## Source Documents Reviewed",
+    "   - <path> \u2014 <brief description>",
+    "",
+    "   ## Existing Requirements Checked",
+    "   - <category>: <count> existing docs, <count> open issues",
+    "",
+    "   ## Identified Gaps (New)",
+    "   ### Gap 1: <Title>",
+    "   - **Category:** FR / BR / NFR / SEC / DR / INT / OPS / UX / MT / ADR / TR",
+    "   - **Source:** <path to doc + section that revealed this gap>",
+    "   - **Priority:** High / Normal / Low",
+    "   - **Rationale:** <why this requirement is needed>",
+    "   - **Duplicate check:** No existing requirement or open issue found",
+    "   - **Proposed scope:** <1-2 sentences on what the requirement should cover>",
+    "",
+    "   ## Already Covered",
+    "   <list of potential gaps that turned out to already have requirements>",
+    "",
+    "   ## In Progress",
+    "   <gaps that already have open issues \u2014 include issue numbers>",
+    "",
+    "   ## Ambiguous / Needs Human Decision",
+    "   <gaps where the correct category or scope is unclear>",
+    "   ```",
+    "",
+    "7. **Create downstream issues based on findings:**",
+    "   - If any new gaps were identified \u2192 create `req:draft` issue",
+    "     (blocked on this issue via `Depends on: #N`).",
+    "   - If **no gaps** were found \u2192 stop (no further phases needed). Comment",
+    "     on the issue noting that no gaps were identified, and proceed directly",
+    "     to commit and push. The scan issue will be marked done with no",
+    "     downstream work needed.",
+    "",
+    "8. **Commit and push.**",
+    "",
+    "---",
+    "",
+    "## Phase 2: Draft (`req:draft`)",
+    "",
+    "**Goal:** Expand each identified gap into a requirement proposal with enough",
+    "detail for the requirements-writer to produce a full document.",
+    "",
+    "**Budget:** No web searches. Reading + writing.",
+    "",
+    "### Steps",
+    "",
+    "1. **Read the scan report** from Phase 1.",
+    "",
+    "2. **For each gap**, write a detailed proposal:",
+    "",
+    "   ```markdown",
+    "   ## Proposed: <PREFIX>-<NNN> \u2014 <Title>",
+    "",
+    "   **Category:** <FR/BR/NFR/SEC/DR/INT/OPS/UX/MT/ADR/TR>",
+    "   **Priority:** <High/Normal/Low>",
+    "   **Source:** <document path and section>",
+    "",
+    "   ### Summary",
+    "   <2-3 sentences describing what the requirement should capture>",
+    "",
+    "   ### Draft Acceptance Criteria",
+    "   - [ ] <testable criterion 1>",
+    "   - [ ] <testable criterion 2>",
+    "   - [ ] <testable criterion 3>",
+    "",
+    "   ### Traceability",
+    "   - **Implements:** <BR or parent requirement if applicable>",
+    "   - **Related:** <existing requirements that interact with this one>",
+    "   - **Source:** <BCM doc, competitive analysis, or meeting that revealed",
+    "     the gap \u2014 use a markdown link. If the source is a meeting note, the",
+    "     downstream requirement doc must include the same meeting as a link in",
+    "     its Traceability `Related:` list.>",
+    "",
+    "   ### Decision Authority",
+    '   <"Direct write" for BR/FR/NFR/SEC/UX, or "Proposed \u2014 needs human',
+    '   decision" for ADR/TR, or "Mixed \u2014 defer technology choices" for',
+    "   DR/MT/INT/OPS>",
+    "",
+    "   ### Notes for Requirements Writer",
+    "   <any context the writer should know \u2014 related ADRs, existing partial",
+    "   coverage, relevant competitive features>",
+    "   ```",
+    "",
+    "3. **Write the proposals** to:",
+    "   ```",
+    "   <RESEARCH_REQUIREMENTS_ROOT>/req-proposals-<scope>-<YYYY-MM-DD>.md",
+    "   ```",
+    "",
+    "4. **Determine next sequence numbers.** Check each target category",
+    "   directory under `<REQUIREMENTS_ROOT>/<category>/` to find the next",
+    "   available `NNN` for each proposed requirement.",
+    "",
+    "5. **Create the `req:trace` issue** blocked on this draft issue.",
+    "",
+    "6. **Commit and push.**",
+    "",
+    "---",
+    "",
+    "## Phase 3: Trace (`req:trace`)",
+    "",
+    "**Goal:** Create GitHub issues for each proposed requirement and update",
+    "source documents with traceability notes indicating that requirement issues",
+    "were created.",
+    "",
+    "**Budget:** No web searches. Issue creation + minor edits to source",
+    "documents.",
+    "",
+    "### Steps",
+    "",
+    "1. **Read the proposals** from Phase 2.",
+    "",
+    "2. **Create requirement issues.** For each proposal:",
+    "",
+    "   All `type:requirement` issues default to `priority:medium` (override",
+    "   only if the proposal's priority was explicitly High or Low).",
+    "",
+    "   ```bash",
+    "   gh issue create \\",
+    '     --title "docs(<category>): <PREFIX>-<NNN> \u2014 <title>" \\',
+    '     --label "type:requirement" --label "status:ready" --label "priority:medium" \\',
+    '     --body "## Objective',
+    "   Write <PREFIX>-<NNN> \u2014 <title>.",
+    "",
+    "   ## Context",
+    "   - **Gap identified by:** requirements scan of <source>",
+    "   - **Proposals file:** <RESEARCH_REQUIREMENTS_ROOT>/req-proposals-<scope>-<date>.md",
+    "",
+    "   ## Inputs",
+    "   - **Depends on:** (none)",
+    "   - **Read:** <RESEARCH_REQUIREMENTS_ROOT>/req-proposals-<scope>-<date>.md, <source docs>",
+    "",
+    "   ## Acceptance Criteria",
+    "   - [ ] Requirement document follows <category> template",
+    "   - [ ] Traceability links to source BCM/competitive/product doc",
+    "   - [ ] Registry index updated",
+    "   - [ ] Decision authority rules followed (direct write vs. proposed)",
+    "",
+    "   ## Scope Size",
+    "   small",
+    "",
+    "   ## Output Path",
+    '   <REQUIREMENTS_ROOT>/<category>/<PREFIX>-<NNN>-<slug>.md"',
+    "   ```",
+    "",
+    "3. **Update source documents.** In each BCM model doc or competitive",
+    "   analysis that was scanned, add a note in the project-relevance /",
+    "   strategic-implications section (whichever heading the source doc uses)",
+    "   indicating that a requirement issue was created:",
+    "",
+    "   ```markdown",
+    "   - Gap addressed: see [<PREFIX>-<NNN>](<relative path to requirement doc>)",
+    "     (issue #<N>)",
+    "   ```",
+    "",
+    "4. **Comment on the scan issue** with a summary of all issues created and",
+    "   all docs updated.",
+    "",
+    "5. **Commit and push.**",
+    "",
+    "---",
+    "",
+    "## Coordination with Other Agents",
+    "",
+    "| Direction | Agent | What |",
+    "|-----------|-------|------|",
+    "| Upstream | BCM Writer | Scans capability-model docs for project-relevance gaps (judged against `docs/project-context.md`) |",
+    "| Upstream | Company Research | Scans competitive analysis for feature comparison gaps |",
+    "| Upstream | Meeting Analyst | Scans meeting extracts for requirement proposals |",
+    "| Downstream | Requirements Writer (BCM Writer) | Creates `type:requirement` issues for the skill to draft |",
+    "",
+    "**File boundaries:** Writes to `<RESEARCH_REQUIREMENTS_ROOT>/req-*.md` and",
+    "minor traceability edits to `<BCM_DOCS_ROOT>` and `<COMPETITIVE_ROOT>`.",
+    "Never writes to `<REQUIREMENTS_ROOT>/` \u2014 that is owned by the",
+    "requirements-writer agent.",
+    "",
+    "---",
+    "",
+    "## Blocked Issues",
+    "",
+    "Additional block reasons specific to requirements synthesis:",
+    "- Source document has unresolved contradictions",
+    "- Category classification is ambiguous (needs human disambiguation)",
+    "- Dependent BCM documents are still in draft with placeholder content",
+    "",
+    "---",
+    "",
+    "## Rules",
+    "",
+    "- **Discover, don't write requirements.** Create issues for the",
+    "  requirements-writer \u2014 don't write requirement documents directly.",
+    "- **Deduplicate rigorously.** Check both existing docs and open issues",
+    "  before flagging a gap.",
+    "- **Respect decision authority.** Mark ADR/TR proposals as needing human",
+    "  decision. Don't create direct-write issues for technology choices.",
+    "- **Bidirectional traceability.** Every `req-scan-*.md` and",
+    "  `req-proposals-*.md` must include a `## Produced` section listing the",
+    "  downstream requirement issues (and eventual requirement documents) it",
+    "  spawned, as markdown links; each formal requirement document under",
+    "  `<REQUIREMENTS_ROOT>/` must include a forward link back to the scan or",
+    "  proposal that produced it."
+  ].join("\n")
+};
+var scanRequirementsSkill = {
+  name: "scan-requirements",
+  description: "Kick off a requirements-analyst scan across BCM model docs, competitive analysis, product docs, or meeting extracts. Creates a req:scan issue and dispatches Phase 1.",
+  disableModelInvocation: true,
+  userInvocable: true,
+  context: "fork",
+  agent: "requirements-analyst",
+  platforms: { cursor: { exclude: true } },
+  instructions: [
+    "# Scan Requirements",
+    "",
+    "Kick off a requirements-analyst scan cycle. Creates a `req:scan` issue",
+    "targeted at the requested scope and dispatches Phase 1 (Scan) in the",
+    "requirements-analyst agent.",
+    "",
+    "## Usage",
+    "",
+    "/scan-requirements <scope>",
+    "",
+    "Where `<scope>` is one of:",
+    "- `bcm:<PREFIX-NNN>` \u2014 a single BCM model doc",
+    "- `competitive:<slug>` \u2014 a single competitive analysis doc",
+    "- `product-roadmap` \u2014 the prioritized feature roadmap",
+    "- `entity-taxonomy` \u2014 the entity taxonomy doc",
+    "- `meeting:<slug>` \u2014 a meeting extract",
+    "- `all-bcm` / `all-competitive` \u2014 full sweep (long-running)",
+    "",
+    "## Steps",
+    "",
+    "1. Create a `req:scan` issue with `type:requirement`, `priority:medium`,",
+    "   and `status:ready`. Body must list the files to read and the scan scope.",
+    "2. Execute Phase 1 (Scan) of the requirements-analyst agent.",
+    "3. If gaps are found, a `req:draft` issue is created automatically.",
+    "",
+    "## Output",
+    "",
+    "- A `req-scan-<scope>-<YYYY-MM-DD>.md` file under the project's research",
+    "  requirements directory.",
+    "- A `req:draft` issue if any gaps were identified."
+  ].join("\n")
+};
+var requirementsAnalystBundle = {
+  name: "requirements-analyst",
+  description: "Requirements gap-discovery agent bundle for BCM-driven projects. 3-phase pipeline (scan, draft, trace) with req:* phase labels.",
+  appliesWhen: () => true,
+  rules: [
     {
-      name: "agent-rules-customization",
-      description: "How to customize agent rules for this repo via the Projen project definition",
-      scope: AGENT_RULE_SCOPE.FILE_PATTERN,
-      filePatterns: [
-        "projenrc/**/*.ts",
-        ".projenrc.ts",
-        ".claude/rules/*.md",
-        ".cursor/rules/*.mdc",
-        "CLAUDE.md"
-      ],
+      name: "requirements-analyst-workflow",
+      description: "Describes the 3-phase requirements gap-discovery pipeline, the req:* label taxonomy, and the boundary with the downstream requirements-writer agent.",
+      scope: AGENT_RULE_SCOPE.ALWAYS,
       content: [
-        "# Customizing Agent Rules",
-        "",
-        "Agent rules for Claude and Cursor are **generated** by configulator's `AgentConfig` component. The generated output files (`.claude/rules/`, `.cursor/rules/`, `CLAUDE.md`) must not be edited directly \u2014 they are overwritten on every `npx projen` run.",
-        "",
-        "## Adding Repo-Specific Rules",
-        "",
-        "Rules that only apply to this repository should be added to the `agentConfig.rules` array in the Projen project definition (`.projenrc.ts` or `projenrc/*.ts`):",
-        "",
-        "```typescript",
-        "agentConfig: {",
-        "  rules: [",
-        "    {",
-        "      name: 'my-repo-rule',",
-        "      description: 'What this rule does',",
-        "      scope: AGENT_RULE_SCOPE.ALWAYS, // or FILE_PATTERN with filePatterns",
-        "      content: '# My Rule\\n\\n- Guideline 1\\n- Guideline 2',",
-        "    },",
-        "  ],",
-        "}",
-        "```",
-        "",
-        "## Extending Existing Bundle Rules",
-        "",
-        "To append repo-specific content to a rule provided by a configulator bundle (without replacing it), use `agentConfig.ruleExtensions`:",
+        "# Requirements Analyst Workflow",
         "",
-        "```typescript",
-        "agentConfig: {",
-        "  ruleExtensions: {",
-        "    'typescript-conventions': '## Additional Guidelines\\n\\n- My custom guideline',",
-        "  },",
-        "}",
-        "```",
+        "Use `/scan-requirements <scope>` to kick off a requirements gap",
+        "discovery cycle. The pipeline runs in 3 phases \u2014 scan, draft, trace \u2014",
+        "each tracked by its own GitHub issue labeled `req:scan`, `req:draft`,",
+        "or `req:trace`. All issues carry `type:requirement`.",
         "",
-        "## After Any Change",
+        "The requirements-analyst *discovers gaps and drafts proposals*; it",
+        "does **not** write final requirement documents. Writing is the job of",
+        "the downstream requirements-writer (BCM writer) agent. Keep that",
+        "boundary clean: proposals land under the research requirements",
+        "directory, not under the authoritative requirements tree.",
         "",
-        "Run `npx projen` then `pnpm install` to regenerate the output files."
+        "See the `requirements-analyst` agent definition for full workflow",
+        "details and phase-by-phase instructions."
       ].join("\n"),
+      platforms: {
+        cursor: { exclude: true }
+      },
       tags: ["workflow"]
+    }
+  ],
+  skills: [scanRequirementsSkill],
+  subAgents: [requirementsAnalystSubAgent],
+  labels: [
+    {
+      name: "type:requirement",
+      color: "1D76DB",
+      description: "Work that produces or discovers a requirement document (FR, BR, NFR, etc.)"
     },
     {
-      name: "projen-conventions",
-      description: "Projen configuration patterns and best practices",
-      scope: AGENT_RULE_SCOPE.FILE_PATTERN,
-      filePatterns: ["projenrc/**/*.ts", ".projenrc.ts"],
-      content: [
-        "# Projen Conventions",
-        "",
-        "## Configuration Management",
-        "",
-        "- **Never edit generated files** (`package.json`, `tsconfig.json`, etc. marked with `// ~~ Generated by projen`)",
-        "- Edit Projen configuration in:",
-        "  - `.projenrc.ts` (root)",
-        "  - `projenrc/*.ts` (package-specific)",
-        "- After making Projen changes, run `npx projen` to synthesize",
-        "",
-        "## Workspace Dependencies",
-        "",
-        "When adding dependencies between packages in a monorepo:",
-        "",
-        '- Use the workspace protocol: `project.addDeps("@org/sibling-pkg@workspace:*")`',
-        "- This ensures the local version is always resolved, not a registry version",
-        '- For dev dependencies: `project.addDevDeps("@org/sibling-pkg@workspace:*")`',
-        "",
-        "## The `configureMyProject` Pattern",
-        "",
-        "Each package should expose a `configureMyProject(options)` factory function that creates and configures its Projen project:",
-        "",
-        "```typescript",
-        "export function configureMyProject(",
-        "  options: MyProjectOptions,",
-        "): TypeScriptProject {",
-        "  const project = new TypeScriptProject({",
-        "    ...options,",
-        "    // package-specific defaults",
-        "  });",
-        "",
-        "  // Attach components, configure rules, etc.",
-        "  return project;",
-        "}",
-        "```",
-        "",
-        "This pattern keeps `.projenrc.ts` clean and makes package configuration reusable and testable.",
-        "",
-        "## Custom Projen Components",
-        "",
-        "All custom components must extend `Component` from Projen and use a static `.of()` factory for discovery:",
-        "",
-        "```typescript",
-        "export class MyComponent extends Component {",
-        "  public static of(project: Project): MyComponent | undefined {",
-        "    const isDefined = (c: Component): c is MyComponent =>",
-        "      c instanceof MyComponent;",
-        "    return project.components.find(isDefined);",
-        "  }",
-        "",
-        "  constructor(project: Project, options: MyComponentOptions) {",
-        "    super(project);",
-        "    // Implementation",
-        "  }",
-        "}",
-        "```",
-        "",
-        "## Component Authoring",
-        "",
-        "- Export project types and utilities from `index.ts`",
-        "- Follow Projen's component lifecycle patterns",
-        "- Use `merge` from `ts-deepmerge` for deep merging configuration objects",
-        "- Components should be reusable and configurable; use TypeScript interfaces for component options",
-        "- Provide sensible defaults while allowing customization",
-        "- Document public APIs with minimal JSDoc; put extended documentation in markdown",
-        "",
-        "## Dependencies",
-        "",
-        "- Dependencies managed through Projen configuration, not directly in `package.json`",
-        '- Use catalog dependencies when available (e.g., `"projen": "catalog:"`)',
-        "- Peer dependencies for shared libraries (e.g., `constructs`, `projen`, `aws-cdk-lib`)",
-        '- Use workspace protocol for internal packages: `"@org/pkg@workspace:*"`'
-      ].join("\n"),
-      tags: ["workflow"]
+      name: "req:scan",
+      color: "C5DEF5",
+      description: "Phase 1: scan source docs for requirement gaps and deduplicate"
+    },
+    {
+      name: "req:draft",
+      color: "BFDADC",
+      description: "Phase 2: draft requirement proposals for the requirements-writer"
+    },
+    {
+      name: "req:trace",
+      color: "D4C5F9",
+      description: "Phase 3: create requirement issues and backfill traceability on source docs"
     }
   ]
 };
 
-// src/agent/bundles/requirements-analyst.ts
-var requirementsAnalystSubAgent = {
-  name: "requirements-analyst",
-  description: "Discovers requirement gaps from BCM model docs, competitive analysis, product docs, and meeting extracts. Produces scan reports and proposals for the downstream requirements-writer agent. Runs through a 3-phase pipeline (scan \u2192 draft \u2192 trace), one phase per session, tracked by req:* GitHub issue labels.",
+// 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: [
-    "# Requirements Analyst Agent",
+    "# Research Analyst Agent",
     "",
-    "Dedicated agent loop for discovering requirement gaps from BCM (Business",
-    "Capability Model) documents, product docs, and competitive analysis \u2014 then",
-    "creating well-formed requirement issues for the downstream",
-    "requirements-writer (BCM writer) agent to draft. Designed for scheduled",
-    "execution downstream of the BCM writer and company research agents.",
+    "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_MAINTAINER_SECTION,
+    ...PROJECT_CONTEXT_READER_SECTION,
     "## Design Principles",
     "",
-    "1. **Discover, don't write.** This agent identifies *what requirements are",
-    "   missing*. The requirements-writer skill writes the actual documents. The",
-    "   boundary keeps this agent fast and the requirements-writer authoritative.",
-    "2. **Trace everything.** Every discovered gap links to the source that",
-    "   revealed it (a BCM model doc, competitive analysis, product doc, or",
-    "   meeting extract).",
-    "3. **Respect the taxonomy.** Route every discovered requirement to the",
-    "   correct BCM category (FR, BR, NFR, SEC, DR, INT, OPS, UX, MT, ADR, TR)",
-    "   using the disambiguation rules in the requirements-writer skill.",
-    "4. **Deduplicate.** Before creating an issue, check whether a requirement",
-    "   already exists or an issue is already open for it.",
+    "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",
     "",
-    "Requirements synthesis flows through **3 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",
-    "\u2502  1. SCAN     \u2502\u2500\u2500\u2500\u2500\u25B6\u2502  2. DRAFT    \u2502\u2500\u2500\u2500\u2500\u25B6\u2502  3. TRACE    \u2502",
-    "\u2502  Read docs,  \u2502     \u2502  Write gap   \u2502     \u2502  Create GH   \u2502",
-    "\u2502  identify    \u2502     \u2502  report with \u2502     \u2502  issues and  \u2502",
-    "\u2502  gaps, check \u2502     \u2502  requirement \u2502     \u2502  update src  \u2502",
-    "\u2502  for dupes   \u2502     \u2502  proposals   \u2502     \u2502  docs with   \u2502",
-    "\u2502              \u2502     \u2502              \u2502     \u2502  traceability\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",
+    "\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 |",
     "|-------|-------|-------------|",
-    "| `req:scan` | 1. Scan | Read source docs, identify potential requirement gaps, check against existing requirements and open issues, write deduplicated scan report |",
-    "| `req:draft` | 2. Draft | Write gap report with proposed requirements |",
-    "| `req:trace` | 3. Trace | Create GitHub issues for each proposed requirement and update source documents with traceability notes |",
+    "| `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:requirement` and a `status:*` label.",
+    "All issues also carry `type:research` and a `status:*` label.",
     "",
-    "**Issue count per scan cycle:** 1 scan + 1 draft + 1 trace = **3 sessions**.",
+    "**Issue count per research cycle:** 1 scope + N slice + 1 verify =",
+    "**N + 2 sessions**. Typical N is 3\u20136.",
     "",
     "**Shortened paths:**",
-    "- No gaps found after scan \u2192 skip draft and trace \u2192 **1 session**",
-    "- No source docs need traceability updates \u2192 still **3 sessions** (trace",
-    "  handles both issue creation and doc updates)",
+    "- 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",
     "",
-    "Projects adopting this bundle must define these paths in their agent",
-    "configuration (`agentConfig.rules` extension or project-level docs):",
+    "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 | Typical value |",
-    "|-------------|---------|---------------|",
-    "| `<BCM_DOCS_ROOT>` | Root of BCM model docs (capability models) | `src/content/docs/concepts/` |",
-    "| `<COMPETITIVE_ROOT>` | Competitive analysis docs | `src/content/docs/business-strategy/competitive/` |",
-    "| `<PRODUCT_ROOT>` | Product roadmap / entity taxonomy | `src/content/docs/product/` |",
-    "| `<MEETINGS_ROOT>` | Meeting extracts | `src/content/docs/research/meetings/` |",
-    "| `<RESEARCH_REQUIREMENTS_ROOT>` | Scan reports and proposals | `src/content/docs/research/requirements/` |",
-    "| `<REQUIREMENTS_ROOT>` | Final requirement documents (owned by requirements-writer) | `src/content/docs/requirements/` |",
-    "| `<PREFIX>` | Project-specific requirement ID prefix | e.g. `VRTX`, `ACME` |",
+    "| 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 your project stores these in different locations, substitute accordingly",
-    "wherever the phase instructions reference a path.",
+    "If `docs/project-context.md` specifies a different research tree,",
+    "prefer that. Otherwise fall back to the defaults above.",
     "",
     "---",
     "",
@@ -3521,348 +4553,340 @@ var requirementsAnalystSubAgent = {
     "",
     "Run this loop exactly once per session. Never start a second issue.",
     "",
-    "1. Claim one open `type:requirement` issue using phase priority:",
-    "   `req:scan` > `req:draft` > `req:trace`.",
-    "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 `req:*` label.",
-    "4. Commit, push, open a PR (if applicable), and close the issue per your",
-    "   project's PR workflow.",
+    "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: Scan (`req:scan`)",
-    "",
-    "**Goal:** Read source documents, identify where requirements are missing,",
-    "incomplete, or contradictory, then check each potential gap against existing",
-    "requirements and open issues to eliminate duplicates. Produces a single",
-    "deduplicated scan report.",
-    "",
-    "**Budget:** Reading source docs + reading requirement registries + searching",
-    "issues. Write one deduplicated scan output file.",
-    "",
-    "### Scan Sources",
+    "## Phase 1: Scope (`research:scope`)",
     "",
-    "The issue specifies which source(s) to scan. Common scan scopes:",
+    "**Goal:** Turn a natural-language research question into a bounded",
+    "scope file and `N` focused slice issues.",
     "",
-    "| Scope | What to read | What to look for |",
-    "|-------|-------------|-----------------|",
-    "| **BCM model doc** | One `{PREFIX}-NNN` doc under `<BCM_DOCS_ROOT>` | The doc's project-relevance section (commonly `## <Project> Relevance` or `## Strategic Implications`) \u2014 gaps where capabilities exist but no FR/BR/INT addresses them. Use `docs/project-context.md` to judge what is relevant. |",
-    "| **Competitive analysis** | One `comp-*.md` doc under `<COMPETITIVE_ROOT>` | Feature comparison gaps \u2014 competitor features the product lacks requirements for |",
-    "| **Product roadmap** | `<PRODUCT_ROOT>/prioritized-feature-roadmap.md` | Roadmap items without corresponding FRs |",
-    "| **Entity taxonomy** | `<PRODUCT_ROOT>/entity-taxonomy.md` | Entities without CRUD requirements (FR), data requirements (DR), or security requirements (SEC) |",
-    "| **Meeting extract** | `<MEETINGS_ROOT>/meeting-*.extract.md` | Requirements identified but not yet formalized |",
+    "**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 source documents** specified in the issue.",
-    "",
-    "2. **Identify potential gaps.** For each potential missing requirement:",
-    "   - Classify into the correct BCM category (FR, BR, NFR, SEC, DR, INT,",
-    "     OPS, UX, MT, ADR, TR)",
-    "   - Apply the disambiguation rules from the requirements-writer skill",
-    "   - Note the source that revealed the gap",
-    "   - Estimate priority based on the source context",
-    "",
-    "3. **Read the requirements registry.** Scan `_index.md` files in each",
-    "   `<REQUIREMENTS_ROOT>/<category>/` directory to know what already exists.",
+    "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",
     "",
-    "4. **Search for existing issues.** For each potential gap, search open issues:",
-    "   ```bash",
-    '   gh issue list --label "type:requirement" --state open \\',
-    "     --json number,title --limit 100",
-    "   ```",
+    "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>/`.",
     "",
-    "5. **Classify each gap:**",
-    "   - **New** \u2014 no existing requirement or open issue covers this",
-    "   - **Duplicate** \u2014 an existing requirement already addresses this",
-    "   - **In progress** \u2014 an open issue already targets this",
-    "   - **Partial** \u2014 existing requirement partially covers this; note the gap",
+    "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)",
     "",
-    "6. **Write the deduplicated scan report** to:",
-    "   ```",
-    "   <RESEARCH_REQUIREMENTS_ROOT>/req-scan-<scope>-<YYYY-MM-DD>.md",
-    "   ```",
+    "4. **Write the scope file** to",
+    "   `<SCOPE_DIR>/<RESEARCH_SLUG>.scope.md`:",
     "",
-    "   Format:",
     "   ```markdown",
     "   ---",
-    '   title: "Requirements Scan: <scope>"',
+    '   title: "Research Scope: <question>"',
+    "   slug: <RESEARCH_SLUG>",
     "   date: YYYY-MM-DD",
     "   parent_issue: <N>",
-    "   status: complete",
+    "   slice_count: <N>",
     "   ---",
     "",
-    "   # Requirements Scan: <scope>",
+    "   # Research Scope: <question>",
     "",
-    "   ## Source Documents Reviewed",
-    "   - <path> \u2014 <brief description>",
+    "   ## Question",
+    "   <verbatim question from the issue>",
     "",
-    "   ## Existing Requirements Checked",
-    "   - <category>: <count> existing docs, <count> open issues",
+    "   ## Authorized Sources",
+    "   - <source category or path>",
     "",
-    "   ## Identified Gaps (New)",
-    "   ### Gap 1: <Title>",
-    "   - **Category:** FR / BR / NFR / SEC / DR / INT / OPS / UX / MT / ADR / TR",
-    "   - **Source:** <path to doc + section that revealed this gap>",
-    "   - **Priority:** High / Normal / Low",
-    "   - **Rationale:** <why this requirement is needed>",
-    "   - **Duplicate check:** No existing requirement or open issue found",
-    "   - **Proposed scope:** <1-2 sentences on what the requirement should cover>",
+    "   ## Acceptance Criteria",
+    "   - [ ] <criterion for the final deliverable>",
     "",
-    "   ## Already Covered",
-    "   <list of potential gaps that turned out to already have requirements>",
+    "   ## 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",
     "",
-    "   ## In Progress",
-    "   <gaps that already have open issues \u2014 include issue numbers>",
+    "   ### Slice 2: <title>",
+    "   ...",
     "",
-    "   ## Ambiguous / Needs Human Decision",
-    "   <gaps where the correct category or scope is unclear>",
+    "   ## Out of Scope",
+    "   <sub-questions deliberately excluded from this cycle>",
+    "",
+    "   ## Deliverable",
+    "   <DELIVERABLES_DIR>/<RESEARCH_SLUG>.md",
     "   ```",
     "",
-    "7. **Create downstream issues based on findings:**",
-    "   - If any new gaps were identified \u2192 create `req:draft` issue",
-    "     (blocked on this issue via `Depends on: #N`).",
-    "   - If **no gaps** were found \u2192 stop (no further phases needed). Comment",
-    "     on the issue noting that no gaps were identified, and proceed directly",
-    "     to commit and push. The scan issue will be marked done with no",
-    "     downstream work needed.",
+    "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).",
     "",
-    "8. **Commit and push.**",
+    "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: Draft (`req:draft`)",
+    "## Phase 2: Slice (`research:slice`)",
     "",
-    "**Goal:** Expand each identified gap into a requirement proposal with enough",
-    "detail for the requirements-writer to produce a full document.",
+    "**Goal:** Answer one slice by searching the authorized sources and",
+    "writing a single slice note file.",
     "",
-    "**Budget:** No web searches. Reading + writing.",
+    "**Budget:** Search budget is one slice \u2014 do not expand scope. Write",
+    "one slice note. Do not create downstream issues.",
     "",
     "### Steps",
     "",
-    "1. **Read the scan report** from Phase 1.",
+    "1. **Read the scope file** referenced in the issue body.",
     "",
-    "2. **For each gap**, write a detailed proposal:",
+    "2. **Identify your slice** by number and title. Re-read the slice's",
+    "   focus, sources, and output path.",
     "",
-    "   ```markdown",
-    "   ## Proposed: <PREFIX>-<NNN> \u2014 <Title>",
+    "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.",
     "",
-    "   **Category:** <FR/BR/NFR/SEC/DR/INT/OPS/UX/MT/ADR/TR>",
-    "   **Priority:** <High/Normal/Low>",
-    "   **Source:** <document path and section>",
+    "4. **Synthesize a slice note** and write it to the slice's output",
+    "   path (e.g. `<SLICES_DIR>/<RESEARCH_SLUG>-NN-<slug>.slice.md`):",
     "",
-    "   ### Summary",
-    "   <2-3 sentences describing what the requirement should capture>",
+    "   ```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>",
+    "   ---",
     "",
-    "   ### Draft Acceptance Criteria",
-    "   - [ ] <testable criterion 1>",
-    "   - [ ] <testable criterion 2>",
-    "   - [ ] <testable criterion 3>",
+    "   # Slice NN: <title>",
     "",
-    "   ### Traceability",
-    "   - **Implements:** <BR or parent requirement if applicable>",
-    "   - **Related:** <existing requirements that interact with this one>",
-    "   - **Source:** <BCM doc, competitive analysis, or meeting that revealed",
-    "     the gap \u2014 use a markdown link. If the source is a meeting note, the",
-    "     downstream requirement doc must include the same meeting as a link in",
-    "     its Traceability `Related:` list.>",
+    "   ## Question",
+    "   <the slice-level question>",
     "",
-    "   ### Decision Authority",
-    '   <"Direct write" for BR/FR/NFR/SEC/UX, or "Proposed \u2014 needs human',
-    '   decision" for ADR/TR, or "Mixed \u2014 defer technology choices" for',
-    "   DR/MT/INT/OPS>",
+    "   ## Key Findings",
+    "   - <finding> \u2014 source: <citation>",
     "",
-    "   ### Notes for Requirements Writer",
-    "   <any context the writer should know \u2014 related ADRs, existing partial",
-    "   coverage, relevant competitive features>",
-    "   ```",
+    "   ## Evidence",
+    "   <short quotations, paraphrases, or structured data with citations>",
     "",
-    "3. **Write the proposals** to:",
-    "   ```",
-    "   <RESEARCH_REQUIREMENTS_ROOT>/req-proposals-<scope>-<YYYY-MM-DD>.md",
-    "   ```",
+    "   ## Gaps / Open Questions",
+    "   <anything the slice could not answer inside its budget>",
     "",
-    "4. **Determine next sequence numbers.** Check each target category",
-    "   directory under `<REQUIREMENTS_ROOT>/<category>/` to find the next",
-    "   available `NNN` for each proposed requirement.",
+    "   ## Sources",
+    "   - <source URL or file path> \u2014 <date accessed>",
+    "   ```",
     "",
-    "5. **Create the `req:trace` issue** blocked on this draft issue.",
+    "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.**",
+    "6. **Commit and push** the slice note. Close the slice issue.",
     "",
     "---",
     "",
-    "## Phase 3: Trace (`req:trace`)",
+    "## Phase 3: Verify (`research:verify`)",
     "",
-    "**Goal:** Create GitHub issues for each proposed requirement and update",
-    "source documents with traceability notes indicating that requirement issues",
-    "were created.",
+    "**Goal:** Reconcile every slice into a single verified deliverable.",
     "",
-    "**Budget:** No web searches. Issue creation + minor edits to source",
-    "documents.",
+    "**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 proposals** from Phase 2.",
+    "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. **Create requirement issues.** For each proposal:",
+    "2. **Build a claim index.** For every assertion in any slice, note",
+    "   which slice(s) support it and which sources back it.",
     "",
-    "   All `type:requirement` issues default to `priority:medium` (override",
-    "   only if the proposal's priority was explicitly High or Low).",
+    "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",
     "",
-    "   ```bash",
-    "   gh issue create \\",
-    '     --title "docs(<category>): <PREFIX>-<NNN> \u2014 <title>" \\',
-    '     --label "type:requirement" --label "status:ready" --label "priority:medium" \\',
-    '     --body "## Objective',
-    "   Write <PREFIX>-<NNN> \u2014 <title>.",
+    "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.",
     "",
-    "   ## Context",
-    "   - **Gap identified by:** requirements scan of <source>",
-    "   - **Proposals file:** <RESEARCH_REQUIREMENTS_ROOT>/req-proposals-<scope>-<date>.md",
+    "5. **Write a verification report** to",
+    "   `<DELIVERABLES_DIR>/<RESEARCH_SLUG>.verify.md`:",
     "",
-    "   ## Inputs",
-    "   - **Depends on:** (none)",
-    "   - **Read:** <RESEARCH_REQUIREMENTS_ROOT>/req-proposals-<scope>-<date>.md, <source docs>",
+    "   ```markdown",
+    "   ---",
+    '   title: "Verification Report: <question>"',
+    "   slug: <RESEARCH_SLUG>",
+    "   date: YYYY-MM-DD",
+    "   parent_issue: <N>",
+    "   slices_read: <count>",
+    "   ---",
     "",
-    "   ## Acceptance Criteria",
-    "   - [ ] Requirement document follows <category> template",
-    "   - [ ] Traceability links to source BCM/competitive/product doc",
-    "   - [ ] Registry index updated",
-    "   - [ ] Decision authority rules followed (direct write vs. proposed)",
+    "   # Verification Report: <question>",
     "",
-    "   ## Scope Size",
-    "   small",
+    "   ## Acceptance Criteria Coverage",
+    "   - [x] <criterion> \u2014 covered by slice(s) <NN, NN>",
+    "   - [ ] <criterion> \u2014 **not covered**; gap noted in deliverable",
     "",
-    "   ## Output Path",
-    '   <REQUIREMENTS_ROOT>/<category>/<PREFIX>-<NNN>-<slug>.md"',
-    "   ```",
+    "   ## Slice Coverage",
+    "   | Slice | Claims | Reused in deliverable | Notes |",
+    "   |-------|--------|-----------------------|-------|",
+    "   | 01 | <count> | <count> | |",
     "",
-    "3. **Update source documents.** In each BCM model doc or competitive",
-    "   analysis that was scanned, add a note in the project-relevance /",
-    "   strategic-implications section (whichever heading the source doc uses)",
-    "   indicating that a requirement issue was created:",
+    "   ## Reconciled Contradictions",
+    "   - <short summary of each reconciled contradiction and why>",
     "",
-    "   ```markdown",
-    "   - Gap addressed: see [<PREFIX>-<NNN>](<relative path to requirement doc>)",
-    "     (issue #<N>)",
+    "   ## Unresolved Contradictions",
+    "   - <contradiction the verifier could not resolve>",
+    "",
+    "   ## Gaps",
+    "   - <question the pipeline could not answer>",
     "   ```",
     "",
-    "4. **Comment on the scan issue** with a summary of all issues created and",
-    "   all docs updated.",
+    "6. **Comment on the scope issue** with a summary linking to the",
+    "   deliverable and verification report.",
     "",
-    "5. **Commit and push.**",
+    "7. **Commit and push.** Close the verify issue.",
     "",
     "---",
     "",
-    "## Coordination with Other Agents",
-    "",
-    "| Direction | Agent | What |",
-    "|-----------|-------|------|",
-    "| Upstream | BCM Writer | Scans capability-model docs for project-relevance gaps (judged against `docs/project-context.md`) |",
-    "| Upstream | Company Research | Scans competitive analysis for feature comparison gaps |",
-    "| Upstream | Meeting Analyst | Scans meeting extracts for requirement proposals |",
-    "| Downstream | Requirements Writer (BCM Writer) | Creates `type:requirement` issues for the skill to draft |",
-    "",
-    "**File boundaries:** Writes to `<RESEARCH_REQUIREMENTS_ROOT>/req-*.md` and",
-    "minor traceability edits to `<BCM_DOCS_ROOT>` and `<COMPETITIVE_ROOT>`.",
-    "Never writes to `<REQUIREMENTS_ROOT>/` \u2014 that is owned by the",
-    "requirements-writer agent.",
+    "## Output Boundaries",
     "",
-    "---",
+    "This agent writes **only** to:",
     "",
-    "## Blocked Issues",
+    "- `<SCOPE_DIR>/` \u2014 scope files (Phase 1)",
+    "- `<SLICES_DIR>/` \u2014 slice notes (Phase 2)",
+    "- `<DELIVERABLES_DIR>/` \u2014 deliverables and verification reports",
+    "  (Phase 3)",
     "",
-    "Additional block reasons specific to requirements synthesis:",
-    "- Source document has unresolved contradictions",
-    "- Category classification is ambiguous (needs human disambiguation)",
-    "- Dependent BCM documents are still in draft with placeholder content",
+    "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",
     "",
-    "- **Discover, don't write requirements.** Create issues for the",
-    "  requirements-writer \u2014 don't write requirement documents directly.",
-    "- **Deduplicate rigorously.** Check both existing docs and open issues",
-    "  before flagging a gap.",
-    "- **Respect decision authority.** Mark ADR/TR proposals as needing human",
-    "  decision. Don't create direct-write issues for technology choices.",
-    "- **Bidirectional traceability.** Every `req-scan-*.md` and",
-    "  `req-proposals-*.md` must include a `## Produced` section listing the",
-    "  downstream requirement issues (and eventual requirement documents) it",
-    "  spawned, as markdown links; each formal requirement document under",
-    "  `<REQUIREMENTS_ROOT>/` must include a forward link back to the scan or",
-    "  proposal that produced it."
+    "- **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 scanRequirementsSkill = {
-  name: "scan-requirements",
-  description: "Kick off a requirements-analyst scan across BCM model docs, competitive analysis, product docs, or meeting extracts. Creates a req:scan issue and dispatches Phase 1.",
+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: "requirements-analyst",
+  agent: "research-analyst",
   platforms: { cursor: { exclude: true } },
   instructions: [
-    "# Scan Requirements",
+    "# Research",
     "",
-    "Kick off a requirements-analyst scan cycle. Creates a `req:scan` issue",
-    "targeted at the requested scope and dispatches Phase 1 (Scan) in the",
-    "requirements-analyst agent.",
+    "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",
     "",
-    "/scan-requirements <scope>",
+    "/research <question>",
     "",
-    "Where `<scope>` is one of:",
-    "- `bcm:<PREFIX-NNN>` \u2014 a single BCM model doc",
-    "- `competitive:<slug>` \u2014 a single competitive analysis doc",
-    "- `product-roadmap` \u2014 the prioritized feature roadmap",
-    "- `entity-taxonomy` \u2014 the entity taxonomy doc",
-    "- `meeting:<slug>` \u2014 a meeting extract",
-    "- `all-bcm` / `all-competitive` \u2014 full sweep (long-running)",
+    "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 `req:scan` issue with `type:requirement`, `priority:medium`,",
-    "   and `status:ready`. Body must list the files to read and the scan scope.",
-    "2. Execute Phase 1 (Scan) of the requirements-analyst agent.",
-    "3. If gaps are found, a `req:draft` issue is created automatically.",
+    "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 `req-scan-<scope>-<YYYY-MM-DD>.md` file under the project's research",
-    "  requirements directory.",
-    "- A `req:draft` issue if any gaps were identified."
+    "- 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 requirementsAnalystBundle = {
-  name: "requirements-analyst",
-  description: "Requirements gap-discovery agent bundle for BCM-driven projects. 3-phase pipeline (scan, draft, trace) with req:* phase labels.",
-  appliesWhen: () => true,
+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: "requirements-analyst-workflow",
-      description: "Describes the 3-phase requirements gap-discovery pipeline, the req:* label taxonomy, and the boundary with the downstream requirements-writer agent.",
+      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: [
-        "# Requirements Analyst Workflow",
+        "# Research Pipeline Workflow",
         "",
-        "Use `/scan-requirements <scope>` to kick off a requirements gap",
-        "discovery cycle. The pipeline runs in 3 phases \u2014 scan, draft, trace \u2014",
-        "each tracked by its own GitHub issue labeled `req:scan`, `req:draft`,",
-        "or `req:trace`. All issues carry `type:requirement`.",
+        "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 requirements-analyst *discovers gaps and drafts proposals*; it",
-        "does **not** write final requirement documents. Writing is the job of",
-        "the downstream requirements-writer (BCM writer) agent. Keep that",
-        "boundary clean: proposals land under the research requirements",
-        "directory, not under the authoritative requirements tree.",
+        "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 `requirements-analyst` agent definition for full workflow",
-        "details and phase-by-phase instructions."
+        "See the `research-analyst` agent definition for full workflow",
+        "details, default paths, and phase-by-phase instructions."
       ].join("\n"),
       platforms: {
         cursor: { exclude: true }
@@ -3870,55 +4894,94 @@ var requirementsAnalystBundle = {
       tags: ["workflow"]
     }
   ],
-  skills: [scanRequirementsSkill],
-  subAgents: [requirementsAnalystSubAgent],
+  skills: [researchSkill],
+  subAgents: [researchAnalystSubAgent],
   labels: [
     {
-      name: "type:requirement",
-      color: "1D76DB",
-      description: "Work that produces or discovers a requirement document (FR, BR, NFR, etc.)"
+      name: "type:research",
+      color: "5319E7",
+      description: "Work that produces or consumes a research note, slice, or deliverable"
     },
     {
-      name: "req:scan",
+      name: "research:scope",
       color: "C5DEF5",
-      description: "Phase 1: scan source docs for requirement gaps and deduplicate"
+      description: "Phase 1: decompose a research question into N focused slice issues"
     },
     {
-      name: "req:draft",
+      name: "research:slice",
       color: "BFDADC",
-      description: "Phase 2: draft requirement proposals for the requirements-writer"
+      description: "Phase 2: execute one research slice \u2014 search authorized sources and write a slice note"
     },
     {
-      name: "req:trace",
+      name: "research:verify",
       color: "D4C5F9",
-      description: "Phase 3: create requirement issues and backfill traceability on source docs"
+      description: "Phase 3: reconcile slice notes into a verified deliverable"
     }
   ]
 };
 
-// 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.",
+// src/agent/bundles/slack.ts
+var slackBundle = {
+  name: "slack",
+  description: "Slack MCP message formatting and best practices",
+  appliesWhen: () => false,
+  rules: [
+    {
+      name: "slack-message-formatting",
+      description: "Format Slack messages with explicit links so bullets and labels render correctly",
+      scope: AGENT_RULE_SCOPE.ALWAYS,
+      content: [
+        "# Slack Message Formatting",
+        "",
+        "When composing or sending messages to Slack (e.g., via Slack MCP tools like `slack_send_message`), use formatting that Slack's mrkdwn parser renders correctly.",
+        "",
+        "## Rules",
+        "",
+        "1. **Use Slack's explicit link syntax** for any link in a message:",
+        "   - Format: `<https://example.com|display text>`",
+        "   - Text outside the angle brackets (bullets, labels) stays separate and won't merge into the link",
+        "",
+        "2. **Do not rely on auto-linkification** when the message has bullets or labels before URLs \u2014 auto-linked URLs can break or merge with surrounding text",
+        "",
+        "3. **Put each list item on its own line** with a newline between items so list structure is clear",
+        "",
+        "4. **Example \u2014 preferred:**",
+        "   ```",
+        "   Status update:",
+        "",
+        "   \u2022 Feature A: <https://github.com/org/repo/pull/1|repo#1>",
+        "   \u2022 Feature B: <https://github.com/org/repo/pull/2|repo#2>",
+        "   ```",
+        "",
+        "5. **Avoid:** Plain URLs immediately after a bullet/label on the same line (e.g., `\u2022 Feature A: https://github.com/...`) when sending via API, as it can render with bullets inside or between links"
+      ].join("\n"),
+      tags: ["workflow"]
+    }
+  ]
+};
+
+// src/agent/bundles/software-profile.ts
+var softwareProfileAnalystSubAgent = {
+  name: "software-profile-analyst",
+  description: "Researches a software product (competitor, adjacent, incumbent, enabler, infrastructure, or ecosystem-tool) from public sources, produces a structured markdown profile, and contributes rows to a shared feature matrix ranked against configurable segment-importance weights. One product per session, tracked by software:* GitHub issue labels.",
   model: AGENT_MODEL.POWERFUL,
   maxTurns: 80,
   platforms: { cursor: { exclude: true } },
   prompt: [
-    "# Research Analyst Agent",
+    "# Software Profile 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.",
+    "You research a single software product 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, a set of feature-matrix rows, and optional",
+    "follow-up research issues for adjacent products.",
     "",
     "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.",
+    "the consuming project sells, which industry it serves, or which",
+    "products matter to it. All domain-specific vocabulary, segment",
+    "weights, feature taxonomies, 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.",
@@ -3928,75 +4991,144 @@ var researchAnalystSubAgent = {
     ...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.",
+    "1. **One product per session.** Never profile two products in a",
+    "   single session, even if they came up together.",
+    "2. **Public sources only.** Use the product's own site, docs, pricing",
+    "   pages, changelogs, public demos, and similar 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 and feature-matrix",
+    "   rows are the deliverables. Both are 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 product types, feature",
+    "   taxonomies, or segment assumptions. Use the generic software-type",
+    "   taxonomy below and let consuming projects override it via their",
+    "   `docs/project-context.md` or `agentConfig.rules`.",
+    "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",
+    "   products worth evaluating, emit a follow-up issue rather than",
+    "   expanding the profile beyond its scope.",
+    "7. **Segment weights live in project context.** Segment-importance",
+    "   weights belong in `docs/project-context.md` (or an override",
+    "   passed in the issue body). This agent reads them; it never",
+    "   invents them.",
+    "",
+    "---",
+    "",
+    "## Software Type Taxonomy",
+    "",
+    "Pick exactly one type per software 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` | Products that offer a substitutable feature set to the same buyers for the same jobs-to-be-done. |",
+    "| `adjacent` | Products that solve a neighboring problem or serve an overlapping buyer \u2014 not a direct substitute but worth understanding for positioning and integration. |",
+    "| `incumbent` | Established, widely-deployed products that define the status quo in the space. Often older, broader, and harder to displace. |",
+    "| `enabler` | Products the consuming project might build on, integrate with, or resell. Platforms, SDKs, APIs, and similar building blocks. |",
+    "| `infrastructure` | Lower-level infrastructure or runtime components the consuming project depends on (databases, queues, identity, observability, etc.). |",
+    "| `ecosystem-tool` | Developer tooling, plugins, extensions, or companion products that surround an incumbent or competitor without being one themselves. |",
+    "",
+    "If the product plausibly fits two types, prefer the one that reflects",
+    "the **reason the profile was requested**, and note the secondary",
+    "type in the profile body.",
+    "",
+    "---",
+    "",
+    "## Segment-Importance Weights",
+    "",
+    "Feature ranking uses **segment-importance weights** \u2014 a small table",
+    "that assigns a numeric weight to each customer segment the consuming",
+    "project cares about. Higher weight means the segment matters more to",
+    "the project's own strategy; features that serve high-weight segments",
+    "rank higher in the matrix.",
+    "",
+    "**Convention:** segment weights live in `docs/project-context.md`",
+    "under a `## Segment Weights` section. The format is a simple",
+    "markdown table with `segment` and `weight` columns. Weights are",
+    "non-negative numbers; the scale is project-defined (0\u20131, 0\u201310, and",
+    "0\u2013100 are all valid as long as the project is internally",
+    "consistent).",
+    "",
+    "Example `docs/project-context.md` fragment:",
+    "",
+    "```markdown",
+    "## Segment Weights",
+    "",
+    "| segment | weight |",
+    "|---------|--------|",
+    "| enterprise | 3 |",
+    "| mid-market | 2 |",
+    "| smb       | 1 |",
+    "| hobbyist  | 0.5 |",
+    "```",
+    "",
+    "If `docs/project-context.md` does not define segment weights,",
+    "**do not invent them**. Either:",
+    "",
+    "- Accept an `weights:` override in the invoking issue body, or",
+    "- Produce the feature matrix with a single segment (`default`)",
+    "  weighted `1` and flag the missing weights in the profile's",
+    "  `## Open Questions` section.",
     "",
     "---",
     "",
     "## 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",
+    "\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. RESEARCH  \u2502\u2500\u2500\u25B6\u2502 2. PROFILE   \u2502\u2500\u2500\u25B6\u2502 3. MATRIX    \u2502\u2500\u2500\u25B6\u2502 4. FOLLOWUP  \u2502",
+    "\u2502 Collect      \u2502   \u2502 Write the    \u2502   \u2502 Extract      \u2502   \u2502 Enqueue      \u2502",
+    "\u2502 public       \u2502   \u2502 structured   \u2502   \u2502 feature rows \u2502   \u2502 research for \u2502",
+    "\u2502 sources into \u2502   \u2502 markdown     \u2502   \u2502 and score    \u2502   \u2502 adjacent     \u2502",
+    "\u2502 bounded      \u2502   \u2502 profile to   \u2502   \u2502 against the  \u2502   \u2502 products     \u2502",
+    "\u2502 notes file   \u2502   \u2502 <PROFILES>/  \u2502   \u2502 weights      \u2502   \u2502 surfaced     \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 |",
     "|-------|-------|-------------|",
-    "| `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. |",
+    "| `software:research` | 1. Research | Gather public sources. Write a bounded research-notes file. Create the profile issue. |",
+    "| `software:profile` | 2. Profile | Read the research notes. Write the structured profile to `<PROFILES_DIR>`. Create the matrix issue. |",
+    "| `software:matrix` | 3. Matrix | Read the profile. Extract feature rows into `<MATRIX_FILE>`. Score against segment weights. Create the follow-up issue if warranted. |",
+    "| `software:followup` | 4. Followup | Read the profile. Enqueue software-research issues for adjacent products surfaced in the profile. |",
     "",
-    "All issues also carry `type:research` and a `status:*` label.",
+    "All issues also carry `type:software-profile` and a `status:*` label.",
     "",
-    "**Issue count per research cycle:** 1 scope + N slice + 1 verify =",
-    "**N + 2 sessions**. Typical N is 3\u20136.",
+    "**Issue count per product cycle:** 1 research + 1 profile + 1 matrix +",
+    "0\u20131 followup = **3\u20134 sessions**. The followup phase is skipped when",
+    "the profile did not surface any adjacent product worth researching.",
     "",
     "**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.",
+    "- Research phase determines the product 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**.",
+    "- Narrow product with no adjacent candidates \u2192 **3 sessions**.",
     "",
     "---",
     "",
     "## 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`.",
+    "defaults by passing paths in the `/profile-software` 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` |",
+    "| `<SOFTWARE_ROOT>` | Root folder for software profiles | `docs/software/` |",
+    "| `<PROFILES_DIR>` | Final software profile files | `<SOFTWARE_ROOT>/profiles/` |",
+    "| `<NOTES_DIR>` | Research-notes files from Phase 1 | `<SOFTWARE_ROOT>/notes/` |",
+    "| `<MATRIX_FILE>` | Shared feature-matrix file | `<SOFTWARE_ROOT>/feature-matrix.md` |",
+    "| `<PRODUCT_SLUG>` | Short kebab-case slug identifying the product | derived from the product name |",
     "",
-    "If `docs/project-context.md` specifies a different research tree,",
-    "prefer that. Otherwise fall back to the defaults above.",
+    "If `docs/project-context.md` specifies a different software-research",
+    "tree (for example by reusing the research-pipeline deliverables",
+    "folder), prefer that. Otherwise fall back to the defaults above.",
     "",
     "---",
     "",
@@ -4004,221 +5136,275 @@ var researchAnalystSubAgent = {
     "",
     "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`.",
+    "1. Claim one open `type:software-profile` issue using phase priority:",
+    "   `software:research` > `software:profile` > `software:matrix` >",
+    "   `software: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 `research:*`",
+    "3. Execute the phase handler that matches the issue's `software:*`",
     "   label.",
     "4. Commit, push, open a PR (if applicable), and close the issue per",
     "   your project's PR workflow.",
     "",
     "---",
     "",
-    "## Phase 1: Scope (`research:scope`)",
+    "## Phase 1: Research (`software:research`)",
     "",
-    "**Goal:** Turn a natural-language research question into a bounded",
-    "scope file and `N` focused slice issues.",
+    "**Goal:** Gather public sources into a bounded research-notes file.",
     "",
-    "**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.",
+    "**Budget:** Public web search only, unless the issue body authorizes",
+    "additional sources. Write one notes file. Do not write the profile",
+    "or extend the feature matrix in this phase.",
     "",
     "### 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",
+    "1. **Read the issue body.** It should include:",
+    "   - The product name and website (if known)",
+    "   - The requested software type from the taxonomy above",
+    "   - The reason the profile was requested (framing \u2014 what does the",
+    "     invoking project want to learn?)",
+    "   - Optional: `<PRODUCT_SLUG>` override, custom output paths,",
+    "     `weights:` override for segment-importance weights",
     "",
-    "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>/`.",
+    "2. **Derive `<PRODUCT_SLUG>`** if not supplied \u2014 a 2\u20134 word",
+    "   kebab-case summary of the product name. Ensure the slug is not",
+    "   already in use under `<PROFILES_DIR>/` or `<NOTES_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)",
+    "3. **Gather sources.** Prioritize in this order:",
+    "   - The product's own website (home, product, pricing, docs,",
+    "     changelog, integrations)",
+    "   - Public documentation, developer references, API docs",
+    "   - Public changelogs, release notes, roadmap posts",
+    "   - Reputable independent reviews and comparison articles",
+    "   - Public issue trackers or community forums when the issue body",
+    "     authorizes them",
     "",
-    "4. **Write the scope file** to",
-    "   `<SCOPE_DIR>/<RESEARCH_SLUG>.scope.md`:",
+    "4. **Write a research-notes file** to",
+    "   `<NOTES_DIR>/<PRODUCT_SLUG>.notes.md`:",
     "",
     "   ```markdown",
     "   ---",
-    '   title: "Research Scope: <question>"',
-    "   slug: <RESEARCH_SLUG>",
+    '   title: "Research Notes: <product name>"',
+    "   slug: <PRODUCT_SLUG>",
+    "   software_type: <one of the taxonomy values>",
     "   date: YYYY-MM-DD",
     "   parent_issue: <N>",
-    "   slice_count: <N>",
     "   ---",
     "",
-    "   # Research Scope: <question>",
-    "",
-    "   ## Question",
-    "   <verbatim question from the issue>",
+    "   # Research Notes: <product name>",
     "",
-    "   ## Authorized Sources",
-    "   - <source category or path>",
+    "   ## Framing",
+    "   <why this product was requested and what to learn>",
     "",
-    "   ## Acceptance Criteria",
-    "   - [ ] <criterion for the final deliverable>",
+    "   ## Raw Findings",
+    "   - <finding> \u2014 source: <citation>",
     "",
-    "   ## 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",
+    "   ## Candidate Features",
+    "   - <feature name>: <one-line description> \u2014 source: <citation>",
     "",
-    "   ### Slice 2: <title>",
-    "   ...",
+    "   ## Candidate Adjacent Products",
+    "   - <product name> \u2014 source: <citation>",
     "",
-    "   ## Out of Scope",
-    "   <sub-questions deliberately excluded from this cycle>",
+    "   ## Open Questions",
+    "   <anything the notes could not answer from public sources>",
     "",
-    "   ## Deliverable",
-    "   <DELIVERABLES_DIR>/<RESEARCH_SLUG>.md",
+    "   ## Sources",
+    "   - <source URL or file path> \u2014 <date accessed>",
     "   ```",
     "",
-    "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.",
+    "5. **Create the `software:profile` issue** with",
+    "   `Depends on: #<research-issue>`. Its body references the notes",
+    "   file path and the requested software type.",
     "",
-    "7. **Commit and push** the scope file. Close the scope issue.",
+    "6. **Commit and push** the notes file. Close the research issue.",
     "",
     "---",
     "",
-    "## Phase 2: Slice (`research:slice`)",
+    "## Phase 2: Profile (`software:profile`)",
     "",
-    "**Goal:** Answer one slice by searching the authorized sources and",
-    "writing a single slice note file.",
+    "**Goal:** Write the structured software profile from the research",
+    "notes.",
     "",
-    "**Budget:** Search budget is one slice \u2014 do not expand scope. Write",
-    "one slice note. Do not create downstream issues.",
+    "**Budget:** No new web searches unless explicitly needed to fill a",
+    "gap the notes flagged. Write one profile file.",
     "",
     "### 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.",
+    "1. **Read the research-notes file** referenced in the issue body.",
     "",
-    "4. **Synthesize a slice note** and write it to the slice's output",
-    "   path (e.g. `<SLICES_DIR>/<RESEARCH_SLUG>-NN-<slug>.slice.md`):",
+    "2. **Check for duplicates.** If `<PROFILES_DIR>/<PRODUCT_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>/<PRODUCT_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: "Slice NN: <title>"',
-    "   slug: <RESEARCH_SLUG>",
-    "   slice: NN",
+    '   title: "<product name>"',
+    "   slug: <PRODUCT_SLUG>",
+    "   software_type: <one of the taxonomy values>",
+    "   website: <primary URL>",
     "   date: YYYY-MM-DD",
-    "   parent_scope: <SCOPE_DIR>/<RESEARCH_SLUG>.scope.md",
     "   parent_issue: <N>",
+    "   notes: <NOTES_DIR>/<PRODUCT_SLUG>.notes.md",
     "   ---",
     "",
-    "   # Slice NN: <title>",
+    "   # <product name>",
     "",
-    "   ## Question",
-    "   <the slice-level question>",
+    "   ## Summary",
+    "   <2\u20134 sentence elevator description: what it does, who it's for>",
     "",
-    "   ## Key Findings",
-    "   - <finding> \u2014 source: <citation>",
+    "   ## Classification",
+    "   - **Primary type:** <taxonomy value>",
+    "   - **Secondary type (if any):** <taxonomy value or `n/a`>",
+    "   - **Relevance to this project:** <1\u20132 sentences tying the product",
+    "     back to the framing from the notes>",
     "",
-    "   ## Evidence",
-    "   <short quotations, paraphrases, or structured data with citations>",
+    "   ## Offering",
+    "   - **Jobs-to-be-done:** <bullet list of core use cases>",
+    "   - **Target segments:** <who this product is for; reuse segment",
+    "     names from the project's segment-weights table when possible>",
+    "   - **Pricing model:** <if disclosed>",
+    "   - **Deployment model:** <SaaS / self-hosted / hybrid / on-prem>",
     "",
-    "   ## Gaps / Open Questions",
-    "   <anything the slice could not answer inside its budget>",
+    "   ## Features",
+    "   <grouped bullet list of notable features, each cited. These become",
+    "   the rows in the feature matrix during Phase 3.>",
+    "",
+    "   ## Technology Signals",
+    "   <stack hints from docs, integrations, and public engineering",
+    "   content \u2014 each bullet cited>",
+    "",
+    "   ## Positioning / Differentiation",
+    "   <how the product describes itself and how it differs from adjacent",
+    "   products \u2014 use its own language, cited, rather than inferred>",
+    "",
+    "   ## Risks / Open Questions",
+    "   <what the profile could not answer; flag anything the matrix or",
+    "   follow-up phase should escalate>",
+    "",
+    "   ## Follow-up Candidates",
+    "   - **Adjacent products to evaluate:** <list of candidate product",
+    "     names>",
     "",
     "   ## Sources",
-    "   - <source URL or file path> \u2014 <date accessed>",
+    "   - <source URL> \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.",
+    "4. **Create the `software:matrix` issue** with",
+    "   `Depends on: #<profile-issue>`. Its body references the profile",
+    "   path, the matrix file path, and the segment-weights source",
+    "   (`docs/project-context.md` or an explicit override).",
     "",
-    "6. **Commit and push** the slice note. Close the slice issue.",
+    "5. **Commit and push** the profile file. Close the profile issue.",
     "",
     "---",
     "",
-    "## Phase 3: Verify (`research:verify`)",
+    "## Phase 3: Matrix (`software:matrix`)",
     "",
-    "**Goal:** Reconcile every slice into a single verified deliverable.",
+    "**Goal:** Extract feature rows from the profile into the shared",
+    "feature matrix and score each feature against the segment-importance",
+    "weights.",
     "",
-    "**Budget:** No new web searches. Read the scope, read every slice",
-    "note, reconcile contradictions, write the deliverable and a short",
-    "verification report.",
+    "**Budget:** No new research. Read the profile, update the matrix,",
+    "close the phase.",
+    "",
+    "### Matrix File Format",
+    "",
+    "The feature matrix is a single markdown file at `<MATRIX_FILE>`. It",
+    "uses a wide table with one row per (product, feature) pair and one",
+    "column per segment plus a computed `score` column.",
+    "",
+    "```markdown",
+    "---",
+    'title: "Software Feature Matrix"',
+    "weights_source: docs/project-context.md#segment-weights",
+    "updated: YYYY-MM-DD",
+    "---",
+    "",
+    "# Software Feature Matrix",
+    "",
+    "| product | feature | <segment-1> | <segment-2> | ... | score | source |",
+    "|---------|---------|-------------|-------------|-----|-------|--------|",
+    "| <slug>  | <feature-name> | 0\u20131 | 0\u20131 | ... | <weighted-sum> | <profile-path> |",
+    "```",
+    "",
+    "Segment columns carry a **coverage score** in `[0, 1]` representing",
+    "how well the feature serves that segment \u2014 `1` means fully covered,",
+    "`0` means not covered, intermediate values reflect partial coverage",
+    "(e.g. self-serve only, gated by pricing tier, limited by scale).",
+    "",
+    "The `score` column is the weighted sum:",
+    "",
+    "```",
+    "score = \u03A3 (coverage[segment] * weight[segment])",
+    "```",
+    "",
+    "using the weights loaded from `docs/project-context.md`.",
     "",
     "### 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`.",
+    "1. **Load segment weights.** Read `## Segment Weights` from",
+    "   `docs/project-context.md`. If absent, fall back to the",
+    "   `weights:` override in the issue body, or the single-segment",
+    "   default described in `## Segment-Importance Weights` above.",
     "",
-    "2. **Build a claim index.** For every assertion in any slice, note",
-    "   which slice(s) support it and which sources back it.",
+    "2. **Read the profile file** referenced in the issue body. Extract",
+    "   the bullets under `## Features` as candidate matrix rows.",
     "",
-    "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",
+    "3. **Open or create `<MATRIX_FILE>`.** If the file does not exist,",
+    "   write the front-matter and header row using the current set of",
+    "   segment columns. If it exists, ensure its segment columns match",
+    "   the loaded weights; if they have drifted, add any missing columns",
+    "   and leave a note in the profile's `## Risks / Open Questions`.",
     "",
-    "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.",
+    "4. **Append or update rows** for the current product. One row per",
+    "   feature. For each row:",
+    "   - Assign a coverage score in `[0, 1]` for each segment, citing",
+    "     the profile section that justifies the score.",
+    "   - Compute the `score` as the weighted sum.",
+    "   - Set the `source` column to the profile file path.",
     "",
-    "5. **Write a verification report** to",
-    "   `<DELIVERABLES_DIR>/<RESEARCH_SLUG>.verify.md`:",
+    "5. **Update the matrix front-matter** (`updated: YYYY-MM-DD`).",
     "",
-    "   ```markdown",
-    "   ---",
-    '   title: "Verification Report: <question>"',
-    "   slug: <RESEARCH_SLUG>",
-    "   date: YYYY-MM-DD",
-    "   parent_issue: <N>",
-    "   slices_read: <count>",
-    "   ---",
+    "6. **Decide whether a follow-up issue is warranted.** Create a",
+    "   `software:followup` issue (depending on this matrix issue) only",
+    "   if the profile lists at least one adjacent product candidate.",
+    "   Otherwise, note in the matrix issue's closing comment that no",
+    "   follow-up is needed.",
     "",
-    "   # Verification Report: <question>",
+    "7. **Commit and push** the matrix file (and any profile updates).",
+    "   Close the matrix issue.",
     "",
-    "   ## 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> | |",
+    "## Phase 4: Followup (`software:followup`)",
     "",
-    "   ## Reconciled Contradictions",
-    "   - <short summary of each reconciled contradiction and why>",
+    "**Goal:** Create downstream research issues for the adjacent products",
+    "surfaced in the profile.",
     "",
-    "   ## Unresolved Contradictions",
-    "   - <contradiction the verifier could not resolve>",
+    "**Budget:** No new research. Read the profile, enqueue issues, close",
+    "the phase.",
     "",
-    "   ## Gaps",
-    "   - <question the pipeline could not answer>",
-    "   ```",
+    "### Steps",
     "",
-    "6. **Comment on the scope issue** with a summary linking to the",
-    "   deliverable and verification report.",
+    "1. **Read the profile file** referenced in the issue body.",
     "",
-    "7. **Commit and push.** Close the verify issue.",
+    "2. **Enqueue software-research issues** for each entry under",
+    "   `Follow-up Candidates > Adjacent products to evaluate`. Each new",
+    "   issue follows the same 4-phase pipeline \u2014 start it in the",
+    "   `software:research` phase with `type:software-profile`,",
+    "   `priority:medium`, and `status:ready`.",
+    "",
+    "3. **Cross-link** \u2014 update the profile's `## Follow-up Candidates`",
+    "   section so each entry references its newly-created issue number.",
+    "",
+    "4. **Commit and push** (if the profile was updated). Close the",
+    "   followup issue.",
     "",
     "---",
     "",
@@ -4226,118 +5412,133 @@ var researchAnalystSubAgent = {
     "",
     "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)",
+    "- `<NOTES_DIR>/` \u2014 research-notes files (Phase 1)",
+    "- `<PROFILES_DIR>/` \u2014 software profiles (Phase 2, updated in later",
+    "  phases)",
+    "- `<MATRIX_FILE>` \u2014 shared feature matrix (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.",
+    "The pipeline produces **profiles, notes, and matrix rows only**.",
+    "Deeper research on adjacent products is delegated to new cycles of",
+    "this same pipeline via follow-up issues. This agent never writes",
+    "company profiles, person profiles, formal requirement documents, or",
+    "comparative long-form analyses itself. Keep this boundary clean so",
+    "the software-profile pipeline stays generic.",
     "",
     "---",
     "",
     "## Rules",
     "",
-    "- **One phase per session.** Never run two phases back-to-back in a",
-    "  single session.",
+    "- **One product per session.** Never profile two products back-to-back.",
     "- **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."
+    "- **Cite everything.** Profile claims without source citations do not",
+    "  belong in the deliverable.",
+    "- **No invented weights.** Segment weights come from",
+    "  `docs/project-context.md` or an explicit issue-body override. If",
+    "  neither is available, fall back to the single-segment default and",
+    "  flag the gap \u2014 never guess.",
+    "- **Produce profiles and matrix rows, not downstream work.** Do not",
+    "  open `type:requirement` or formal evaluation issues from this",
+    "  pipeline. Follow-up work is scoped through `software:followup` or",
+    "  delegated to downstream research agents."
   ].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.",
+var profileSoftwareSkill = {
+  name: "profile-software",
+  description: "Kick off a software-profile pipeline. Creates a software:research issue for the given product and dispatches Phase 1 (Research) in the software-profile-analyst agent.",
   disableModelInvocation: true,
   userInvocable: true,
   context: "fork",
-  agent: "research-analyst",
+  agent: "software-profile-analyst",
   platforms: { cursor: { exclude: true } },
   instructions: [
-    "# Research",
+    "# Profile Software",
     "",
-    "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.",
+    "Kick off a software-profile pipeline. Creates a `software:research`",
+    "issue carrying the product name, type, and framing, then dispatches",
+    "Phase 1 (Research) in the software-profile-analyst agent.",
     "",
     "## Usage",
     "",
-    "/research <question>",
+    "/profile-software <product-name>",
     "",
-    "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",
+    "Optional extensions in the issue body:",
+    "- `type: <competitor | adjacent | incumbent | enabler |",
+    "   infrastructure | ecosystem-tool>` \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 product slug",
+    "- `weights: <table>` \u2014 override the segment-importance weights for",
+    "  this profile cycle (otherwise loaded from",
+    "  `docs/project-context.md`)",
+    "- `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/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`",
+    "- `docs/software/notes/<slug>.notes.md`",
+    "- `docs/software/profiles/<slug>.md`",
+    "- `docs/software/feature-matrix.md` (shared across all products)",
     "",
     "## Steps",
     "",
-    "1. Create a `research:scope` issue with `type:research`,",
+    "1. Create a `software:research` issue with `type:software-profile`,",
     "   `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.",
+    "   product name, selected type, framing, and any overrides.",
+    "2. Execute Phase 1 (Research) of the software-profile-analyst",
+    "   agent.",
+    "3. Phase 1 creates the `software:profile` issue. Phase 2 creates",
+    "   the `software:matrix` issue. Phase 3 may create a",
+    "   `software:followup` 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."
+    "- A research-notes file under the project's notes directory",
+    "- A single software profile under the profiles directory",
+    "- One or more rows appended to the shared feature-matrix file,",
+    "  scored against the configured segment weights",
+    "- Optional follow-up research issues for adjacent products",
+    "  surfaced in the profile",
+    "- This pipeline produces **profiles, notes, and matrix rows only**",
+    "  \u2014 it does not write company profiles, person profiles, or formal",
+    "  requirement documents itself."
   ].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.",
+var softwareProfileBundle = {
+  name: "software-profile",
+  description: "Software research, profiling, and feature-matrix pipeline: research, profile, matrix, followup. Opt-in only; domain-neutral; filesystem-durable between phases; ranks features against configurable segment-importance weights.",
   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.",
+      name: "software-profile-workflow",
+      description: "Describes the 4-phase software-profile pipeline, the software:* label taxonomy, the generic software-type taxonomy, and the segment-weights convention that drives feature-matrix scoring.",
       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."
+        "# Software Profile Workflow",
+        "",
+        "Use `/profile-software <product-name>` to kick off a software",
+        "research, profiling, and feature-matrix pipeline. The pipeline",
+        "runs in up to 4 phases \u2014 research, profile, matrix, followup \u2014",
+        "each tracked by its own GitHub issue labeled",
+        "`software:research`, `software:profile`, `software:matrix`, or",
+        "`software:followup`. All issues carry `type:software-profile`.",
+        "",
+        "The pipeline produces **software profiles, research notes, and",
+        "rows in a shared feature matrix**. Features are ranked against",
+        "segment-importance weights declared in",
+        "`docs/project-context.md` under a `## Segment Weights` section.",
+        "Deeper research on adjacent products surfaced in a profile is",
+        "delegated to new cycles of this same pipeline via",
+        "`software:followup` issues.",
+        "",
+        "See the `software-profile-analyst` agent definition for full",
+        "workflow details, default paths, the software-type taxonomy,",
+        "the segment-weights convention, and phase-by-phase",
+        "instructions."
       ].join("\n"),
       platforms: {
         cursor: { exclude: true }
@@ -4345,68 +5546,33 @@ var researchPipelineBundle = {
       tags: ["workflow"]
     }
   ],
-  skills: [researchSkill],
-  subAgents: [researchAnalystSubAgent],
+  skills: [profileSoftwareSkill],
+  subAgents: [softwareProfileAnalystSubAgent],
   labels: [
     {
-      name: "type:research",
-      color: "5319E7",
-      description: "Work that produces or consumes a research note, slice, or deliverable"
+      name: "type:software-profile",
+      color: "0E8A16",
+      description: "Work that produces or maintains a software profile, research notes, or feature-matrix rows"
     },
     {
-      name: "research:scope",
+      name: "software:research",
       color: "C5DEF5",
-      description: "Phase 1: decompose a research question into N focused slice issues"
+      description: "Phase 1: gather public sources about a software product into a research-notes file"
     },
     {
-      name: "research:slice",
+      name: "software:profile",
       color: "BFDADC",
-      description: "Phase 2: execute one research slice \u2014 search authorized sources and write a slice note"
+      description: "Phase 2: write the structured software profile from research notes"
     },
     {
-      name: "research:verify",
+      name: "software:matrix",
       color: "D4C5F9",
-      description: "Phase 3: reconcile slice notes into a verified deliverable"
-    }
-  ]
-};
-
-// src/agent/bundles/slack.ts
-var slackBundle = {
-  name: "slack",
-  description: "Slack MCP message formatting and best practices",
-  appliesWhen: () => false,
-  rules: [
+      description: "Phase 3: extract feature rows into the shared feature matrix and score them against segment weights"
+    },
     {
-      name: "slack-message-formatting",
-      description: "Format Slack messages with explicit links so bullets and labels render correctly",
-      scope: AGENT_RULE_SCOPE.ALWAYS,
-      content: [
-        "# Slack Message Formatting",
-        "",
-        "When composing or sending messages to Slack (e.g., via Slack MCP tools like `slack_send_message`), use formatting that Slack's mrkdwn parser renders correctly.",
-        "",
-        "## Rules",
-        "",
-        "1. **Use Slack's explicit link syntax** for any link in a message:",
-        "   - Format: `<https://example.com|display text>`",
-        "   - Text outside the angle brackets (bullets, labels) stays separate and won't merge into the link",
-        "",
-        "2. **Do not rely on auto-linkification** when the message has bullets or labels before URLs \u2014 auto-linked URLs can break or merge with surrounding text",
-        "",
-        "3. **Put each list item on its own line** with a newline between items so list structure is clear",
-        "",
-        "4. **Example \u2014 preferred:**",
-        "   ```",
-        "   Status update:",
-        "",
-        "   \u2022 Feature A: <https://github.com/org/repo/pull/1|repo#1>",
-        "   \u2022 Feature B: <https://github.com/org/repo/pull/2|repo#2>",
-        "   ```",
-        "",
-        "5. **Avoid:** Plain URLs immediately after a bullet/label on the same line (e.g., `\u2022 Feature A: https://github.com/...`) when sending via API, as it can render with bullets inside or between links"
-      ].join("\n"),
-      tags: ["workflow"]
+      name: "software:followup",
+      color: "FBCA04",
+      description: "Phase 4: enqueue follow-up research issues for adjacent products surfaced in the profile"
     }
   ]
 };
@@ -5023,7 +6189,9 @@ var BUILT_IN_BUNDLES = [
   prReviewBundle,
   requirementsAnalystBundle,
   researchPipelineBundle,
-  companyProfileBundle
+  companyProfileBundle,
+  peopleProfileBundle,
+  softwareProfileBundle
 ];
 
 // src/agent/bundles/scope.ts
@@ -8561,6 +9729,7 @@ export {
   jestBundle,
   meetingAnalysisBundle,
   orchestratorBundle,
+  peopleProfileBundle,
   pnpmBundle,
   prReviewBundle,
   projenBundle,
@@ -8569,6 +9738,7 @@ export {
   resolveModelAlias,
   resolveTemplateVariables,
   slackBundle,
+  softwareProfileBundle,
   turborepoBundle,
   typescriptBundle,
   vitestBundle